This project aims to kick start websites using pinax and satchmo, providing the core buildout.cfg and settings files to get new projects up and running.
The buildout will create a new website using the Django 1.1, pinax from git, and satchmo from hg.
There is a sample website project based off pinax social_project which intergrates the satchmo blocks into the base.html template.
- python-dev
- virtualenv
- git
- mercurial
- svn
Checkout this project to any path
Create newproject directory
mkdir newproject cd newprojectExecute create-site.sh
INSTALL_DIR/create-site.shEdit website/settings.py and set database details.
See the pinax and satchmo documentation for more configuration options.
http://www.satchmoproject.com/docs/svn/new_installation.html
You need to patch the django_friends models.py to resolve a conflict with a satchmo model.:
all_src/friends/models.pyedit #45:
users = models.ManyToManyField(User)add a related name:
users = models.ManyToManyField(User, related_name="contacts")syncdb
bin/django syncdbbuild_media
bin/django build_media --allrunserver using development settings
bin/django runserver
It may be helpful to load the satchmo sample data to have something to work with.
load sample locale text
bin/django satchmo_load_l10n
load sample store
bin/django satchmo_load_store
If you want to create a site using a modified buildout.cfg, put the buildout.cfg at the root of the project and run create-site.sh. The script will see your buildout.cfg and not overwrite it.
It is often a good idea to set a path for download-cache in the main buildout configuration. See http://pypi.python.org/pypi/zc.buildout#using-a-download-cache
By default buildout will store eggs in the eggs
directory of the project structure.
Using a common eggs directory allows projects to share the same eggs and makes builds much quicker.
Set the eggs-directory in the main buildout configuration to a writeable path. Make sure the path exists before you run buildout.
For more details on zc.buildout see: