Webb Pinner

Doesn't reach 100% but #22 improves coverage and fixes some bugs in the user routes.

Can you confirm you ran `make virtualenv` and then activated the venv before running `make install`?

Well I think i fixed it. I think the problem is that the current build doesn't include all the dependencies. My solution was to download the 2.0.1 and 2.0.0 zip...

The way I've handled this in the past is to add the module arg when invoking a reader/transform/writer that's not already imported. i.e. ``` transforms: - class: SplitTransform module: logger.transforms.split_transform...

Would something like this work: Use the reader/transforms/writers/ `__init__.py` files to import all the readers/transforms/writers. i.e. ``` #logger.readers.__init__.py from . import cached_data_reader from . import logfile_reader from . import network_reader...

There might be a utility already installed (on Ubuntu at least) that can help with this: https://www.digitalocean.com/community/tutorials/how-to-manage-logfiles-with-logrotate-on-ubuntu-22-04

Was doing work on Revelle and took the logrotate approach for the OpenRVDAS logfiles. Was pretty simply to setup: 1. Created a new logrotate config from openrvdas: `/etc/logrotate.d/openrvdas` 2. Add...

For context... My default recommendation for installing OpenRVDAS/Grafana/InfluxDB on vessel's is to breakout Grafana and InfluxDB onto it's own hardware/VM. I have encountered too many instances where InfluxDB consumes system...

The sealog-server README.md provides a good start on how to submit events and listen to the websocket pub/sub. https://github.com/OceanDataTools/sealog-server/blob/2.x/README.md

ok... circling back to this. Connecting to Sealog and submitting an event is easy... it's defining the contents of the even within the logger_config.yaml file that is giving me trouble....