Conference Management System
XSLT Mako JavaScript Python CSS HTML
Latest commit 0e04adc Feb 14, 2016 @iseppi iseppi Merge pull request #503 from lod/crud_tests
Added functional testing for CRUD like controllers
Permalink
Failed to load latest commit information.
alembic New alembic file populates missing lookup tables Jan 24, 2016
bin
docs Zookeepr example API Documentation May 18, 2015
plugins/php-auth Replace PBKDF2 with SHA-256 (fix #336) May 3, 2015
wsgi
zk Added functional testing for CRUD like controllers Feb 8, 2016
zkpylons
.gitignore Clean out references to lca_info.py Aug 24, 2015
.testr.conf Add tox support to zookeepr Apr 27, 2015
.travis.yml Try and fix travis CI - add pwgen Feb 8, 2016
AUTHORS Update authors file May 2, 2015
INSTALL.md Added functional testing for CRUD like controllers Feb 8, 2016
LICENSE Legal stuff May 26, 2008
README.md
development.ini.sample created production sample config files May 3, 2015
production.ini.sample created production sample config files May 3, 2015
requirements.txt Updated install process and instructions Feb 6, 2016
setup.cfg Rewrite tests to allow them to work again Aug 27, 2015
setup.py Updated install process and instructions Feb 6, 2016
test-requirements.txt
test.ini Added functional testing for CRUD like controllers Feb 8, 2016
tox.ini Fix travis/tox issues on remote server Feb 7, 2016
tox.pip6.ini

README.md

zookeepr conference management

Build Status

zookeepr Readme

This document details how running zookeepr, how to run tests, and where to start hacking.

It assumes that you have the necessary dependencies installed and the development environment up and running. Please refer to INSTALL if you do not have your environment set up.

Running zookeepr

See INSTALL.md

  • Run paster serve -v --reload development.ini
  • Point your browser to http://localhost:5000/

Where to start hacking

  • Refer to the docstrings to familiarise yourself with the code
  • PEP-8 is your new god. PyLint can be used to enforce it. Refer to http://www.python.org/dev/peps/pep-0008/
    • Check the code against pep8 with tox -e pep8
  • Run tests with tox
  • Add yourself to the AUTHORS file if you think you're contributions are worthy :-)