Helios server
Python JavaScript Other
Pull request Compare This branch is 23 commits ahead, 292 commits behind benadida:master.
Latest commit ca7c8c9 Feb 20, 2013
glondu Advertise dummy auth
As per Henrik Ingo's suggestion.
Permalink
Failed to load latest commit information.
helios
helios_auth
heliosbooth In ZK proofs, responses should be taken modulo q Feb 1, 2013
heliosverifier In ZK proofs, responses should be taken modulo q Feb 1, 2013
selenium added first selenium test Feb 15, 2011
server_ui HTML compliance Feb 1, 2013
templates first commit of iacr helios Jul 26, 2009
.gitignore
CONTRIBUTORS.txt merged in Emily Stark's SJCL integration, tweaked a bit Jun 19, 2011
QUICKSTART.md
README.txt added more true integration tests with dependencey django-webtest and… Jun 5, 2011
__init__.py first commit of iacr helios Jul 26, 2009
autoretry.py
deploy-staging.sh added ability to email a single user Oct 8, 2011
django-gae.py
django.wsgi updated path in django Aug 7, 2010
email_debug.py improved tasks and added email debugging Aug 5, 2010
fabfile.py updated booth Jun 26, 2011
manage.py batch of updates for puredjango May 2, 2010
reset.sh
settings.py Advertise dummy auth Feb 20, 2013
urls.py Fix with django 1.3 Jun 13, 2012

README.txt

The Helios Election Server
==========================

LICENSE: this code is released under the GPL v3 or later.

NEEDS:
- as of Helios v3.1, requires Django 1.2.5+

- http://github.com/openid/python-openid
- rabbitmq 1.8
-- http://www.rabbitmq.com/debian.html
-- update the deb source
-- apt-get install rabbitmq-server

- celery 2.0.2 and django-celery 2.0.2 for async jobs
-- http://celeryq.org
-- apt-get install python-setuptools
-- easy_install celery
-- easy_install django-celery

- South for schema migration
-- easy_install South

- django-webtest for testing
-- http://pypi.python.org/pypi/django-webtest
-- easy_install webtest
-- easy_install django-webtest

GETTING SOUTH WORKING ON EXISTING INSTALL
- as of Helios v3.0.4, we're using South to migrate data models
- if you've already loaded the data model beforehand, you need to tell South that you've migrated appropriately
- so, if your data model is up to date with the code, do

python manage.py syncdb

to get the south db models set up, and then:

python manage.py migrate --list

- if there are some unchecked migrations, and you are SURE that your database is up to date with the models (which should be the case if you're on a v3.0.x version), then do

python manage.py migrate --fake