trotFunky/FabulaVotes
1
0
Fork 0
Code Releases Packages Activity
A simple application presenting truths and allowing people to guess on their authors for an upcoming campaign of Fabula Ultima
17 commits 1 branch 8 tags 130 KiB
Rust 83.1%
JavaScript 9.1%
CSS 7.8%
Find a file
trotFunky 635716c04b vote: Change graph display condition, don't fetch for admin 
Now, the graph will only show when everyone has voted and the week is no longer
the last one active.
This is to minimize information gathering by looking during voting.

Don't fetch the vote data for the admin : it is not used, so no need to
query the database.

Update README with new TODOs and clean up main includes a bit.
2024-07-26 00:47:10 +01:00
db v1.1: Add weekly introductions 2024-07-23 21:51:51 +01:00
src vote: Change graph display condition, don't fetch for admin 2024-07-26 00:47:10 +01:00
static_files styles: Minor reorganization 2024-07-26 00:41:05 +01:00
templates templates/truth: Prevent changing vote if not last week 2024-07-25 23:44:00 +01:00
.gitignore v1.0: First production version 2024-07-23 21:51:42 +01:00
Cargo.lock auth: Fix auth token getting leaked to console 2024-07-23 21:51:56 +01:00
Cargo.toml auth: Fix auth token getting leaked to console 2024-07-23 21:51:56 +01:00
LICENSE.md v1.0: First production version 2024-07-23 21:51:42 +01:00
README.md vote: Change graph display condition, don't fetch for admin 2024-07-26 00:47:10 +01:00
Rocket.toml v1.0: First production version 2024-07-23 21:51:42 +01:00

README.md

Fabula Votes

This web application is intended as a simple way to share Truths for an upcoming campaign of Fabula Ultima, vote and who we think wrote them and see some stats !

TODO

A list of things that could be implemented/added to the application, some of them are needed for "feature completeness" !

  • Being able to change from one week to the next
    • Create new weeks for the admin
    • Proper week redirection
      • Correctly handle non-existing week number
  • Add introduction to the weekly truths
  • Bundle static assets in the binary
  • Move the database queries to their own functions
    • Cache those results
  • Centralize Markdown parsing ?
  • Use fairings for the different elements ?
  • Use guards for User calls ?

Dependencies

This project currently uses :

  • Rocket, for the web application backend
  • SQLX, for database access (this is only expeceted to be used with SQLite)
  • Tera, for templating
  • Argon2, for password hashing
  • Pull_down CMark, for markdown rendering

License

The code present in this repository is licensed under the Mozilla Public License 2.0.