Submitted by Arvi89 on Fri, 08/08/2014 - 00:08
Hello :)
I know it's possible now to have either apache or nginx but I was wondering if at some point it will be possible to have both of them running at the same time (I don't really like cpanel but they do it really well).
Have a good day :)
Status:
Active
Comments
What's the goal of having both running? (I'm not ruling it out, I just can't think of a good use case.)
Submitted by Arvi89 on Fri, 08/08/2014 - 02:36 Comment #2
Nginx is faster than apache for static files, so for all css, js, images (and more) nginx will take care of it, the rest will be for apache.
Submitted by lp86 on Fri, 08/08/2014 - 13:01 Comment #3
I have them both running on one of my systems. I have two IP addresses, one runs apache and the other runs nginx. I had to change a few things manually but it works for the most part.
Otherwise you will have to run one of them on a different port, if you have a single IP address.
Submitted by Arvi89 on Fri, 08/08/2014 - 23:56 Comment #4
Yeah I did that in the past, both running on different port (and I can still do it), but I was wondering if virtualmin would make this easy by configuring everything automatically :)
Submitted by lp86 on Sat, 08/09/2014 - 00:01 Comment #5
At the same time, no.
To get them on separate IPs I only had to do a little tweaking to make sure there were no port conflicts.
If you are having speed issues, you should take a look at CloudFlare, it is free!
Submitted by Arvi89 on Sat, 08/09/2014 - 02:16 Comment #6
Oh, I'm not having speed issues, I use my server more like a place to make experimentation :)
I have cloudflare, but unfortunately, it's kinda blocked in China (depends of the day), so I can't really use it.
Submitted by wocul on Thu, 08/28/2014 - 20:04 Comment #7
I'd suggest to be careful here - while it has become fairly straightforward to set up nginx on a fresh system, it still involves quite a few manual steps - and at least so far, there's nothing in place to handle migrations between nginx<->apache vhosts as per: http://www.virtualmin.com/node/25176#comment-126690
In other words, nginx support -and especially apache interoperability- could still be considered to be relatively fragile - before people look at supporting more complex setups (such as e.g. reverse proxies, nginx for static content), it would be better to establish some well-defined interface for both HTTPDs and provide some kind of feature migration matrix to transparently convert compatible settings, but also recognize incompatible ones.
For the time being, it would already be a huge accomplishment to provide some kind of post-install wizard that allows to easily switch between apache and nginx while being aware of existing vhosts.