M
M
macwell2016-12-23 17:56:28
Django
macwell, 2016-12-23 17:56:28

Possible problems for several sites in the same environment, processed by one gunicorn?

Good day.
There is a local server on a bunch of nginx + gunicorn
It has three virtual environments (virtualenv). Each has its own set of applications.
The first and second projects are different, but in projects from 3 to 12 they are almost twins, they differ in nuances.
Each site is started from sysstemd by a separate service. The first two refer to their copy of gunicorn. But from 3 to 12, although they are launched by different services, they use one common virtualenv gunicron for them.
Now everything works locally, and there are no problems. But I would not like to know about the problems when all this will be put on the Internet. What problems can such a bunch of sites face? After googling for a couple of days, I did not find an answer. Is it really necessary to put each site in its own separate environment?
Project 1 / env / ... / gunicorn
/ project1_files www.site1.org
Project 2 / env / ... / gunicorn
/ project2_files www.site2.org
Project 3...12 / env / ... / gunicorn
/ project3_files somename.site3.org
...
/ project12_files someothername.site3.org

Answer the question

In order to leave comments, you need to log in

2 answer(s)
M
Mykola, 2016-12-24
@IKMOL

If I understood correctly, then for projects 3-12 you have one virtual environment, and for launching each (3-12) project there is a separate service. Then there shouldn't be any problems. Only if in some project you need a different version of the application that is not compatible with others and when updating the same application, you will break the rest.

M
macwell, 2016-12-25
@macwell

Yes, Wednesday 3-12 is one. Each project is launched by a separate service. If I change the composition of applications, then for all at once. These sites should continue to be "twins".

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question