**Ke**lder **R**egistratie **S**ysteem
Go to file
2020-08-04 18:45:48 +02:00
events Fix wachtlijst visual, add not-null constraint 2020-08-04 17:36:37 +02:00
KeRS Add static config 2020-07-25 15:07:06 +02:00
oauth Remove unneeded code 2020-07-25 13:06:54 +02:00
scripts Format script 2020-07-25 12:25:20 +02:00
static Make 'Uitschrijven' button red to distinct enrolled events 2020-07-27 20:17:55 +02:00
templates Add link to kelderregels in the footer 2020-08-04 18:45:48 +02:00
users Add timeslots 2020-08-04 03:32:02 +02:00
.editorconfig Add editorconfig 2020-07-22 01:46:38 +02:00
.gitignore add initial models 2020-07-21 22:24:45 +02:00
docker-compose.yml Add static config 2020-07-25 15:07:06 +02:00
Dockerfile Add specific versions for docker images 2020-07-24 22:40:38 +02:00
Makefile Remove migration rewriting from Makefile 2020-07-26 00:58:47 +02:00
manage.py Initial commit 2020-07-21 21:20:23 +02:00
README.md Add development environment docs in README 2020-07-25 12:40:57 +02:00
requirements.txt Add code highlighting 2020-08-04 04:27:30 +02:00
web.env Add static config 2020-07-25 15:07:06 +02:00

KeRS - Kelderregistratiesysteem

Development

Install Python and virtualenv if not already available.

Choose between:

  • SQLite3 (easier to set up, works because we don't do advanced DB shizzlery or custom SQL yet)
  • MySQL/MariaDB (used in production, less chance of weird bugs due to compatibility problems between SQLite3 and MariaDB)

If you choose SQLite3, set the environment variable KERS_DB_BACKEND to sqlite3. To do so, you can add export KERS_DB_BACKEND=sqlite3 to your shell's init file (e.g. ~/.bashrc) and restart your shell.

If you choose MySQL/MariaDB, set up the server, and look in KeRS/settings.py for the possible environment variables you can set (e.g. DATABASE_NAME).

Set up the development environment:

python -m virtualenv venv
venv/bin/pip install -r requirements
make migrate

To run the development server:

make