Server configuration - What should non-root users pay attention to when using nginx+uwsgi to deploy Django programs separately?

Question

In the past, all the Django programs developed by my colleagues were handed over to me for deployment. Now the boss hopes that the programs developed by each can be deployed independently without having to go through me . The boss hopes that I can write a non-root user to deploy Django independently. document.
The root user and permissions are in my hands. Other colleagues are non-root accounts. Non-root accounts must use nginx uwsgi to deploy their own django.
Are there any pitfalls that need to be paid attention to during this process? Seek the guidance of the great God.

Answer 1

Except for the permission issues on the related directories, everything else is pretty much the same.
You can send Buddha to West: write a one-click installation script.

Answer 2

The best solution for this scenario is Docker.

1. Docker, previously used nginx to reverse to the corresponding instance based on the domain name or location.

2. If your operating system uses systemd, you can also use uwsgi emperor to manage uwsgi, and then nginx is managed by root for reverse generation.