PyCon 2014 website being built by Caktus Consulting Group, based on symposion.
Rather than use this as the basis for your conference site directly, you should instead look at https://github.com/pinax/symposion which was designed for reuse.
PyCon 2014 is built on top of Pinax Symposion but may have customizations that will just make things more difficult for you.
Installation instructions are in this README. There's more documentation at https://readthedocs.org/projects/pycon/
Create a new virtualenv and activate it.
Install the requirements for running and testing locally:
pip install -r requirements/dev.txt
(For production, install -r requirements/project.txt).
Compile the locale
python setup.py compile_catalog -l fr -d locale -D django
Copy
pycon/settings/local.py-example
topycon/settings/local.py
.Edit
pycon/settings/local.py
according to the comments. Note that you will have to edit it; by default everything there is commented out.Create your database. (This is assuming you haven't changed the default database settings.):
createdb pycon2014
Initialize the database and apply migrations:
python manage.py syncdb --migrate
You could run the local server at this point, but it turns out that with an empty database, a lot of things don't work. If you have ssh access to the staging server, an easy solution is to copy the database and media from there:
$ fab staging get_db_dump:pycon2014 $ fab staging get_media
Change
pycon2014
in that first command to the name of your local database.Run local server:
python manage.py runserver
Start with instructions above, except:
- Install requirements from requirements/project.txt instead of requirements/dev.txt
- Stop when you get to Run local server
Edit
pycon/settings/local.py
to make sure DEBUG=False.Add an appropriate ALLOWED_HOSTS setting (https://docs.djangoproject.com/en/1.5/ref/settings/#std:setting-ALLOWED_HOSTS)
Install
lessc
(Go to http://lesscss.org and search for "Server-side usage")Pre-compress everything by running:
python manage.py compress --force
That will write compressed css and js files under site_media
Gather the static files:
python manage.py collectstatic --noinput
Arrange to serve the site_media directory as
/2014/site_media/whatever
. E.g.site_media/foo.html
would be at/2014/site_media/foo.html
.Arrange to serve the wsgi application in
symposion/wsgi.py
at/
, running with the same virtualenv (or equivalent). It will only handle URLs starting with/2014
though, so you don't have to pass it any other requests.
python manage.py test
There's more documentation under docs/
.