Go to file
Reynir Björnsson 005431d6f6 team shifts: implement marking shifts for sale
A common occurence is that not enough people volunteer for shifts at
first, and then the few volunteers take all the shifts (too many). Then
late comers aren't able to take any shifts.

This commit implements a third state for shift assignment: for sale. A
shift marked for sale means the team member is able to take the shift if
need be, but would rather someone else takes the shift. Another team
member will be able to take shifts at the same time even if the required
number of people are met.

The current semantics is for-sale shifts are replaced eagerly. Another
possible implementation would be to only replace for-sale shifts if the
number of required people is met.
2021-08-26 14:32:16 +02:00
.github Upgrade to GitHub-native Dependabot 2021-04-29 19:31:35 +00:00
docker Initial docker-compose setup 2021-07-30 09:26:50 +02:00
schedule Event feedback (#451) 2020-02-22 14:50:09 +01:00
scripts Merge teamcomms branch. Refactor team app and add events app. 2018-04-09 23:11:05 +02:00
src team shifts: implement marking shifts for sale 2021-08-26 14:32:16 +02:00
.flake8 Facilities (#458) 2020-02-24 23:28:52 +01:00
.gitignore SpeakerAvailability, EventSession, autoscheduler, and other goodies (#497) 2020-06-03 21:18:06 +02:00
.gitmodules readd submodule with the correct branch 2017-04-02 20:21:12 +02:00
.isort.cfg add flake8 and isort to pre-commit config, make flake8 and isort happy (#441) 2020-02-12 13:10:41 +01:00
.pre-commit-config.yaml use --ignore-init-module-imports 2021-07-19 17:09:56 +02:00
.travis.yml we still need the user 2020-07-12 23:07:55 +02:00
LICENSE Add BSD 3-clause LICENSE file 2018-03-04 15:41:07 +01:00
README.md remove FK from ShopTicket to Order and replace with an FK to OrderProductRelation 2021-07-29 09:03:52 +02:00



Build Status codecov

Django project to power Bornhack. Features include news, villages, webshop, and more.

Development setup

Clone the repo

Clone with --recursive to include submodules:

git clone --recursive https://github.com/bornhack/bornhack-website

If you already cloned the repository without --recursive, you can change into the directory and add the submodules with:

git submodule update --init --recursive


Create a Python 3.7 virtual environment and activate it:

$ virtualenv venv -p python3.7
$ source venv/bin/activate

If you installed python3 using Homebrew on macOS, you will need to install virtualenv by running the following command first:

pip3 install virtualenv

System libraries

Install system dependencies (method depends on OS):

  • postgresql headers (for psycopg2):
    • Debian: libpq-dev
    • FreeBSD: databases/postgresql11-client
    • macOS: If using the PostgreSQL.app, the headers are included, only path needs to be added
  • libjpeg (for pdf generation)
    • Debian: libjpeg-dev
    • FreeBSD: graphics/jpeg-turbo
    • macOS: brew install libjpeg
  • libmagic (might already be installed)
    • macOS: brew install libmagic
  • wkhtmltopdf (also for pdf generation):
  • fonts
    • Debian: ?
    • FreeBSD: x11-fonts/webfonts
    • macOS: ?

Python packages

Install pip packages:

(venv) $ pip install -r src/requirements/dev.txt


You need to have a running Postgres instance (sqlite or mysql or others can't be used, because we use Postgres-specific fields and PostGIS/GeoDjango). Install Postgres and PostGIS, and add a database bornhack (or whichever you like) with some way for the application to connect to it, for instance adding a user with a password. Connect to the database as a superuser and run create extension postgis. The postgres version in production is 12 and the postgis version in production is 2.5. The minimum postgres version is 10, because we use GIST indexes on uuid fields (for ExclusionConstraints).

Configuration file

Copy dev environment settings file and change settings as needed:

(venv) $ cp src/bornhack/environment_settings.py.dist.dev src/bornhack/environment_settings.py

Edit the configuration file, setting up DATABASES matching your Postgres settings.


Is this a new installation? Initialize the database:

(venv) $ python src/manage.py migrate

Is this for local development? Bootstrap the database with dummy data and users:

(venv) $ python src/manage.py bootstrap_devsite


Is this for local development? Start the Django devserver:

(venv) $ python src/manage.py runserver

Otherwise start uwsgi or similar to serve the application.



Running tests

If your database user in your dev setup is not a postgres superuser you will encounter permission errors when the migrations try to create extensions "btree_gist" and "postgis". You can solve this by connecting to the "template1" database as the postgres superuser and creating the extensions there, which means they will be automatically loaded for all newly created databases.

Add a camp

Add a new camp by running:

(venv) $ python src/manage.py createcamp {camp-slug}

Then go to the admin interface to edit the camp details, adding the same slug that you just used and some current dates.

You can also specify details like:

  • A sponsors page, {camp-slug}_sponsors.html, to sponsors/templates.
  • A frontpage, {camp-slug}_camp_detail.html, to camps/templates.
  • A call for speakers page, {camp-slug}_call_for_speakers.html, to program/templates.
  • A static_src/img/{camp-slug}/logo and add two logos:
    • {camp-slug}-logo-large.png
    • {camp-slug}-logo-small.png