darwindarak

8 ms·

1. 1.▲
   by darwindarak 2y ago

   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 ei
2. 2.▲
   by darwindarak 2y ago

   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
3. 3.▲
   by darwindarak 2y ago

   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
4. 4.▲
   by darwindarak 2y ago

   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?
5. 5.▲
   Show HN: rallyup – Lightweight Wake-on-LAN Scheduler(github.com)

   141 points by darwindarak 2y ago|25 comments
6. 6.▲
   by darwindarak 11y ago

   The hollow shells are just contours used for visualization, the vortex rings are not actually hollow (as in no fluid in the region). As for tracking particles near vortex rings, I thing you're looking for something like http:/&#