3 ms·
I move my private projects from Heroku to Fly.io. It wasn't as easy as advertised, but oh well, it works now. There's one thing that's straight out frustrating
by odiroot 4y ago
I move my private projects from Heroku to Fly.io. It wasn't as easy as advertised, but oh well, it works now.
There's one thing that's straight out frustrating: no support for easy environment variables management. Yes you can add secrets but it's hard to read them back. Not everything is a secret, e.g. log level.
- tptacek 4y agoYou can set environment variables directly in your `fly.toml`. https://fly.io/docs/reference/configuration/#the-env-variables-section https://fly.io/docs/reference/configuration/#the-env-variabl... You can't read secrets back once you've set them. That's because we can't read secrets back once we've set them --- at least, our API can't. The API has write-only access to our secret storage.
- odiroot 4y agoI'm fully aware of this but it doesn't help. I'd have to commit every change to variables into Git. Environment is not code. And Heroku had it figured out. And mind you, Fly.io is trying to sell itself as natural Heroku competitor.