darwindarak

That’s a good point. Ideally, if we had complete control over how applications behave on startup, we could design them to “self-heal” and avoid dependency issues altogether. However, many of the components in the systems we work with are either closed source or require more experience and expertise to modify.

We’ve also noticed that, in practice, for many data-critical production systems, many of our customers prefer to manually control the boot process to confirm data integrity.

The scenario of partial crashes is interesting. I need to think about how to handle that a bit more. Thanks for the feedback!

Thanks! Getting it working on an embedded system would be a fun addition and a nice intro/training project for one of our new engineers (I think…).

What type of API are you thinking of? It already runs on a YAML config, so maybe a web server that takes the config as a JSON body instead?

Thanks for catching that! Updated to match. The names I liked was already taken on crates.io but never got it out of my head

Thanks for the feedback! So would a tagging system be useful? Right now you can declare dependencies on a single server, but maybe we can have it depend on at least one of the machines in a tagged group booting up?