Comments on: Nginx & Django on Webfaction – Part 2

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!

By: Richard Cooper

Richard Cooper — Sun, 07 Feb 2010 15:04:02 +0000

probably something to do with the sys.path.append lines in runserver.py
I’d look there first if you have path issues. :)

Let me know if you get it fixed and I’ll update the post with any changes….

By: Andy Baker

Andy Baker — Sat, 06 Feb 2010 16:29:45 +0000

What’s the cause of this step?:

ROOT_URLCONF = ‘urls’

The reason I’m asking is I’m getting a bunch of other import errors in an app that worked fine without nginx and that line seems to imply some funkiness with my Python path.

By: Hernan

Hernan — Fri, 13 Nov 2009 06:21:42 +0000

Also found out that

command = /home/mystartp/webapps/fcgi/accuputt/runserver.py

was not working for me, I had to do

command = python2.5 /home/mystartp/webapps/fcgi/accuputt/runserver.py

By: Hernan

Hernan — Fri, 13 Nov 2009 05:05:45 +0000

shouldn’t the crontab be like:

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

and

./start_supervisor.sh start

By: Richard Cooper

Richard Cooper — Sun, 27 Sep 2009 21:39:24 +0000

@tim

If you use “easy-install-2.5 supervisor” on webfaction it will install it in the correct directory (if you are worried then cd ~/ to take you to your home folder first.)

I’ll post something in the morning (UK time) about mounting the supervisor on a sub domain. But basically you have to create a new website record in the control panel to link the supervisor App (created at the beginning of this post) to the sub-domain.

By: tim

tim — Sun, 27 Sep 2009 21:11:14 +0000

Which folder do you install supervisor in? Also can you explain how to mount the process of supervisor on a subdomain?