You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now we could manage compose-file and env of a stack in a single place.
I recently encountered a case where I would like to deploy a nginx service which should be configured via config file. Thanks to configs feature, I could create a config and reference it in the stack compose file.
This works fine, but could be better if we can create files in the stack UI and reference it in compose file with config file syntax (see how they reference ./my_config.txt). In this way, we could group all related things in one place without the need to manage another global resource.
This discussion was converted from issue #1904 on July 27, 2023 04:22.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Thanks with a picture:
Now we could manage compose-file and env of a stack in a single place.
I recently encountered a case where I would like to deploy a nginx service which should be configured via config file. Thanks to
configsfeature, I could create a config and reference it in the stack compose file.This works fine, but could be better if we can create files in the stack UI and reference it in compose file with config file syntax (see how they reference
./my_config.txt). In this way, we could group all related things in one place without the need to manage another global resource.Beta Was this translation helpful? Give feedback.
All reactions