Please, allow locations {} usage in "Additional nginx directives"
Please, allow locations {} usage in "Additional nginx directives" in addition to simple directives. Thank you.
dreamer22
shared this idea
Thank you for your input!
Unfortunately, we have to close your request because it has not become quite popular for further implementation over the years.
—
IG
-
Patrick Zajda commented
Hello,
In the virtual host config file, there is a location ~/ which could break some other locations.
Replacing it by location / could help a lot to avoid conflicts, else custom directives are not used at all because of the ~/ -
dreamer22
commented
May be you need to make the whole template thing more transparent, like embedding clear logical blocks into the additional apache & nginx commands page. I have had some issues with setting a some location directive, or better said, keeping them apart. I cannot be more specific, because it was a while ago, and I have no access to that server anymore, sorry. but there is definitely something wrong. And probably, integrating all the nginx config files into the plesk panel would be great, like http config, server, locations configs and so on.
I hope you could follow me. I am not good with nginx.Thank you anyways, plesk is great!
-
David Wieler
commented
It does allow new locations. For example, 'location ~ / {}' will work. But you CAN NOT change anything inside 'location / {}', because it's already set, and you'll get a duplicate location error.....
Only way to change this is my manually editing files in cd /usr/local/psa/admin/conf/templates/, or copying them to a custom folder inside that and playing with PHP, which is simply stupid I think.
There should be a way to change/edit/add/remove the default location / {} directive inside "Addition nginx directives"