trwnh / nginx-config-hacks Goto Github PK

https://save.matbm.net/nsbwoasfiqbc.html?XJW5yw

I've had an issue where a PHP app was at the /virtual folder in my server. The fast_cgi was claiming "file not found".
fastcgi_param SCRIPT_FILENAME $document_root/virtual/$fastcgi_script_name; solved the issue. Since the fast_cgi will search for scripts at the /virtual folder now.

Currently there is phpsub.conf:

and example subdirectory config:

maybe play around with this to see how modular it could be? just looking at it quickly it seems like the SCRIPT_FILENAME line can be moved out of phpsub.conf and the rewrite block could be eliminated entirely...

also with this config in particular, alias directive may not even be necessary since the folder name and the uri path are the same. perhaps it could be eliminated as well, or a better example used (where the uri is different from the physical path on the system).

https://blog.martinfjordvald.com/2013/04/nginx-config-history-fastcgi_params-versus-fastcgi-conf/

i can't seem to find any downsides to just using $request_filename 100% of the time over $document_root$fastcgi_script_name for SCRIPT_FILENAME. $request_filename just seems to be less likely to break -- it takes alias into account,

Also https://www.nginx.com/resources/wiki/start/topics/tutorials/config_pitfalls/#use-request-filename-for-script-filename

And if you use $request_filename, you should set index using index directive, fastcgi_index will not work.

which seems to be the only pitfall, per se.