This repository has been archived on 2025-06-17. You can view files and clone it. You cannot open issues or pull requests or push a commit.
2013-12-04 22:14:34 +01:00
2013-12-04 22:14:34 +01:00
2013-10-15 21:45:52 +02:00
2013-09-25 14:05:56 +02:00
2013-10-21 15:53:55 +02:00
2013-05-19 16:19:03 +02:00
2013-11-30 12:47:17 +01:00

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

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

Build Status

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

Installation

Manual install:

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
./manage.py runserver

See the EDB wiki for more info.

TODO Vagrant install:

Download latest version of Vagrant from downloads.vagrantup.com and then do:

vagrant plugin install vagrant-salt
vagrant up
vagrant ssh

Test coverage

pip install coverage
coverage run --source='dusken' manage.py test dusken
coverage report -m

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 
pip install pygraphviz django-extensions
python manage.py graph_models -o diagramfile.png dusken

Design References

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

Developer References

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].
S
Description
Dårlig Utrustet Studentsystem som Kommer til å Endre Norge
Readme
229 KiB
0 Stars 9 Watchers 0 Forks
Languages
Python 96.1%
SaltStack 2.8%
Shell 1.1%