Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(front-end): User-level logger configurator package #53

Open
selimnairb opened this issue Apr 26, 2024 · 0 comments
Open

(front-end): User-level logger configurator package #53

selimnairb opened this issue Apr 26, 2024 · 0 comments
Labels
enhancement New feature or request major

Comments

@selimnairb
Copy link
Member

Original report by Brian Calder (Bitbucket: brian_r_calder, ).


Although the embedded web-server and default setup from cold boot makes it much easier to configure loggers, you still have to manually set the logger information, add a metadata file, and if you’re using auto-upload, provide the pre-shared password and CA certificate for authentication and TLS. All of this takes some preparation time; for small logger deployments, this is fine to do by hand, but for scale deployments it could become expensive.

Therefore, this enhancement request is to allow in the front-end web management interface a mode to generate a configuration package for a logger including:

  • The configuration JSON for the logger, to be loaded in the embedded web site configuration page. This sets the logger’s unique ID, name, status of the various loggers, etc.
  • A metadata JSON to embed in the logger. This would require the user to provide information about sensors and offsets (if available), and processing requirements, the logger identification number (if available), name, type, length, etc.
  • An upload pre-shared password string (typically a UUID4)
  • The CA certificate for auto-upload. This will be the same for all loggers, most likely, but should be included in the package so that the current version is readily available.

For bonus points, provide a desktop tool that takes this configuration package and uses the logger’s underlying “command” API endpoint to send all of it to the logger in sequence, then reboot. If this is possible, then add to the configuration package:

  • List of algorithms to be set on the logger as requests for post-processing.
  • List of NMEA0183 messages to accept from the input streams.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request major
Projects
None yet
Development

No branches or pull requests

1 participant