The dusken-prototype from edb-gjengen

dusken-prototype's Introduction

#D.U.S.K.E.N

Dårlig Utrustet Studentsystem som Kommer til å Endre Norge.

You can find the documentation at dusken.readthedocs.org.

Installation

sudo apt-get install python-virtualenv python-dev postgresql libpq-dev pgadmin3
cd dusken
virtualenv --distribute venv
. venv/bin/activate
pip install -r requirements.txt
cd dusken
cp settings-sample.py settings.py
# Edit database settings (sqlite3 is easiest to setup, but postgresql is recommended. See discussion below.)
cd ..
./manage.py syncdb --all
./manage.py runserver

If Django is running under Apache and mod_wsgi you need WSGIPassAuthorization On in your VirtualHost.

See the EDB wiki for more info.

Development tasks

# Reset DB
python manage.py reset_db --router=default --noinput && python manage.py syncdb --all

# Generate Fixtures for Test
python manage.py dumpdata dusken.<model> -n --indent=4 > dusken/fixtures/<model>.json

# Database Diagram Generation
sudo apt-get install graphviz libgraphviz-dev # system requirements
pip install pygraphviz django-extensions # python requirements
python manage.py graph_models -o diagramfile.png dusken auth

Development references

Tastypie

Database

Design references

A similar data model might allready exist out there, somewhere.

SQLite3 vs PostgreSQL

SQLite runs tests much faster
SQLite does not check foreign key constraints out of the box [1] [FIXED].
SQLite is easier to set up.
SQLite does not provide environment parity between development and production [2].

Recommend Projects