| Commit message (Collapse) | Author | Files | Lines | ||
|---|---|---|---|---|---|
| 2026-05-13 | Server.Frontend.Tracker: dedicated configuration menuHEADmain | stuebinm | 1 | -2/+14 | |
| There is no back-channel with which we could retrieve the config that is currently on an owntracks client. However, we can send out each config with its own slightly tweaked host url, so that we can detect its provisioning on the incoming requests anyways. Credits for the idea go to Emily. | |||||
| 2026-05-02 | owntracks: support returning commands | stuebinm | 1 | -7/+23 | |
| 2026-04-16 | Server.Frontend.Tracker: creation & deletion dialogs | stuebinm | 1 | -4/+5 | |
| 2026-04-16 | lib: formatter run | stuebinm | 1 | -9/+11 | |
| 2026-04-16 | Server: ingest owntracks messages, frontend tracker view | stuebinm | 1 | -11/+78 | |
| 2026-04-16 | meta: reorganisation, rename "token" to "trackerId" | stuebinm | 1 | -22/+21 | |
| 2024-05-19 | Server.Ingest: bugfix (tentative) | stuebinm | 1 | -12/+12 | |
| 2024-05-15 | Server.Ingest: new handling of unassigned trackers | stuebinm | 1 | -71/+135 | |
| now takes all potential stops along each trip into account when guessing tickets; also checks if a ticket is still likely in case the tracker switched its direction. This should solve many cases where a tracker is accidentally turned off or falls asleep halfway before the last station of one trip, then wakes up in the middle of the next. | |||||
| 2024-05-08 | restructure: split up the server module | stuebinm | 1 | -0/+211 | |
 |
index : tracktrain | |
| track trains on their traintracks |
| aboutsummaryrefslogtreecommitdiff |