It's probably a bad idea to put your virtualenv in /root, this is the root user's home dir. I usually create a specific user that will be running my mezzanine projects. This way you are not running gunicorn as root, but as a normal user. Really, it's a best practice to reduce the number of services running as root to as few as possible. I am fairly certain that the fabfile assumes you are running as a normal user which may account for the permission issue(s).
Cheers, Matt On Sun, Apr 27, 2014 at 11:41 PM, Jared Nielsen <[email protected]> wrote: > So I deleted my Droplet and started fresh, following Josh's tutorial to the > T. > > Devian 7 x64 > Created a fresh local mezzanine project. > But I didn't have a live_settings.py file in /deploy. > So I copied one from an older project. > > Why wasn't a live_settings.py generated? Would one be generated later? > There is a local_settings.py.templates that contains the same information. > > I proceeded, ran fab all and got hung up on the virtualenv. Here's my error: > >> [oulipy.com] out: /bin/bash: line 0: cd: /root/venv: Permission denied >> [oulipy.com] out: >> >> Fatal error: run() received nonzero return code 1 while executing! >> >> Requested: virtualenv oulipy --distribute >> Executed: /bin/bash -l -c "cd /root/venv && virtualenv oulipy >> --distribute" >> >> Aborting. >> Disconnecting from oulipy.com... done. > > > At first I was getting an error that the directory didn't exist, so I > created it. Then I tried changing permissions on the directory. But I'm > stuck here. > Any help is greatly appreciated. > > > > On Sunday, April 27, 2014 8:58:26 PM UTC-6, Jared Nielsen wrote: >> >> Everything about Mezzanine is awesome. Except deployment. >> I'm new to Mezzanine and Django and struggling to get my site deployed. >> I chose Digital Ocean because for their price, their documentation and >> Josh's fab post: >> http://bitofpixels.com/blog/deploying-mezzanine-to-digital-ocean-using-the-included-fabfile/ >> >> I'm attempting two approaches. >> 1. The first is following the Digital Ocean guidelines, beginning with >> this tutorial: >> >> https://www.digitalocean.com/community/articles/how-to-install-and-get-started-with-django-based-mezzanine-cms-on-ubuntu >> >> I create a droplet, login, create a virtualenv, pip install mezzanine and >> pillow, mezzanine-project, createdb, runserver like this: python manage.py >> runserver 0.0.0.0:8000 >> No problem. Fresh Mezzanine project in my browser. >> >> So I create a new virtualenv and directory, git clone my mezzanine >> project, install requirements, runserver: >> >>> django.core.exceptions.ImproperlyConfigured: The SECRET_KEY setting must >>> not be empty. >> >> >> So I create a local_settings.py file and add a SECRET_KEY. >> >> Then runserver, and I get this error at http://<my_droplet>:8000 >>> >>> Bad Request (400) >> >> >> Am I wrong to think that I can run my Mezzanine project with a development >> server? >> >> >> Moving on... >> >> 2. Following Josh's tutorial: >> http://bitofpixels.com/blog/deploying-mezzanine-to-digital-ocean-using-the-included-fabfile/ >> >> I fill in all my settings and when I run fab all, I get: >> >>> [jarednielsen.com] Executing task 'all' >>> >>> --- >>> all >>> --- >>> >>> >>> ------- >>> install >>> ------- >>> >>> >>> $ cat /etc/default/locale -> >>> >>> [jarednielsen.com] Login password for 'jarednielsen': >> >> >> I enter my password and it times out for a moment, then asks for my >> password again and again. >> >> What am I missing here? >> >> Many thanks in advance. >> >> >> >> > -- > You received this message because you are subscribed to the Google Groups > "Mezzanine Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- M. Summers "...there are no rules here -- we're trying to accomplish something." - Thomas A. Edison -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
