aboutsummaryrefslogtreecommitdiff
path: root/lib/API.hs (follow)
Commit message (Collapse)AuthorAgeFilesLines
* 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!