Contents
We're using github to track the code and the list of issues here.
If you can help, please follow this process:
- Read over the issues. if you see one you want to work on, comment on the issue, saying "I'll take this" or something to that effect. For extra credit, discuss your approach.
- Fork the repository.
- Fix it! No, there's no awesome set of unit tests, but thanks for asking, and I agree, that would be really nice :)
- Send us a pull request.
- We'll review and merge and then close the issue.
In step 1, if you see that somebody else already started work on the issue you are interested in, that's great! Clone or fork their forked repository, and then help them out. Working with internet strangers is a great way to make new friends.
The PyOhio 2015 website being built by Caktus Consulting Group, based on Pinax 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.
PyOhio 2015 is built on top of Pinax Symposion but may have customizations that may make things more difficult for you.
This documentation assume you have the following installed:
- `pip >= 1.2.1 <http://www.pip-installer.org/>`_ - `virtualenv >= 1.11 <http://www.virtualenv.org/>`_ - `virtualenvwrapper >= 3.6 <http://pypi.python.org/pypi/virtualenvwrapper>`_
Create a new virtualenv and install the necessary requirements:
mkvirtualenv --distribute pyohio --python=python2.7 $VIRTUAL_ENV/bin/pip install -r $PWD/requirements/dev.txt
(For production, install -r requirements/base.txt).
Then create a local settings file and set your DJANGO_SETTINGS_MODULE to use it:
cp pyohio/settings/local.py.example pyohio/settings/local.py echo "export DJANGO_SETTINGS_MODULE=pyohio.settings.local" >> $VIRTUAL_ENV/bin/postactivate echo "unset DJANGO_SETTINGS_MODULE" >> $VIRTUAL_ENV/bin/postdeactivate
Exit the virtualenv and reactivate it to activate the settings just changed:
deactivate workon pyohio
Setup the postgres database and load fixtures:
createdb pyohio python manage.py syncdb python manage.py migrate python manage.py loaddata fixtures/*
Create a user account:
python manage.py createsuperuser
Run local server:
python manage.py runserver
Here's how to get a local copy of the database:
$ gondor sqldump primary > /tmp/pyohio2015.pg_dump $ dropdb pyohio2015 $ createdb pyohio2015 $ psql pyohio2015 < /tmp/pyohio2015.pg_dump
for glory!
Copy database instance from previous year locally:
gondor sqldump primary > pyohio-<year>-db.sql
Copy instance variables:
gondor env:get
Copy site media (user images, sponsor logos, etc.):
scp -r <old-instance-id>@ssh.gondor.io:site_media/media /tmp/media
Update site to new year:
vi gondor.yml
Create new instances for the new site:
gondor create --kind=production primary gondor create --kind=dev dev
Deploy database dump to new year instance:
gondor manage dev database:load pyohio-<year>-db.sql gondor manage primary database:load pyohio-<year>-db.sql
Set instance variables to new year instance:
gondor end:set dev SITE_ID=2 ... gondor env:set primary SITE_ID=3 ...
Deploy site media:
scp -r /tmp/media/* <new-instance-id>@ssh.gondor.io:site_media/media
Deploy code to new year instance:
gondor deploy <primary|dev> <HEAD|master|git commit id>
python manage.py test pyohio
Right now, if a talk is accepted, if the speaker updates their talk, the text on the schedule will not show those updates.
There is a github issue for this here: pyohio#51
In the meantime, here's how to fix this problem:
Go to the review page for a talk and change the status from Accepted to Standby.
This has a side effect of removing the talk from the schedule.
Immediately change the talk back from Standby to Accepted.
Go to the edit schedule page:
and then find the plus symbol where the talk used to be. Click that and in the popup modal, select the talk and add it to the schedule.
You have to do that every time somebody updates their proposal.