Multi-Application Dynamic Routing with Static Asset Fallback

This configuration snippet defines an internal routing engine rule set within Nginx Unit to evaluate incoming HTTP requests sequentially. The routing core compares request URI paths against configured glob patterns. When a URI matches static asset extensions, Unit bypasses runtime application workers entirely and serves assets directly from disk using kernel-level file transfer optimizations. Unmatched URIs fall back to an isolated application process pool.

This design pattern is essential for hybrid monoliths or microservices where static frontend assets must be served with low latency alongside a dynamic REST API backend. It eliminates the need for a separate Nginx reverse proxy layer placed in front of application runtimes like Python or PHP.

Offloading static file delivery directly to Unit reduces application process thread consumption and memory overhead. However, administrators must carefully configure target directory permissions and ensure asset paths do not leak sensitive root file system structures beyond the designated static root path.

> System.Execute()

curl -X PUT -d '[
  {
    "match": {
      "uri": ["/static/*", "*.png", "*.js", "*.css"]
    },
    "action": {
      "share": "/var/www/app/static/"
    }
  },
  {
    "action": {
      "pass": "applications/py_api"
    }
  }
]' --unix-socket /var/run/control.unit.sock http://localhost/config/routes/main_route

> Architecture & Security Context

Verified for Valters IT Hub. When deploying this configuration in a production homelab or enterprise environment, ensure that you monitor system resources and implement strict access controls. Administrator privileges are required.

ID: VALTERSIT-CFADABB595AD