Lio李歐
Lio李歐
Yeah, we should clean up the warnings/errors for this. The idea is that `defang config` always overrides environment that was set in the `compose.yaml`, but we should show more than...
This would fix #420
Examples, https://github.com/DefangLabs/defang-mvp/blob/5ddb064cfcdf218a14caa7b004bba568ac063d24/fabric/cmd/server/fabric.go#L646 https://github.com/DefangLabs/defang-mvp/blob/e4e49fefc0e050da4dece1273cf76e95fda5e041/fabric/cmd/server/fabric_utils.go#L82 https://github.com/DefangLabs/defang-mvp/blob/f44705a430aac7c0a986fa1ba171322b18e64da8/fabric/cmd/server/fabric_grpc.go#L802 https://github.com/DefangLabs/defang-mvp/blob/5ddb064cfcdf218a14caa7b004bba568ac063d24/fabric/cmd/server/fabric.go#L684
`tail` should be replaced with something like `docker logs` with optional "follow"
Duplicate of https://github.com/DefangLabs/defang/issues/459
Do you mean during generation or during deployments? Or when?
Progress bar is hard to do. Alternatively, a better spinner that shows more activity. See also DefangLabs/defang-mvp#1090
Special case for `CI=1` is not great. I feel that will get abused since it's a good feature to use even locally. We should expose it in some other way....
Also would be useful to add to our shell script installer.
Not important enough. Can use the alternative installers instead.