You bring your web app in a
- GitHub repo
- App Platform handles deployments and builds
- DNS, HTTPS, CDN, DDoS Mitigation, Vertical Scaling, Horizontal Scaling, and more.
Mezzanine deployment - .virtualenv missing Mezzanine after running fab install/create/deploy/all
Hey all! Have gotten past some previous issues, and managed to upload the project through Git. Now when I want to testrun the server using gunicorn, like cd into the project folder and run python manage.py runserver as usual, I get the error:
File “manage.py”, line 7, in <module>
from mezzanine.utils.conf import realprojectname
ModuleNotFoundError: No module named ‘mezzanine’
So it’s my understanding when i run fab all, or the individual sequences like fab install and create, that it should automatically create a venv with packages according to the requirements.txt
The requirements.txt is up to date, and has mezzanine listed in it.
I’m running on windows 7, but doubt that has any meaning at this point when the resources are pushed onto the droplet, and I can clearly see through FTP that Python is installed in the .virtualenvs folder, but none of the other necessary resources.
I tried running “pip install mezzanine” while having the virtual env activated through SSH, but can’t see where it installed it, definitely not the virtualenv’s lib folder.
How can I properly get all the necessary packages (mezzanine) up to the droplet? Thanks for reading.
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.×