!zotlabs.org | Hubzilla Development
In order to simplify the web server configuration, I've modified boot.php to serve the static pages (css,js,etc.) from the filesystem instead of needing the rules put in the NGINX configuration (or .htaccess or apache config). This allows separating the application server from the web server (eg. PHP-FPM on a secured - "internal network" TCP port).
Basically - EVERYTHING get's rewritten and fed into PHP - and static files (files that have the specified extensions AND exist in the directory tree) get fed using fpassthru($filehandle).
Certainly this is inefficient unless caching is enabled (of course, obeying the Cache-control directives). But as long as caching is set up, I find a number of benefits to this setup.
This may be too specialized for a general MR, but if others consider it useful, I'll submit it. (I have a fairly unique use-case and network deployment structure including using intermediate caching in the 'outward facing' NGINX servers that serve pages, so this may not be generally useful. Of course, we could add a configuration variable... but unless someone else expresses an interest, I don't want to add stuff just because we can.)