Ryan Tharp

so you can pass it your other files in a multisnode cfg

Integrate systemd control of service

3

actually call "systemctl stop lokid" when as root as needed

think about and discuss

Lokid now required a specific storage server version

1

This logic should be in the loki-launcher validation/startup and communicate it to the user, so they don't silently fail

develop game plan - log api - writes to file/stdout/syslog/network/socketserver - format human/json - control per stdout/stderr - event emitter with tagging

as base

move multi-instance info out of this repo

3

mkdir a directory somewhere if you want to use a different user per repo, then clone the repo to the user's home directory (this is safer than running them all...

parse it, include it in status maybe hold start up while it's ran?

Use spawn for background daemon comm channels to pass status

3

don't bail until you're sure it succeed or timeout

option to create a lokid.service file from scratch

1

need to pass in what user you want to run it as