af75c90b84
We now use `django-notifications` and `django-contrib-comments` to manage notifications and comments. Subscriptions are managed through the `SubscriptionMixin` model, and can correspond to unique users and to group-like subscriptions. |
||
|---|---|---|
| communication | ||
| equipment | ||
| evenementiel | ||
| event | ||
| provisioning | ||
| shared | ||
| users | ||
| .gitignore | ||
| manage.py | ||
| README.md | ||
| requirements-devel.txt | ||
| requirements.txt | ||
| Vagrantfile | ||
Gestion Événementiel
Vagrant
Production-like environment
Our Vagrant setup provides two ways of running GestionEvenementiel:
-
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.0to make the server reachable outside the VM at addresslocalhost:8000 -
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).