3 ms·
If you have anything to do with Drupal (and possibly Wordpress) as well, you might run into issues. At least concerning Drupal, a lot of plugins require change
by mercer 12y ago
If you have anything to do with Drupal (and possibly Wordpress) as well, you might run into issues.
At least concerning Drupal, a lot of plugins require changes to the .htaccess file(s), and at least when I tried, this was hard to translate to nginx.
But there are some .htaccess to nginx converters, so I'm not sure if that is a big issue at this time.
And as others have said, you might find the nginx approach to be much more comfortable than .htaccess. I did.
- vegardx 12y agoDrupal works flawlessly with Nginx[1], and there is little magic involved. You even have good handling of private files, permission and such. There's only a few modules that require changes to the default ".htaccess" (basically just overriding Apache default logic) of Drupal, like the module Boost. But since Nginx can serve as both a application server and reverse proxy, you can have the best of both worlds, without doing hack-y things like Boost, which basically generates a lot of static files. You don't want to use those converters, as they usually rely heavily on ifs, which is a bad thing, when things normally can be handled pretty well with the "try_files"-directive. [1] I've been using it in my stack for a couple of dozen Drupal sites for about two years now.
- mercer 12y agoThanks for the information! I've mostly moved away from Drupal, but I still maintain a number of sites for some clients. Good to know a move to nginx is an option.