Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| applications:society-voting [2025/03/28 23:29] – root | applications:society-voting [2025/05/20 19:10] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== Society Voting ===== | + | ====== Society Voting ====== |
| + | |||
| + | The [[https:// | ||
| + | |||
| + | It is deployed in a single Docker container on [[infrastructure: | ||
| + | |||
| + | ===== Spinning up ===== | ||
| + | |||
| + | There are two configured versions on [[infrastructure: | ||
| + | |||
| + | Switch to directory ''/ | ||
| + | |||
| + | < | ||
| + | |-- config.yaml | ||
| + | |-- docker-compose.yaml | ||
| + | |-- restart.sh | ||
| + | |-- src | ||
| + | `-- voting.sqlite3.db | ||
| + | </ | ||
| + | |||
| + | '' | ||
| + | |||
| + | Next, make sure all the values in '' | ||
| + | |||
| + | Finally, '' | ||
| + | |||
| + | ===== Stuff to know ===== | ||
| + | |||
| + | Due to an impossible to replicate bug, the Docker image includes a shim which will restart the application after the conclusion of a vote. Don't be alarmed if you cannot immediately see the results, just refresh the page after a few seconds. For that reason, you may want to set the session signing token to a fixed value so users aren't logged out after every vote. | ||
| + | |||
| + | On that vein, if the Docker container fails to start with some message that '' | ||
| + | |||
| + | It is possible the bug is actually fixed now, but I do not want to test it in an actual election (which unfortunately has been the only situation where the bug has presented itself).((Theo claims to have tested this in a real election for another society and it worked just fine so take that as you will)) | ||