Question

I recently setup a deployment solution for my Django project using Fabric. The basic workflow being:

1. Check out the latest source from git on the server.
2. Copy it to a ‘releases’ directory and add a timestamp to the directory name.
3. Update the ‘current’ symlink to point to the latest build.

This works just fine, only problem is, since the top level directory is a symlink called ‘current’ and that points to a folder like ‘project_name_2010_10_04’ ALL of the following Import statements will fail:

from project_name.app import models

…

INSTALLED_APPS = (
    'project_name.app'
)

…

urlpatterns = patterns('',
    (r'^$', 'project_name.app.views.index'),
)

So the solution I’ve found is to remove EVERY single reference to ‘project_name’ in my project, and the app seems to deploy and work just fine (for now). But this doesn’t seem like the right way to solve the problem… mostly because in a newly created Django project the ‘urls.py’, ‘settings.py’ all reference the project name by default and also various Django documentation mentions using the project name for various things.

So to sum up my problem, is there a way to specify a package name that differs from the actual directory name?

Answer 1

Simply put, you really shouldn’t be using your project name hard-coded anywhere, especially in specific apps, as it just completely breaks their portability and re-usability.