> 
> **Possible Duplicate:**  
> 
> [How to manage local vs production settings in Django?](https://stackoverflow.com/questions/1626326/how-to-manage-local-vs-production-settings-in-django) 
> 
> 
> 

I have managed to deploy successfully a **Django project** on **Apache's Web Server** with `mod_wsgi`.

I would like some recommendations on how to manage multiple `settings.py` files. Right now I have one for development and one totally different for production (regarding DB parameters, static content localization, and stuff like that). My `settings.py` file is versioned (don't know if this is a good practise) and I deploy it with something like:

```
$ hg archive myproject.tbz2
$ cd /path/of/apache/web/project/location
$ bzip2 -db /home/myself/myproject/myproject.tbz2 | tar -xvf -

```

It's working OK. But I find myself manipulating multiple `settings.py` files.

I guess my question is: what are the best practices when deploying **DJANGO PROJECTS** regarding multiple `settings.py` file versions?