Answer the question
In order to leave comments, you need to log in
Answer the question
In order to leave comments, you need to log in
Apache is a clumsy combine with a bunch of different modules, it can do everything, but in some places it is slow and eats a lot of resources, nginx is a fast web proxy, it can only work with static itself, but it does it very quickly, when adding different pieces it can replace apache in 99% of the projects are completely, if you are not sure, then it is better to use nginx as a frontend, apache - as a backend, get the strengths of the solutions, without the torment of finishing engines for nginx.
Nginx in most situations came to replace Apache, as it consumes less memory and does less work, but it does it more efficiently, which is especially true on a weak server, or under heavy load, a large number of connections (the same WebSockets).
For example, with PHP. There is a module for Apache2, and Nginx simply redirects requests to scripts to PHP-FPM, which is completely separate and has nothing to do with Nginx directly.
Since you have Django, Nginx will give statics, and requests to scripts, depending on the configuration on uwsgi or somewhere else, can be configured in different ways.
It makes sense to install Nginx as a frontend for Apache2 only as a transitional process, the fewer layers - the fewer points of failure and the higher the speed of work.
I would recommend Ubuntu, in my experience, it was the least hassle with the initial setup.
+ almost any problems are easily googled.
I liked the look of elementary os
the information there is already outdated, since the questions are 2-6 years old.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question