Application de gestion de l'organisation d'évènements et de l'inventaire du matériel
Find a file
2018-10-11 09:48:03 +02:00
api Update AppConfigs 2017-08-19 15:36:45 +02:00
communication MAJ : add on_delete + MIDDLEWARE 2018-08-27 00:02:33 +02:00
equipment hotfix: dates activity 2018-08-27 15:31:44 +02:00
event Inscription en perm 2018-08-28 22:19:24 +02:00
poulpe allauth don't works right now… 2018-10-11 09:48:03 +02:00
provisioning rename app evenementiel to poulpe 2018-08-20 14:32:52 +02:00
shared Fix css filtrage catégories 2018-08-28 22:40:02 +02:00
users avec les migrations c'est mieux 2018-08-27 14:09:27 +02:00
.gitignore event base done 2018-08-26 21:18:51 +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 MAJ : MAJ 2.0, remove debug_panel, django.change url.resolvers to django.urls 2018-08-27 00:30:12 +02:00
requirements-prod.txt prod requirements 2018-08-06 10:19:48 +02:00
requirements.txt MAJ allauth 2018-10-04 21:34:39 +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).