Application de gestion de l'organisation d'évènements et de l'inventaire du matériel
Find a file
2018-08-20 16:02:42 +02:00
api Update AppConfigs 2017-08-19 15:36:45 +02:00
communication Update AppConfigs 2017-08-19 15:36:45 +02:00
equipment add migrations 2018-08-20 13:24:47 +02:00
event event admin base 2018-08-20 16:02:42 +02:00
poulpe rename app evenementiel to poulpe 2018-08-20 14:32:52 +02:00
provisioning rename app evenementiel to poulpe 2018-08-20 14:32:52 +02:00
shared equipment main views 2018-08-20 13:17:10 +02:00
users Update AppConfigs 2017-08-19 15:36:45 +02:00
.gitignore rename app evenementiel to poulpe 2018-08-20 14:32:52 +02:00
manage.py rename app evenementiel to poulpe 2018-08-20 14:32:52 +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-prod.txt prod requirements 2018-08-06 10:19:48 +02:00
requirements.txt equipment main views 2018-08-20 13:17:10 +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).