| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | onboard/tracker: remember token as query parameter | stuebinm | 2024-05-03 | 1 | -13/+23 |
| | | | | | | | there's some trade-offs here (cookies may be discarded by the browser, query parameters lost if people use a bookmark), but either works fine for not re-issuing tokens if someone reloads the web site. | ||||
| * | restructure: get the tracker to work again | stuebinm | 2024-05-02 | 1 | -0/+137 |
| | | | | | | | | | | | | | | | | 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 database | stuebinm | 2024-04-24 | 1 | -3/+3 |
| | | | | | now mostly independent of the gtfs, but still no live-reloading of it. | ||||
| * | on-board-unit: display estimated delay etc. | stuebinm | 2022-09-11 | 1 | -1/+14 |
| | | |||||
| * | use websockets for the on-board-unit | stuebinm | 2022-09-10 | 1 | -19/+46 |
| | | |||||
| * | init onboard-unit | stuebinm | 2022-09-03 | 1 | -0/+92 |
 |
index : tracktrain | |
| track trains on their traintracks |
| aboutsummaryrefslogtreecommitdiff |