aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* todo: warnings given by google mapsHEADmainstuebinm7 hours1-0/+3
|
* fix: tripupdates should not contain old tripsstuebinm8 hours1-2/+2
| | | | apparently i forgot an if here?
* update todo itemsstuebinm32 hours1-33/+69
| | | | | largely based on things noticed on 2024-05-01, this year's first day of Ilztalbahn trains running.
* changelog for 0.0.2stuebinm32 hours2-1/+6
| | | | this is the initial version used during 2024's Ilztalbahn season.
* document new config options in config.yaml.samplestuebinm32 hours1-0/+6
|
* restructure: get the tracker to work againstuebinm32 hours11-135/+407
| | | | | | | | | | | | | | | 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)
* correct styling on mobile devicesstuebinm8 days1-1/+4
|
* restructure: save a ticket's stop in the databasestuebinm8 days11-332/+508
| | | | now mostly independent of the gtfs, but still no live-reloading of it.
* restructure: have "tickets" independent of gtfsstuebinm13 days15-208/+341
| | | | | | 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).
* add config.yaml.sample filestuebinm13 days2-3/+6
|
* use direnv for dependenciesstuebinm13 days2-0/+6
|
* general housekeepingstuebinm2024-04-1715-173/+119
| | | | | 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-1739-3690/+10916
| | | | | | 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).
* update nix overridesstuebinm2023-06-301-18/+14
| | | | | | | | protocol-buffers's last release has been some while ago, and since then a deprecated function it used to use has been removed from the bytestring package. so here's some fun overrides to ignore that.
* change server timetables apistuebinm2023-05-261-1/+2
|
* expose sequence length of trip to onboard unitstuebinm2023-05-264-23/+41
|
* gtfs-rt: discard old trips from tripupdates feedstuebinm2023-05-231-7/+12
| | | | google maps complains about it otherwise
* onboard-tools: fix httpsstuebinm2023-05-202-3/+3
|
* expose the gtfs.zip used in the APIstuebinm2023-05-205-29/+49
|
* … add assets to gitstuebinm2023-03-161-0/+62
|
* add assets to nix derivationstuebinm2023-03-161-0/+4
|
* simple on-board toolsstuebinm2023-03-118-10/+289
| | | | | | 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-234-68/+10
|
* better web interface & cssstuebinm2023-01-285-31/+108
|
* yaml be imprecise & confusingstuebinm2023-01-281-0/+3
|
* config: prefer env varsstuebinm2023-01-221-1/+1
|
* switch to ghc 9.0.2stuebinm2023-01-224-61/+83
| | | | this makes the nix builds /much/ nicer
* oauth2 via uffdstuebinm2023-01-229-52/+232
| | | | | | 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-135-2/+60
| | | | | (what was that about doing the realtime stuff somewhere else and /not/ in this monolithic server thingie? oh well …)
* stylish-haskell runstuebinm2022-12-123-6/+7
|
* a subscribe websocket for real-time location infostuebinm2022-12-122-7/+37
| | | | (for a leaflet map view or sth which isn't implemented yet)
* cabal: set minimum warp version to make conferer-warp buildstuebinm2022-12-071-1/+1
|
* 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-293-8/+23
| | | | | 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??
* use the threaded rtsstuebinm2022-11-231-0/+1
| | | | (apparently i didn't do that yet???)
* nix: strip ghc dependencies from outputstuebinm2022-11-071-1/+12
|
* gtfs-rt: don't remove SCHEDULED from schedule_relationshipstuebinm2022-10-161-2/+2
| | | | | (since it's the default value it's not serialised; but best practices say to have it there explicitly)
* fix nix buildstuebinm2022-10-161-2/+2
|
* fix gtfs tripupdatesstuebinm2022-10-161-83/+92
|
* simple prometheus metricsstuebinm2022-10-165-9/+55
|
* update glossarystuebinm2022-09-141-5/+8
|
* remove some extrapolation bugsstuebinm2022-09-144-61/+66
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-03 05:53:13 +0000