Could you go into one more level of detail about your app? I think this will help me better understand content for some documentation. Here's the rough bits of

Could you go into one more level of detail about your app? I think this will help me better understand content for some documentation. Here's the rough bits of what Fly has: 1. There's a release command (https://fly.io/docs/reference/configuration/#run-one-off-commands-before-releasing-a-deployment https://fly.io/docs/reference/configuration/#run-one-off-com...) that runs after the container is built, but before its deployed. In Rails that's when a database migration would be run. 2. To run a task after the application is deployed, there's shell access. Here's what that looks like for running Rails tasks: https://fly.io/docs/rails/the-basics/run-tasks-and-consoles/ https://fly.io/docs/rails/the-basics/run-tasks-and-consoles/ 3. Pre-deployment/build commands can be run from the Dockerfile, like a Rails asset compilation. Here's a link to that https://github.com//superfly/flyctl/blob/master/scanner/templates/rails/standard/Dockerfile#L84 https://github.com//superfly/flyctl/blob/master/scanner/temp... I recognize that this is a lot for folks who aren't comfortable configuring stuff and want the "no-config ease" of Heroku, but it's at least possible on Fly.