aboutsummaryrefslogtreecommitdiff
path: root/lib/API.hs (follow)
Commit message (Collapse)AuthorAgeFilesLines
* new feature: Server.Frontend.Tickerstuebinm2024-05-161-0/+1
| | | | | | | | 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.
* Server.Ingest: new handling of unassigned trackersstuebinm2024-05-151-2/+16
| | | | | | | | 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.
* restructure: get the tracker to work againstuebinm2024-05-021-31/+23
| | | | | | | | | | | | | | | 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-241-4/+4
| | | | now mostly independent of the gtfs, but still no live-reloading of it.
* restructure: have "tickets" independent of gtfsstuebinm2024-04-201-6/+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).
* general housekeepingstuebinm2024-04-171-7/+3
| | | | | jumps to GHC2021 as default language, adds in some fields, moves the old org mode glossary to markdown, etc.
* replace protocol-buffers with proto-lensstuebinm2024-04-171-7/+26
| | | | | | I do not really like either option, but at least the second one seems more likely to be maintained (and a little less clunky to use, too, for what it's worth).
* expose the gtfs.zip used in the APIstuebinm2023-05-201-13/+21
|
* simple on-board toolsstuebinm2023-03-111-2/+7
| | | | | | these are just enough to send train positions to tracktrain with the current API, but are somewhat brittle (e.g. will fail if not restarted between trips, etc.)
* don't hardcode cssstuebinm2023-02-231-0/+1
|
* simple realtime position mapstuebinm2022-12-131-1/+1
| | | | | (what was that about doing the realtime stuff somewhere else and /not/ in this monolithic server thingie? oh well …)
* a subscribe websocket for real-time location infostuebinm2022-12-121-0/+1
| | | | (for a leaflet map view or sth which isn't implemented yet)
* simple prometheus metricsstuebinm2022-10-161-1/+11
|
* on-board-unit: display estimated delay etc.stuebinm2022-09-111-1/+1
|
* correct the generated openapi descriptionstuebinm2022-09-111-4/+19
|
* some config thingyesodstuebinm2022-08-281-1/+1
| | | | | works kinda well, but doesn't complain about unknown config values in json, which is kinda hmpf tbh
* this does way too much tbh (also functioning delays)stuebinm2022-08-281-1/+0
| | | | most of it deals with timezones, and all the weird implications that has
* controlroom: lots of pretty little knobsstuebinm2022-08-271-32/+23
| | | | (also some database schema changes, for good measure)
* control room: translations & form inputstuebinm2022-08-141-2/+2
| | | | still basic, but works pretty well overall
* controlroom: replace servant/lucid with yesodstuebinm2022-08-141-2/+2
| | | | aka use something meant for webapps to write the webapp
* somewhat functioning control roomstuebinm2022-07-111-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!
* don't have the ControlRoom API in Swaggerstuebinm2022-07-071-5/+1
| | | | | | just causes pain and isn't really useful for anything since it's a webform API meant to be used by the web frontend, not by other applications.
* barebones webform API & frontendstuebinm2022-07-031-17/+20
|
* remove some unused importsstuebinm2022-07-031-10/+10
|
* websockets and better (empty) response messagesstuebinm2022-07-021-9/+13
| | | | (tough mostly untested)
* rudimentary admin api implementationstuebinm2022-07-021-3/+4
|
* more or less functional servicealerts for gtfs rtstuebinm2022-07-021-20/+36
| | | | (kinda barebones, but the important things should be there)
* gtfs realtime proof of conceptstuebinm2022-07-021-1/+12
| | | | | | | | this adds a package for protobuf stuff, generated via hprotoc. Seems to work kinda fine? (the generated API is horrible though, will have to write some wrappers for that)
* optional date parameter for the timetable endpointstuebinm2022-06-271-12/+23
| | | | (mostly to make debugging easier, but also more generially useful i guess)
* foreign keys are a thingstuebinm2022-06-161-11/+23
| | | | | | (and they can be useful, too!) Also, documentation & deleting imports / extensions that aren't used.
* actually use the databasestuebinm2022-06-161-0/+35
(at least for a few simple things) Also, more modules!
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-07 23:58:48 +0000