You should begin by reading the concepts page.
Once you’re familiar with the concepts which Django-in-a-Box (DiaB) is based upon, you should move onto the directory layout documentation so you know where everything goes and where to look for certain things. The tools section will give you information on the tools which DiaB comes with by default, and the
etc/ directory documentation provides a reference for the plaintext configuration machinery in DiaB. Finally, you can read the quickstart document to get started straight away.
For helpful information on site administration, consult the README which comes with every DiaB site.
Django-in-a-Box currently only runs on UNIX-based systems. That means Mac OS X, *BSD, GNU/Linux and a few others. Unfortunately, I have neither the time, the resources nor the inclination to work around the issues which Windows presents; if you want to fork the project and add support yourself, go ahead.
To run Django-in-a-Box, you’ll need to install a couple of applications. Most of the necessary Python libraries are automatically installed by DiaB, but in order to run the bootstrap the process, you’ll need:
- Python (included with almost every UNIX system today)
- Paver (
- virtualenv (
- lighttpd (see its page in the tools documentation)
Django-in-a-Box was built to work well with Version Control Systems. There are just a couple of things to remember:
The project directory should be under version control, but not the site directory. The contents of the site directory will vary wildly from deployment to deployment, but the project directory should remain constant.
You'll want to tell your VCS to ignore certain types of file: compiled
.DS_Storefiles, and the
etc/symlink in the project directory. On Mercurial, this is done with a
.hgignorefile; Git uses a
.gitignore, and Subversion uses