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
23 commits 1 branch 8 tags 130 KiB
Rust 83.1%
JavaScript 9.1%
CSS 7.8%
Find a file
trotFunky 07d8cf42d7 vote: Properly take player and truth numbers into account 
Fetch the amount of truths for the week and the player count to find the total possible votes.
Use this to remove the hardocded value in the check.
Update the check to fail if there was an error as well.

Now that the truth count is calculated, send it to the javascript to build the graph
labels automatically as well.
2024-07-26 19:25:41 +01:00
db v1.1: Add weekly introductions 2024-07-23 21:51:51 +01:00
src vote: Properly take player and truth numbers into account 2024-07-26 19:25:41 +01:00
static_files vote: Properly take player and truth numbers into account 2024-07-26 19:25:41 +01:00
templates index: Remove the form if all votes were cast 2024-07-26 17:57:06 +01:00
.gitignore v1.0: First production version 2024-07-23 21:51:42 +01:00
Cargo.lock vote: Fix logic to hide graph if week is active 2024-07-26 11:30:12 +01:00
Cargo.toml vote: Fix logic to hide graph if week is active 2024-07-26 11:30:12 +01:00
LICENSE.md v1.0: First production version 2024-07-23 21:51:42 +01:00
README.md Redirects: properly redirect to the current week 2024-07-26 01:08:47 +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.