tracktrain - track trains on their traintracks

	Commit message (Collapse)	Author	Files	Lines
2024-05-16	Persist: add cascade rules to foreign keys	stuebinm	1	-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-16	new feature: Server.Frontend.Ticker	stuebinm	1	-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-15	Server.Ingest: new handling of unassigned trackers	stuebinm	1	-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-02	restructure: get the tracker to work again	stuebinm	1	-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-24	restructure: save a ticket's stop in the database	stuebinm	1	-12/+54
	now mostly independent of the gtfs, but still no live-reloading of it.
2024-04-20	restructure: have "tickets" independent of gtfs	stuebinm	1	-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-17	general housekeeping	stuebinm	1	-15/+7
	jumps to GHC2021 as default language, adds in some fields, moves the old org mode glossary to markdown, etc.
2022-09-11	on-board-unit: display estimated delay etc.	stuebinm	1	-2/+6

2022-09-11	correct the generated openapi description	stuebinm	1	-1/+3

2022-09-02	reasonable delay forecasts	stuebinm	1	-2/+3

2022-08-31	guess at future delays (horrible, incorrect, and unfinished)	stuebinm	1	-6/+9

2022-08-28	this does way too much tbh (also functioning delays)	stuebinm	1	-8/+2
	most of it deals with timezones, and all the weird implications that has
2022-08-27	controlroom: lots of pretty little knobs	stuebinm	1	-18/+30
	(also some database schema changes, for good measure)
2022-08-14	control room: translations & form input	stuebinm	1	-1/+1
	still basic, but works pretty well overall
2022-08-14	controlroom: replace servant/lucid with yesod	stuebinm	1	-2/+1
	aka use something meant for webapps to write the webapp
2022-07-20	a little more control room work	stuebinm	1	-2/+8

2022-07-17	some work on the control room	stuebinm	1	-1/+1
	(it can do useful stuff! but it also still breaks on some things!)
2022-07-11	somewhat functioning control room	stuebinm	1	-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-02	rudimentary admin api implementation	stuebinm	1	-5/+4

2022-07-02	gtfs realtime: add vehicle positions	stuebinm	1	-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-02	more or less functional servicealerts for gtfs rt	stuebinm	1	-2/+7
	(kinda barebones, but the important things should be there)
2022-06-19	handle GTFS shapes (& send them out along trips)	stuebinm	1	-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-16	a couple more database schemas	stuebinm	1	-5/+28
	might eventually be needed; until then they're just scaffolding so I don't loose sight of things
2022-06-16	foreign keys are a thing	stuebinm	1	-10/+10
	(and they can be useful, too!) Also, documentation & deleting imports / extensions that aren't used.
2022-06-16	actually use the database	stuebinm	1	-0/+85
	(at least for a few simple things) Also, more modules!