aboutsummaryrefslogtreecommitdiff
path: root/lib (follow)
Commit message (Collapse)AuthorAgeFilesLines
* gtfs-rt: set trip_descriptor.schedule_relationshipstuebinm2022-12-031-1/+2
| | | | (hardcoded for now, since we don't have new trips)
* unreasonably stupid and probably unnecessary codestuebinm2022-12-032-5/+18
| | | | (but maybe google will like it)
* set uncertainty in gtfs-rtstuebinm2022-12-031-2/+2
|
* always display secondsstuebinm2022-12-031-2/+2
| | | | (this is a hack to make the gtfs rt valid)
* this is almost certainly bullshitstuebinm2022-12-031-6/+6
|
* let's try something else as wellstuebinm2022-12-031-1/+2
|
* another gtfs rt thingie?stuebinm2022-12-031-1/+2
|
* fix google warningstuebinm2022-12-031-1/+1
|
* controlroom: show tripShortName instead of tripIdstuebinm2022-11-292-8/+20
| | | | | since the ids really should be internal to the gtfs, and not needed in "normal" contexts.
* respect gtfs start/end datestuebinm2022-11-291-1/+4
| | | | | | not only is this a surprisingly stupid bug, i distinctly remember writing these few lines sometime ago … but they're not in the commit history, so i guess they got lost somehow??
* fix gtfs tripupdatesstuebinm2022-10-161-83/+92
|
* simple prometheus metricsstuebinm2022-10-163-7/+35
|
* remove some extrapolation bugsstuebinm2022-09-144-61/+66
|
* on-board-unit: display estimated delay etc.stuebinm2022-09-113-6/+12
|
* correct the generated openapi descriptionstuebinm2022-09-112-5/+22
|
* gtfs realtime: add tripUpdate feedstuebinm2022-09-105-33/+104
|
* use websockets for the on-board-unitstuebinm2022-09-101-32/+31
|
* fix the close-to-a-station bugstuebinm2022-09-091-22/+31
| | | | | | (previously tracktrain could end up in a situation where the next and last station weren't actually adjacent stops, which messed up the prediction)
* init onboard-unitstuebinm2022-09-031-0/+21
|
* reasonable delay forecastsstuebinm2022-09-024-66/+96
|
* guess at future delays (horrible, incorrect, and unfinished)stuebinm2022-08-315-43/+95
|
* some config thingyesodstuebinm2022-08-286-29/+64
| | | | | 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-286-99/+346
| | | | most of it deals with timezones, and all the weird implications that has
* controlroom: lots of pretty little knobsstuebinm2022-08-277-123/+185
| | | | (also some database schema changes, for good measure)
* controlroom: some stylingstuebinm2022-08-261-37/+84
|
* ControlRoom: default layoutstuebinm2022-08-141-18/+30
|
* control room: translations & form inputstuebinm2022-08-145-201/+162
| | | | still basic, but works pretty well overall
* controlroom: replace servant/lucid with yesodstuebinm2022-08-145-269/+212
| | | | aka use something meant for webapps to write the webapp
* better Show instance for Timestuebinm2022-08-141-3/+7
|
* a little more control room workstuebinm2022-07-202-9/+39
|
* some work on the control roomstuebinm2022-07-173-32/+80
| | | | (it can do useful stuff! but it also still breaks on some things!)
* fix an operator precedence bugstuebinm2022-07-171-6/+6
|
* somewhat functioning control roomstuebinm2022-07-117-36/+117
| | | | | | 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!
* generic html forms for ADTsstuebinm2022-07-072-88/+122
| | | | this does some GHC generics witchery, now in its own module!
* don't have the ControlRoom API in Swaggerstuebinm2022-07-073-13/+3
| | | | | | 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.
* wrote some generic html form codestuebinm2022-07-061-12/+97
| | | | | this automatically derives lucid html versions of ADTs which are hopefully compatible with the FormUrlEncoded type class
* barebones webform API & frontendstuebinm2022-07-034-18/+84
|
* remove some unused importsstuebinm2022-07-033-89/+63
|
* add service monad (with built-in logging)stuebinm2022-07-033-20/+35
|
* websockets and better (empty) response messagesstuebinm2022-07-022-57/+78
| | | | (tough mostly untested)
* better module namesstuebinm2022-07-022-2/+3
|
* rudimentary admin api implementationstuebinm2022-07-024-10/+26
|
* gtfs realtime: add vehicle positionsstuebinm2022-07-023-17/+71
| | | | | | (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)
* more or less functional servicealerts for gtfs rtstuebinm2022-07-025-98/+223
| | | | (kinda barebones, but the important things should be there)
* gtfs realtime proof of conceptstuebinm2022-07-022-2/+75
| | | | | | | | 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-272-16/+31
| | | | (mostly to make debugging easier, but also more generially useful i guess)
* handle GTFS shapes (& send them out along trips)stuebinm2022-06-192-14/+64
| | | | | 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.
* a couple more database schemasstuebinm2022-06-161-5/+28
| | | | | might eventually be needed; until then they're just scaffolding so I don't loose sight of things
* foreign keys are a thingstuebinm2022-06-165-74/+60
| | | | | | (and they can be useful, too!) Also, documentation & deleting imports / extensions that aren't used.
* actually use the databasestuebinm2022-06-163-96/+223
| | | | | | (at least for a few simple things) Also, more modules!
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-20 20:53:21 +0000