Managing fly apps and dependencies as "infrastructure as code"

Questions / Help
3

Answering your questions in order:

  1. We have a preview feature for running multiple processes as a logical grouping in an app, but it’s not really designed for this use case. That’s more for something like a web+worker scenario.

  2. There’s no way to do this with fly.toml, but also something we’re thinking about.

  3. fly secrets import will import key=value pairs from stdin, i.e. cat .env | fly secrets import

  4. Many options in fly.toml can be overridden on the command line, such as env vars. That said, if you already env vars in fly.toml and try to use fly deploy -e, a bug will get in your way.

Generally speaking, we plan to pull a good amount of config into fly.toml but only after we migrate to some newer deployment plumbing we’re working on. Happy to expand on that if you’re interested. Stay tuned!

3 Likes
flyctl secrets import issue