How are you structuring your fly.io powered apps?
Approaches I thought about:
- all apps in a single org, separated by env through the name. e.g.: two apps, api-dev & api-prod. convenient because everything is under a single org but a bit dangerous
- one org for each env, e.g.
my-org-dev
andmy-foo-prod
. Kinda nice because I get separate billing
any other ideas? how are you organizing this?