Blueprints: Autostart and stop internal apps + Resiliency by Machine

[mayailurus]

@andie

Let us know if there’s a pattern or problem/solution you’d like to see as a Fly.io blueprint.

Thanks, I really like this new series… Another good topic, if time permits, might be the intricacies of altering background workers for LiteFS:

• Forcing Workers to only run on Primary machine

• Rails app running SQLite with LiteFS: “cannot rollback - no transaction is active”

• LiteFS GET request containing writes + LiteFS with multiple processes [monitoring the status stream]

• Unable to import remote instance LiteFS [image-conversion workers]

Answering all those simultaneously doesn’t necessarily fit into the “blueprints” style, but even one, going into a lot of detail (and not assuming that the reader knows what FUSE is, etc.), would be helpful, I bet.