| Commit message (Collapse) | Author | Files | Lines | ||
|---|---|---|---|---|---|
| 2024-05-15 | config: add a debug mode option | stuebinm | 2 | -3/+8 | |
| this is meant to be false by default, and otherwise relaxes requirements on e.g. incoming pings, which are inconvenient when testing by hand. | |||||
| 2024-05-10 | space time diagrams: real time & time zones | stuebinm | 3 | -86/+178 | |
| 2024-05-09 | rough initial work on space-time diagrams | stuebinm | 3 | -0/+107 | |
| 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. | |||||
| 2024-05-09 | restructure: split web frontend into several modules | stuebinm | 6 | -302/+479 | |
| 2024-05-08 | restructure: split up the server module | stuebinm | 5 | -302/+394 | |
| 2024-05-03 | fix: tripupdates should not contain old trips | stuebinm | 1 | -2/+2 | |
| apparently i forgot an if here? | |||||
| 2024-05-02 | restructure: get the tracker to work again | stuebinm | 8 | -135/+268 | |
| 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) | |||||
| 2024-04-24 | correct styling on mobile devices | stuebinm | 1 | -1/+4 | |
| 2024-04-24 | restructure: save a ticket's stop in the database | stuebinm | 7 | -327/+502 | |
| now mostly independent of the gtfs, but still no live-reloading of it. | |||||
| 2024-04-20 | restructure: have "tickets" independent of gtfs | stuebinm | 8 | -192/+305 | |
| 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). | |||||
| 2024-04-17 | general housekeeping | stuebinm | 9 | -72/+29 | |
| jumps to GHC2021 as default language, adds in some fields, moves the old org mode glossary to markdown, etc. | |||||
| 2024-04-17 | replace protocol-buffers with proto-lens | stuebinm | 3 | -282/+198 | |
| 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). | |||||
| 2023-05-26 | change server timetables api | stuebinm | 1 | -1/+2 | |
| 2023-05-26 | expose sequence length of trip to onboard unit | stuebinm | 1 | -0/+1 | |
| 2023-05-23 | gtfs-rt: discard old trips from tripupdates feed | stuebinm | 1 | -7/+12 | |
| google maps complains about it otherwise | |||||
| 2023-05-20 | expose the gtfs.zip used in the API | stuebinm | 5 | -29/+49 | |
| 2023-03-11 | simple on-board tools | stuebinm | 2 | -10/+26 | |
| 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.) | |||||
| 2023-02-23 | don't hardcode css | stuebinm | 4 | -68/+10 | |
| 2023-01-28 | better web interface & css | stuebinm | 3 | -30/+84 | |
| 2023-01-22 | switch to ghc 9.0.2 | stuebinm | 2 | -27/+46 | |
| this makes the nix builds /much/ nicer | |||||
| 2023-01-22 | oauth2 via uffd | stuebinm | 4 | -48/+210 | |
| 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. | |||||
| 2022-12-13 | simple realtime position map | stuebinm | 3 | -2/+58 | |
| (what was that about doing the realtime stuff somewhere else and /not/ in this monolithic server thingie? oh well …) | |||||
| 2022-12-12 | stylish-haskell run | stuebinm | 3 | -6/+7 | |
| 2022-12-12 | a subscribe websocket for real-time location info | stuebinm | 2 | -7/+37 | |
| (for a leaflet map view or sth which isn't implemented yet) | |||||
| 2022-12-03 | gtfs-rt: set trip_descriptor.schedule_relationship | stuebinm | 1 | -1/+2 | |
| (hardcoded for now, since we don't have new trips) | |||||
| 2022-12-03 | unreasonably stupid and probably unnecessary code | stuebinm | 2 | -5/+18 | |
| (but maybe google will like it) | |||||
| 2022-12-03 | set uncertainty in gtfs-rt | stuebinm | 1 | -2/+2 | |
| 2022-12-03 | always display seconds | stuebinm | 1 | -2/+2 | |
| (this is a hack to make the gtfs rt valid) | |||||
| 2022-12-03 | this is almost certainly bullshit | stuebinm | 1 | -6/+6 | |
| 2022-12-03 | let's try something else as well | stuebinm | 1 | -1/+2 | |
| 2022-12-03 | another gtfs rt thingie? | stuebinm | 1 | -1/+2 | |
| 2022-12-03 | fix google warning | stuebinm | 1 | -1/+1 | |
| 2022-11-29 | controlroom: show tripShortName instead of tripId | stuebinm | 2 | -8/+20 | |
| since the ids really should be internal to the gtfs, and not needed in "normal" contexts. | |||||
| 2022-11-29 | respect gtfs start/end date | stuebinm | 1 | -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?? | |||||
| 2022-10-16 | fix gtfs tripupdates | stuebinm | 1 | -83/+92 | |
| 2022-10-16 | simple prometheus metrics | stuebinm | 3 | -7/+35 | |
| 2022-09-14 | remove some extrapolation bugs | stuebinm | 4 | -61/+66 | |
| 2022-09-11 | on-board-unit: display estimated delay etc. | stuebinm | 3 | -6/+12 | |
| 2022-09-11 | correct the generated openapi description | stuebinm | 2 | -5/+22 | |
| 2022-09-10 | gtfs realtime: add tripUpdate feed | stuebinm | 5 | -33/+104 | |
| 2022-09-10 | use websockets for the on-board-unit | stuebinm | 1 | -32/+31 | |
| 2022-09-09 | fix the close-to-a-station bug | stuebinm | 1 | -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) | |||||
| 2022-09-03 | init onboard-unit | stuebinm | 1 | -0/+21 | |
| 2022-09-02 | reasonable delay forecasts | stuebinm | 4 | -66/+96 | |
| 2022-08-31 | guess at future delays (horrible, incorrect, and unfinished) | stuebinm | 5 | -43/+95 | |
| 2022-08-28 | some config thingyesod | stuebinm | 6 | -29/+64 | |
| works kinda well, but doesn't complain about unknown config values in json, which is kinda hmpf tbh | |||||
| 2022-08-28 | this does way too much tbh (also functioning delays) | stuebinm | 6 | -99/+346 | |
| most of it deals with timezones, and all the weird implications that has | |||||
| 2022-08-27 | controlroom: lots of pretty little knobs | stuebinm | 7 | -123/+185 | |
| (also some database schema changes, for good measure) | |||||
| 2022-08-26 | controlroom: some styling | stuebinm | 1 | -37/+84 | |
| 2022-08-14 | ControlRoom: default layout | stuebinm | 1 | -18/+30 | |
 |
index : tracktrain | |
| track trains on their traintracks |
| aboutsummaryrefslogtreecommitdiff |