Comments on: Nginx & Django on Webfaction – Part 2

By: Erik Mulberry

Erik Mulberry — Fri, 18 Nov 2011 09:28:03 +0000

Wow that was unusual. I just wrote an exceedingly long comment but after I clicked submit my comment did not show up. Grrrr… nicely I’m not writing all that above again. Irrespective, just wanted to say excellent weblog!

By: ashley

ashley — Thu, 06 Oct 2011 15:32:45 +0000

Thanks for the tutorial. Together with david’s i wrote a nice fabric script that automates django/gunicorn deployments on webfaction :) https://github.com/ashwoods/webfaction-django-fabfile

By: Darron Reveles

Darron Reveles — Mon, 28 Mar 2011 07:12:52 +0000

would you please elaborate on this, I would like a little more info, thanks

By: Orion Vianna

Orion Vianna — Tue, 04 Jan 2011 04:19:26 +0000

You can also force the web interface to use HTTPS
by adding
env['HTTPS'] = env.get(‘HTTP_REFERER’,”).startswith(‘https’) and ‘ON’

to cgi_environment() method in file http.py at line 322

Thanks to Rob Guttman for this :o)
http://www.mail-archive.com/supervisor-users@lists.supervisord.org/msg00564.html

By: Cesar Canassa

Cesar Canassa — Sat, 06 Nov 2010 02:46:48 +0000

Hey, thanks for the tutorial. I just installed a Flask + Nginx application in Webfaction using your approach. Worked very well.

As Hernan said, the Crontab part is missing the ‘start’:

*/10 * * * * cd ~/; ./start_supervisor.sh start

By: panchicore

panchicore — Thu, 23 Sep 2010 02:51:48 +0000

Hi, nice post!.

where is “our nginx.conf” ?

By: JONES

JONES — Mon, 26 Apr 2010 11:01:07 +0000

Nice approach. Thank you for your insight.

By: Andy Baker

Andy Baker — Mon, 15 Feb 2010 18:19:13 +0000

Your easy_install supervisor line won’t necessarily put supervisor into the correct directory as it specify the same lib and bin locations as you did in part 1 of the tutorial.

By: Richard Cooper

Richard Cooper — Mon, 08 Feb 2010 20:27:55 +0000

Hi Andy,
I was just looking at this today as I’m working on a script to enable this to be setup via the Webfaction control panel using their API. I’ll update the post with this in a day or so and give you the credit :)

Thanks for your interest.
Richard.

By: Andy Baker

Andy Baker — Mon, 08 Feb 2010 17:49:51 +0000

Yep. That was it. I’ve still got the bad habits picked up from the Django tutorial and all my projects are called ‘myproject’ ;-)

Assuming a project called ‘myproject’ then as well as:
sys.path.append(‘/home//webapps//myproject/’)

if you add:
sys.path.append(‘/home//webapps//’)

then that you can have imports like either:
import myproject.something
or just:
import something

and the urls line can stay as:
ROOT_URLCONF = ‘myproject.urls’

It’s would be better to fix my code so that I avoided explicitly referencing ‘myproject’ but quite a few tutorials do this and so does manage.py’s

It’s better not to do either of these things but I’ve fallen into bad habits and I’m sure others have too!