Turbogears2 on Dreamhost

It has been almost two years since I tested Turbogears 1 on Dreamhost. Back then it was quite difficult for me to get it running. But some additional personal experience and improvements in Turbogears2 have made it a breeze. I tested with Turbogears 2.0 although I upgraded to 2.1a2 at some point.

First you need to get virtualenv installed, which is pretty simple after you have downloaded and unpacked the source tarball: python2.5 virtualenv.py $HOME. (I wanted it installed in $HOME, but you could use alternative locations as well.) This will install setuptools, but somehow not virtualenv. Then you just do easy_install virtualenv. You will also need PasteDeploy so do: easy_install PasteDeploy.

Next steps might be different for installing a Turbogears2 egg/application, but I used these instructions to install the wiki-20 tutorial in development mode. (To install a properly packaged app you probably just need to do: easy_install app_tarball; paster make-config yourapp production.ini and follow the instructions from FastCGI onwards.)

After that you just follow tg2 automatic installation instructions.

Then use paster quickstart to create a new project template. cd to the created directory, and run python setup.py develop to download any missing dependencies and set things up for debugging and development.

Edit as instructed in the tutorial. Then python setup-app development.ini.

After that it is time to create the production ini: paster make-config Wiki20 production.ini.

Next step is getting this running with FastCGI. Create wiki20.fcgi in the webroot directory:

from fcgi import WSGIServer # you could also use flup etc.
from paste.deploy import loadapp
real_app = loadapp('config:/home/your-username/path/to/production.ini')
def myapp(environ, start_response):
    environ['SCRIPT_NAME'] =  # get rid of the .fcgi in urls
    return real_app(environ, start_response)
server = WSGIServer(myapp)

There are a couple of points of note here:

  • I am using fcgi.py which seems to be slightly more reliable than flup on Dreamhost. You’d better edit fcgi.py so that you won’t show private information to everyone in case of errors.
  • There is a trick to get rid of the .fcgi part from the URLs.

Next we’ll need a .htaccess file:

# Enable Dreamhost stats
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_URI} ^/(stats|failed_auth\.html).*$ [NC]
RewriteRule . - [L]
# FastCGI
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^wiki20\.fcgi/ - [L]
RewriteRule ^(.*)$ wiki20.fcgi/$1 [L]

Now when you go to your site, first time it is going to take a while to load your app, but after that things will be snappy as long as the app stays in memory.

Similar Posts:

    None Found


  1. jeffrey:

    hi, i’m using hostmonster, i think it’s very similar to Dreamhost.
    but i following your instructions, the finally i got following error message:

    : [Errno 20] Not a directory: ‘/home/jeffreyx/.local/lib/python2.6/site-packages/badtg-0.1dev-py2.6.egg/badtg/controllers’
    args = (20, ‘Not a directory’)
    errno = 20
    filename = ‘/home/jeffreyx/.local/lib/python2.6/site-packages/badtg-0.1dev-py2.6.egg/badtg/controllers’
    message = ”
    strerror = ‘Not a directory’

    i use tg2.1a1 flup1.0.2 and python2.6, the project name is badtg
    it seems the egg is not install correctly, but i can import badtg.model in python console.
    how to solve this problem.
    thank you very much.

    BTW: i’ve run django app successfully in hostmonster.

  2. jeffrey:

    OK, it’s fine!
    sorry for bothering.