Per service environment variables #3001
nuxwin
started this conversation in
Feature Requests
Replies: 1 comment
-
Hi @nuxwin . I'm trying to install Harbor Registry in my VPS with coolify. Can you share your compose? I tried many times but always got error in all services |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Good morning,
I'm using latest Coolify v4.0.0-beta.320 PaaS platform version on my own infrastructure (the
next
image).Right now, it is possible to define shared environment variables on a team, project and environment basis.
When creating a new "resource", for instance using the Docker compose option, we can have one to many involved services. Right now, It is possible to define environnlent variables for the project.
As I said, the project is composed of several services. So, it could be great to be able to define environment variables on a per service basis too, rather than poluting all containers with environment variables defined at the project level which are not relevant for all containers.
In the hope that you understand my sentence there. Below, you can find a screeshot of my project (Harbor Registry) which is composed of many services (many containers). I would want be able to define environment variables on a per service basis, (Log, Registryctl ....)
Thank you.
Beta Was this translation helpful? Give feedback.
All reactions