Nicolas De loof
Nicolas De loof
Would be a significant architectural change Also to be considered: what would be expected if build fails ? Should the already running services be stopped (like when you hit Ctrl+C...
Adding support for this feature would require a significant redesign of compose architecture. I don't expect this to happen within the existing codebase. Tagged feature request for "future major release"...
@mTsBucy1 regression was introduced by a commit which is a fix for another issue. Considering a "revert on bug" strategy would prevent we move forward with Compose codebase, and is...
@idsulik sounds good to me, I don't think we have a better option with current compose-go architecture.
IIUC you'd expect `compose ps` command to warn about invalid project name set in env file? How does this relates to `PORT` not being defined? With the current architecture, project...
closing as user didn't provided any feedback for long
@elgordodevops use: ```yaml services: redis: networks: - my_network networks: my_network: name: ${NETWORK_NAME} ``` Anyway, IIRC we added support for interpolation on resources keys some time ago, I wonder this is...
@elgordodevops key used in `networks` doesn't matter, as long as you use a `name` attribute to set the actual network name. But `services.xx.networks` must refer to network by this key
Not sure about the root cause, but you can disable this by running with `COMPOSE_MENU=false` environment variable set
closing for inactivity