I'm starting to think Apache isn't bad once again after pulling several hairs out of nginx config complications over the last 10 years.
If I just wanted to alias system path of '/some/path/' as 'https://domain/another_path/' in the URL, I don't know how to do that... Is it 'alias' or 'root' and should it have a slash at the end or not??? I usually just give up and symlink the directory on the system.
Same with proxy_pass on ending slash that is confusing.
And the priority of 'location' block is a nightmare until you Google enough to figure it out every time I configure nginx, not to mention the cryptic convention of ~ or ~^ and the likes and the fact you can't effectively nest location blocks.
https://news.ycombinator.com/item?id=30440028
I'm starting to think Apache isn't bad once again after pulling several hairs out of nginx config complications over the last 10 years.
If I just wanted to alias system path of '/some/path/' as 'https://domain/another_path/' in the URL, I don't know how to do that... Is it 'alias' or 'root' and should it have a slash at the end or not??? I usually just give up and symlink the directory on the system.
Same with proxy_pass on ending slash that is confusing.
And the priority of 'location' block is a nightmare until you Google enough to figure it out every time I configure nginx, not to mention the cryptic convention of ~ or ~^ and the likes and the fact you can't effectively nest location blocks.