I think it makes sense to "initialize log-sender service" only when a user is installing a happ (install_happ command) with the economics section. We can throw a warning message when the container starts, that the log-sender service is not running and will be initialized when a happ is installed, otherwise user can manually initialize+start log-sender using CLI.
To initialize log-sender the user needs to provide a valid log-collector endpoint and their unytpubkey. These two values are the same for all happs on that machine. We should always check if there is a log-sender service already running, before trying to initialize+start it.
log-sender init \
--config-file /etc/log-sender/config.json \
--endpoint https://log-collector.unyt.dev \
--unyt-pub-key uhCAk4RwM1303s1z9ZGWlYUBMuBeeMb79qZ9TTPc2169HExn2mjpO \
--report-interval-seconds 60 \
--report-path /var/local/lib/holochain/reports/ \
--conductor-config-path /etc/holochain/conductor-config.yaml
I think it makes sense to "initialize log-sender service" only when a user is installing a happ (install_happ command) with the economics section. We can throw a warning message when the container starts, that the log-sender service is not running and will be initialized when a happ is installed, otherwise user can manually initialize+start log-sender using CLI.
To initialize log-sender the user needs to provide a valid log-collector endpoint and their unytpubkey. These two values are the same for all happs on that machine. We should always check if there is a log-sender service already running, before trying to initialize+start it.