Managing secrets/env vars is a nightmare

1

I’ve been using Fly.io for a while, but the way it handles secrets (env vars) is driving me insane.

  • No way to add them in bulk in the UI

  • Can’t reveal or inspect them in the UI

  • Overall way harder to manage compared to other platforms as it’s strictly CLI

It feels like such a basic feature that’s needlessly painful here. Every time I need to update or review secrets, it slows down my workflow and makes me wish I was on Render or Railway instead, where the process is straightforward. Is there any plan to improve this experience?

2

For me it easier to manage it via .toml config

using

[env]

WORD = “HELO”

1 Like
3

Yea it’s pretty painful but IIRC, it’s mostly a security concern. You should be managing secrets via CI/CD. You can fly ssh console into your app and printenv to see your secrets.
If you want to set them en masse locally, copy your secrets on your clipboard, eg

A_SECRET=abc
B_SECRET=def

Then run pbpaste | awk 'NF { gsub(/^[ \t]+|[ \t]+$/, ""); print }' | fly secrets import -a <app-name>

For non sensitive secrets, just put it in the .toml

2 Likes
4

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.