aboutsummaryrefslogtreecommitdiff
path: root/lib/Persist.hs (unfollow)
Commit message (Collapse)AuthorFilesLines
2024-05-16Persist: add cascade rules to foreign keysstuebinm1-9/+7
It turns out persist does support these, they're just not mentioned in the yesod book. (for future reference, the syntax is defined in Database.Persist.Quasi, which does include some documentation [1]) [1] https://hackage.haskell.org/package/persistent-2.14.6.1/docs/Database-Persist-Quasi.html
2024-05-16new feature: Server.Frontend.Tickerstuebinm1-0/+7
A simple way to have "announcements" available via API, and otherwise distinct from the service announcements which show up in Gtfs Realtime. These are meant to go e.g. be embedded on the operator's website, or in other places where it's not as easy to display per-trip specific messages.
2024-05-15Server.Ingest: new handling of unassigned trackersstuebinm1-1/+5
now takes all potential stops along each trip into account when guessing tickets; also checks if a ticket is still likely in case the tracker switched its direction. This should solve many cases where a tracker is accidentally turned off or falls asleep halfway before the last station of one trip, then wakes up in the middle of the next.
2024-05-02restructure: get the tracker to work againstuebinm1-8/+30
This should hopefully be the final (major) part of the restructuring: a tracker no longer has to know which trip it is on (and indeed it has no idea for now), instead the server keeps state about which trips are currently running and will insert incoming pings in a hopefully reasonable manner, based on their geoposition & time. There's lots of associated TODO items here (especially there should be manual overrides for all this logic in the web ui), but that's work for a future me. (incidentally, this also adds support for sending all log messages out via ntfy-sh)
2024-04-24restructure: save a ticket's stop in the databasestuebinm1-12/+54
now mostly independent of the gtfs, but still no live-reloading of it.
2024-04-20restructure: have "tickets" independent of gtfsstuebinm1-25/+30
this is mostly meant to guard against the gtfs changing under tracktrain, and not yet complete (e.g. a ticket does not yet save its expected stops, which it probably should).
2024-04-17general housekeepingstuebinm1-15/+7
jumps to GHC2021 as default language, adds in some fields, moves the old org mode glossary to markdown, etc.
2022-09-11on-board-unit: display estimated delay etc.stuebinm1-2/+6
2022-09-11correct the generated openapi descriptionstuebinm1-1/+3
2022-09-02reasonable delay forecastsstuebinm1-2/+3
2022-08-31guess at future delays (horrible, incorrect, and unfinished)stuebinm1-6/+9
2022-08-28this does way too much tbh (also functioning delays)stuebinm1-8/+2
most of it deals with timezones, and all the weird implications that has
2022-08-27controlroom: lots of pretty little knobsstuebinm1-18/+30
(also some database schema changes, for good measure)
2022-08-14control room: translations & form inputstuebinm1-1/+1
still basic, but works pretty well overall
2022-08-14controlroom: replace servant/lucid with yesodstuebinm1-2/+1
aka use something meant for webapps to write the webapp
2022-07-20a little more control room workstuebinm1-2/+8
2022-07-17some work on the control roomstuebinm1-1/+1
(it can do useful stuff! but it also still breaks on some things!)
2022-07-11somewhat functioning control roomstuebinm1-1/+1
tbh i've kinda lost track at what has all been changed in this, but the control room form handling now works, and i can write announcements into the database. Now on to making it do useful things!
2022-07-02rudimentary admin api implementationstuebinm1-5/+4
2022-07-02gtfs realtime: add vehicle positionsstuebinm1-0/+1
(or at least something that looks like it might be correct — though it carries very little information, and lacks things like what the next stop along the route is)
2022-07-02more or less functional servicealerts for gtfs rtstuebinm1-2/+7
(kinda barebones, but the important things should be there)
2022-06-19handle GTFS shapes (& send them out along trips)stuebinm1-4/+4
unfortunately, this makes some responses pretty large. Let's see if it works this way or if i have to find some way to break them up instead.
2022-06-16a couple more database schemasstuebinm1-5/+28
might eventually be needed; until then they're just scaffolding so I don't loose sight of things
2022-06-16foreign keys are a thingstuebinm1-10/+10
(and they can be useful, too!) Also, documentation & deleting imports / extensions that aren't used.
2022-06-16actually use the databasestuebinm1-0/+85
(at least for a few simple things) Also, more modules!