Timetable Database

Version 1 release!
Timetable Database is now out! Check out my repo.

Modifications:

• Fixed bug where days weren’t in user’s JSON data, and times were being added wrong.
• Added receiver’s email in settings (so they receive NTFY emails).
• Added NTFY server and API key to settings.
• Added endpoint so you can grab NTFY Credentials and Receiver Email.
• Added option to delete lectures on day/time deletion.
• Added option for user to add custom rooms and locations.
• Performance improvements.
• Created GitHub Repository, added how-to guide, and files.

I have now completed the API, Basic Settings and features, migrated to new Timetable Model with better generated lecture_id’s, and blank lecture - lecture_id’s. I also added the feature to manipulate days, times and breaks - so you can customise it to how you like. Timetable Database can now be integrated with another script of mine called ‘NTFY Timetable’ (found in the same repository), which sends notifications via a Cronjob to a NTFY server if the device is reachable (I personally do this via Tailscale, pinging my phone and laptop to see if they’re online), else will email the lecture reminders.

Features to add before I ship the project as V1:

• Add receiver’s email in settings (so they receive NTFY emails).
• Add somewhere in settings to enter your NTFY server and API key.
• Fix weird day key error (just need to add correct key for that one user)
• Add option to delete lectures on day/time deletion.

Features I want to add in V2 (after product is shipped):

• Temporary Lectures (or lab days)
• Hotswappable/Multiple timetables
• Add option is settings to customise locations (so you no longer have to do this via editing the file).
  …and many more features yet to come!

So Far I have created a API, and rewrote the Jinja templating so that it looks more pretty, and is more understandable. It was a absolute mess.