Conversation
sergerad
added
the
no changelog
| Environment="OTEL_SERVICE_NAME=miden-validator" | ||
| EnvironmentFile=/lib/systemd/system/miden-validator.env | ||
| ExecStart=/usr/bin/miden-node validator start | ||
| WorkingDirectory=/opt/miden-node |
There was a problem hiding this comment.
Bit of a meta question, but we should probably distinguish this from the node? In case both node + validator run on the same instance.
| WorkingDirectory=/opt/miden-node | |
| WorkingDirectory=/opt/miden-validator |
A different way of doing things is to have common /opt/miden/ directory and then each service gets its own /opt/miden/<service> folder in there. But that gets dodgy..? Or maybe not.
Essentially, I think I recall that each "org" should have its own /opt directory. But I could be mistaken. I think part of the problem would then be that we probably need a miden user group to own the /opt/miden directory, which would then let the miden-node, miden-validator users act within that group. Or we just have a single miden user which handles all miden services.
Probably I'm overthinking things :)
There was a problem hiding this comment.
Seems reasonable but would opt to add validator in the current scheme we have and do a migration for all existing packages/services separately to this work
|
Tested here https://github.com/0xMiden/miden-node/actions/runs/21810104637 will try run it on validator instance now |
3 participants
The Debian packaging automation needed to be updated to support multiple services in a single Debian package.