Application de gestion de l'organisation d'évènements et de l'inventaire du matériel
Find a file
2017-07-25 14:07:20 +02:00
communication Migrations 2017-07-21 16:20:39 +02:00
equipment Migrations 2017-07-21 16:20:39 +02:00
evenementiel small fixes 2017-07-23 16:21:11 +02:00
event Activity parent nullable 2017-07-25 14:07:20 +02:00
provisioning Merge branch 'master' into Kerl/dev_env 2017-05-17 10:33:05 +01:00
shared Use EventSpecificMixin for event-specific models 2017-07-18 19:08:09 +02:00
users small fixes 2017-07-23 16:21:11 +02:00
.gitignore now Aufinal should be satistied 2017-07-20 15:22:42 +02:00
manage.py venv works fine 2017-07-20 15:18:29 +02:00
README.md Roll back to Debian8 for the vagrant VM 2017-05-18 14:19:37 +01:00
requirements-devel.txt Split the settings in two files, secrets system 2017-05-16 19:52:59 +01:00
requirements.txt Refactor communication models 2017-07-17 17:47:34 +02:00
Vagrantfile Roll back to Debian8 for the vagrant VM 2017-05-18 14:19:37 +01:00

Gestion Événementiel

Vagrant

Production-like environment

Our Vagrant setup provides two ways of running GestionEvenementiel:

  1. You can run the usual development server with:

    python manage.py runserver 0.0.0.0:8000

    Please note that we specify the interface 0.0.0.0 to make the server reachable outside the VM at address localhost:8000

  2. A second instance, more similar to the production environment, runs with Daphne and nginx in the VM. It runs permanently by default but is not reloaded when you update the code. To restart this server, type:

    python manage.py collectstatic --noinput sudo systemctl restart daphne.service worker.service

    To query this instance from the host, you have to use the address localhost:8080. It is a good practice to ensure that this instance works before submitting a merge request (although it might break sometimes).