Blueprints: Autostart and stop internal apps + Resiliency by Machine

[andie]

We posted a little while back to tell you about a new library of docs that describe repeatable patterns and examples that you can use for your own projects: Fly.io Blueprints

This week we added two more:

• Resilient apps use multiple Machines - Make your app resilient to single-host failures with multiple Machines that stay stopped until you need them.
• Autostart and autostop internal apps - Use a Flycast address to get Fly Proxy features, like autostart and autostop, for apps that are exposed only on your private network.

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

[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.

[danwetherald]

Can we please get consistent and consolidated articles when it pertains to SQLite, LiteFS, and multi-process Rails apps on Fly?

At the moment, the articles seem to reference old fly configurations, sundowned litefs cloud, etc.

When using the docker generate --litefs it will basically create a half connected and broken configuration. (a docker-entrypoint is created but not used, fly process group start up commands are broken, etc.

You can read more here: https://community.fly.io/t/deploy-rails-7-2-sqlite-with-litefs-error-too-many-arguments

For example, this article references a fly rake task which is no longer a part of fly deployments in rails: SQLite3 · Fly Docs