Closed kwypchlo closed 2 years ago
Is that a good idea? I would definitely prefer it to alert me if that file is not there. If dc
runs with default setup instead of the one I expect from it that can cause a bunch of problems.
Is that a good idea? I would definitely prefer it to alert me if that file is not there. If
dc
runs with default setup instead of the one I expect from it that can cause a bunch of problems.
the error is thrown anyway, the stack will not start/stop since the services rely on the .env file (see the after error)
the only change is that grep in dc will not print the error, docker-compose (bottom of the file) will exit with code 14 and print the proper error
dc should not report error when .env does not exist (it just logs error, doesn't really break the script anyway), docker-compose will report on that and exit with proper error code
before
after