Skip to content


Repository files navigation


Bulletin is a communication platform aimed at small companies and groups. Check out the wiki for more information, or see what we have running so far at!

Bulletin is being developed by

  • Caylan Lee
  • Yoong Woo Kim
  • Andrew Davies
  • Ivan Darmansyah
  • Peter Weisbeck
  • Brian Oliphant
  • Kyle Boone

When this project is done, Caylan is getting everyone on the team a beer


  • /bulletin_project - project settings
  • /groups - model/view/form for groups
  • /inbox_notifications - code for the inbox and notification system
  • /posts - model/view/form for posts and comments
  • /registration - all the registration goodies including email
  • /session - session stuff
  • /static_resources - anything that python doesn't dynamically generate, e.g. css, js, img
    • when server is ran, you can find these files at /static/
  • /templates - template files

Virtual environment setup

Pretty much how Heroku says to do it. (for reference -

Project settings are currently setup for running on Heroku. In order to run locally on your machine, you may need to comment out the two lines at the bottom of the settings file for dj_database_url.

    cd Bulletin

    virtualenv PYENV --distribute

    source PYENV/bin/activate

At this point, the virtual environment has been activated. As the project continues to change, so too will the requirements, which must be stored in the requirements.txt file in order for Heroku to know which apps to install. To get up to speed if there is already a requirements.txt folder, run:

    pip install -r requirements.txt

If not, then install some base programs, and then create the requirements.txt file.

    pip install django psycopg2 dj-database-url   # for example.

If this is the first time running the virtual environment - you need to set up the database

    python syncdb

Then run the server

    python runserver

After installing any new apps, always make sure to update the new requirements:

    pip freeze > requirements.txt

For testing from the root using nose (be sure to comment out the email goodies portion of -but don't commit that change)

    ./ test


Keep everyone in the loop.






No releases published