3c848fe47c
The popup is horizontally aligned with the click location, and vertically close to event (slightly on top of it, from below). If the click occurs too much on the left or the right side of the screen, the horizontal position is shifted accordingly, so that it is never displayed outside of the screen. Note, however, that the small arrow supposed to point the related event is not shifted as well as of now (not as straightforward since it is a CSS pseudo-element). This commit also removes the ability to display the popup _above_ the event in case the click occurs too close to the bottom of the screen. This feature should be reintroduced by a later commit once it will have been fixed :). |
||
|---|---|---|
| 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).