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
19 commits 1 branch 8 tags 130 KiB
Rust 83.1%
JavaScript 9.1%
CSS 7.8%
Find a file
trotFunky a0b79a17ea Redirects: properly redirect to the current week 
Previously, most redirects targeted the root of the application.
This was okay for the first part of development where only one week would be
active, but would be annoying when using multiple weeks.

Change those redirects to call week::week.

Change the login path to be dependant on the current week as well,
so it can be correctly redirected.
2024-07-26 01:08:47 +01:00
db v1.1: Add weekly introductions 2024-07-23 21:51:51 +01:00
src Redirects: properly redirect to the current week 2024-07-26 01:08:47 +01:00
static_files week: Create new weeks and change active one 2024-07-26 00:52:41 +01:00
templates Redirects: properly redirect to the current week 2024-07-26 01:08:47 +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 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.