d08a39307f
This is the first step to include a visual calendar to Poulpe, only including a "day view" as of now (i.e. events hour-by-hour from one date to another). More views may be added at a later time. It is **NOT WORKING YET**! The CSS has been broken on this branch, and will have to be fixed before the calendar can work: * the CSS of the calendar needs to be adapted to the environment and design of Poulpe; * add actual links to enroll/un-enroll to an activity (cf. `Event` class in `calendar.js`); * other small tweaks :)? Finally, this view is likely to require the addition of start and end date change, so that an user can browse events over several days (cf. `setStartDate` and `setEndDate` methods of `Calendar` class in `calendar.js`). Note that this code should be better re-written (e.g. in Typescript, split between files, using more/better design patterns) at a later time. It should nonetheless be easy to fix it and use it right now (see above requirements for this). |
||
|---|---|---|
| api | ||
| communication | ||
| equipment | ||
| event | ||
| poulpe | ||
| provisioning | ||
| shared | ||
| users | ||
| .gitignore | ||
| manage.py | ||
| README.md | ||
| requirements-devel.txt | ||
| requirements-prod.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).