aboutsummaryrefslogtreecommitdiff
path: root/messages (follow)
Commit message (Collapse)AuthorAgeFilesLines
* new feature: Server.Frontend.Tickerstuebinm2024-05-162-0/+2
| | | | | | | | 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.
* rough initial work on space-time diagramsstuebinm2024-05-092-0/+2
| | | | | | this does svg templating with hamlet. It might be better to use a javascript library instead (templating svgs is a little confusing tbh), but for now i'll see how far i get with this.
* restructure: get the tracker to work againstuebinm2024-05-021-0/+1
| | | | | | | | | | | | | | | 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)
* restructure: save a ticket's stop in the databasestuebinm2024-04-242-2/+2
| | | | now mostly independent of the gtfs, but still no live-reloading of it.
* restructure: have "tickets" independent of gtfsstuebinm2024-04-202-0/+6
| | | | | | 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).
* better web interface & cssstuebinm2023-01-282-1/+24
|
* oauth2 via uffdstuebinm2023-01-222-0/+4
| | | | | | this is unfortunately uffd-specific, since oauth2 is apparently sort of a vague standard. But since it doesn't actually do much it should probably be possible to make it fully configurable & generic if needed.
* simple realtime position mapstuebinm2022-12-132-0/+2
| | | | | (what was that about doing the realtime stuff somewhere else and /not/ in this monolithic server thingie? oh well …)
* controlroom: show tripShortName instead of tripIdstuebinm2022-11-291-0/+3
| | | | | since the ids really should be internal to the gtfs, and not needed in "normal" contexts.
* on-board-unit: display estimated delay etc.stuebinm2022-09-112-0/+9
|
* use websockets for the on-board-unitstuebinm2022-09-101-0/+2
|
* init onboard-unitstuebinm2022-09-032-0/+8
|
* reasonable delay forecastsstuebinm2022-09-022-0/+4
|
* controlroom: lots of pretty little knobsstuebinm2022-08-272-0/+19
| | | | (also some database schema changes, for good measure)
* controlroom: some stylingstuebinm2022-08-262-7/+9
|
* control room: translations & form inputstuebinm2022-08-142-0/+22
still basic, but works pretty well overall