| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|
| |
|
|
| |
now mostly independent of the gtfs, but still no live-reloading of it.
|
| |
|
|
|
|
| |
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).
|
| |
|
|
|
| |
jumps to GHC2021 as default language, adds in some fields, moves the old
org mode glossary to markdown, etc.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
(previously tracktrain could end up in a situation where the next and
last station weren't actually adjacent stops, which messed up the
prediction)
|
| | |
|
| | |
|
| |
|
|
|
| |
works kinda well, but doesn't complain about unknown config values in
json, which is kinda hmpf tbh
|
|
|
most of it deals with timezones, and all the weird implications that has
|
