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
Cosmos cannot support env files as-is because it does not use "files" to start composes
The only thing that I could consider adding are setting fields when importing a compose with envs in them
azukaar
changed the title
[BUG]: env_file is ignored when importing a docker-compose
[FEAT]: Allow setting env settings from UI when importing compose
Feb 4, 2025
As a first-step, could it import the values from the specified file? I know that might not just work because the env_file format gets preprocessed in some manner (something about how shells handle variables?), but having the skeleton - even with wrong values - would be easier than having to manually re-add variables. Especially when combined with a warning about that not working as expected.
For example, when setting up PeerTube according to official documentation.
The text was updated successfully, but these errors were encountered: