-
Notifications
You must be signed in to change notification settings - Fork 220
Open
Description
Am I correct in reading that the StationServer's history_path argument is just to point to where "something else" is actually writing files for history objects?
It appears that the StationServer is only using PubSub to publish results and the HistoryListHandler seems to actually be configured to expect some out of tree system that is writing serialized protobufs?
The reference "chtf.py" is ... "elsehere" ? Does one have to build all this yourself to be able to use the features of StationServer or am I missing the pieces to connect?
Metadata
Metadata
Assignees
Labels
No labels