Hello everyone,
I have deployed Mezzanine CMS on digital ocean Debian droplet. And its running at http://{droplet-ip}:8000. But trying to deploy for production means Mezzanine CMS should run at http://{droplet-ip} and background process should be taken care by nginx, gunicorn.
Followed the Digital ocean documentation for setting-up production site with nginx but no luck! I have no idea where i’m making mistake. Would be greatful if someone can help me with steps - how to configure nginx and other require dependencies for production.
Thank you so much.
Rgds, Sunil
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Click below to sign up and get $100 of credit to try our products over 60 days!
Without knowing exactly what you tried, it’s hard to give you a very detailed answer, but hopefully this points you in the right direction.
A Nginx reverse proxy configuration would normally look something like this:
Though if you are using Mezzanine, you might want to consider using Fabric to handle your deployment needs. Each Mezzanine project should come with a
fabfile.py
that will automate setting up a stanadrd Nginx/Gunicorn/Postgres stack. Check out the Mezzanine docs.Youll need to add some server specific configurable variables in the project’s
settings.py
module. Here’s an example: