| Commit message (Collapse) | Author | Files | Lines |
|---|
|
A simple way to have "announcements" available via API, and otherwise
distinct from the service announcements which show up in Gtfs Realtime.
These are meant to go e.g. be embedded on the operator's website, or in
other places where it's not as easy to display per-trip specific messages.
|
|
this is meant to be false by default, and otherwise relaxes requirements
on e.g. incoming pings, which are inconvenient when testing by hand.
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
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.)
|
|
|
|
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.
|
|
(what was that about doing the realtime stuff somewhere else and /not/
in this monolithic server thingie? oh well …)
|
|
(for a leaflet map view or sth which isn't implemented yet)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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
|
|
(also some database schema changes, for good measure)
|
|
still basic, but works pretty well overall
|
|
aka use something meant for webapps to write the webapp
|
|
tbh i've kinda lost track at what has all been changed in this, but the
control room form handling now works, and i can write announcements into
the database. Now on to making it do useful things!
|
|
just causes pain and isn't really useful for anything since it's a
webform API meant to be used by the web frontend, not by other
applications.
|
|
|
|
|
|
|
|
(tough mostly untested)
|
|
|
|
|
|
(or at least something that looks like it might be correct — though
it carries very little information, and lacks things like what the next
stop along the route is)
|
|
(kinda barebones, but the important things should be there)
|
|
this adds a package for protobuf stuff, generated via hprotoc. Seems to
work kinda fine?
(the generated API is horrible though, will have to write some wrappers
for that)
|
|
(mostly to make debugging easier, but also more generially useful i guess)
|
|
(and they can be useful, too!)
Also, documentation & deleting imports / extensions that aren't used.
|
|
(at least for a few simple things)
Also, more modules!
|
|
this doesn't yet actually use the database, but it's getting close to
3am and I should probably go to bed or something
|
|
lots of lenses in this stuff :(
|
|
unfortunately doesn't quite get rid of all the type family still
since it's just too useful … but does reduce it somewhat.
Also, maps are much easier for looking things up than vectors!
|
|
(template haskell doesn't work well with type families, unfortunately)
|
|
|
