[FEATURE] UI / Remove secrets and config from docker-compose deployments #93

Closed
opened 2025-10-09 16:58:13 -05:00 by giteasync · 4 comments
Owner

Originally created by @jlengelbrecht on GitHub.

What would you like to see implemented next?

Would it be possible to add a UI for this and remove the requirement to hardcode secrets such as apikeys and download client secrets in the compose? Really like the tool but i tend to gitopsify all my deployments would be really nice if i can just configure the tool form a UI once its spun up rather than having to hardcode everything in the docker-compose file. Don't get me wrong I know i could use a .env file but still would be nice to just provide the app the secrets its needs once its spun up through the UI.

Originally created by @jlengelbrecht on GitHub. ### What would you like to see implemented next? Would it be possible to add a UI for this and remove the requirement to hardcode secrets such as apikeys and download client secrets in the compose? Really like the tool but i tend to gitopsify all my deployments would be really nice if i can just configure the tool form a UI once its spun up rather than having to hardcode everything in the docker-compose file. Don't get me wrong I know i could use a .env file but still would be nice to just provide the app the secrets its needs once its spun up through the UI.
giteasync added the enhancement label 2025-10-09 16:58:13 -05:00
Author
Owner

@Flaminel commented on GitHub:

but i tend to gitopsify all my deployments

Wouldn't this make more sense through environment variables that you can supply from a vault store or something? But yeah, a web UI is already in the works.

@Flaminel commented on GitHub: > but i tend to gitopsify all my deployments Wouldn't this make more sense through environment variables that you can supply from a vault store or something? But yeah, a web UI is already in the works.
Author
Owner

@Flaminel commented on GitHub:

@AnthonyEnr1quez Please open a feature request. I'm not sure I can handle that gracefully, given that Cleanuparr is using a database now, but I'll look into it at some point.

@Flaminel commented on GitHub: @AnthonyEnr1quez Please open a feature request. I'm not sure I can handle that gracefully, given that Cleanuparr is using a database now, but I'll look into it at some point.
Author
Owner

@Flaminel commented on GitHub:

No need for these anymore. A web UI is available in v2.

@Flaminel commented on GitHub: No need for these anymore. A web UI is available in `v2`.
Author
Owner

@AnthonyEnr1quez commented on GitHub:

The new UI is slick! However, removing the ability to configure the application through env variables turns the deployment of this application from stateless to stateful (requiring persistent storage). A possible middle ground would be a config file that is mounted in the container.

I can open a new issue if necessary.

@AnthonyEnr1quez commented on GitHub: The new UI is slick! However, removing the ability to configure the application through env variables turns the deployment of this application from stateless to stateful (requiring persistent storage). A possible middle ground would be a config file that is mounted in the container. I can open a new issue if necessary.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/Cleanuparr#93