Welcome to Zamboni’s documentation!¶
If you want to build a completely different site with all the same Django optimizations for security, scalability, L10n, and ease of use, check out Mozilla’s Playdoh starter kit.
- Access Control Lists
- Marketplace API
- Django, the Good Parts
- Working on the Mobile Site
- Setting Up Payments for Apps and Add-ons
- Zamboni in Production
- Templating with Jinja2
- Translating Fields on Models
Did you break something recently? Are you wondering which commit started the problem?
git bisect start git bisect bad git bisect good <master> # Put the known-good commit here. git bisect run fab test git bisect reset
Git will churn for a while, running tests, and will eventually tell you where you suck. See the git-bisect man page for more details.
Run your tests like this:
python manage.py test --noinput --logging-clear-handlers
- --noinput tells Django not to ask about creating or destroying test databases.
- --logging-clear-handlers tells nose that you don’t want to see any logging output. Without this, our debug logging will spew all over your console during test runs. This can be useful for debugging, but it’s not that great most of the time. See the docs for more stuff you can do with nose and logging.
There’s also a few useful makefile targets like test, tdd and test_force_db:
To simply build the docs:
If you’re working on the docs, use make loop to keep your built pages up-to-date:
cd docs make loop