docker-compose env file


I've noticed that after tonight's changes connected with adding

environment file to docker-compose configuration, it became
impossible to start the projects locally with Docker, using * docker-compose
run*. The reason is missing .env file, that has been
specified in the configuration, but doesn’t exist on the three

Adding empty file broke the build, so I left it as is for now. I've

noticed that Jenkins has been configured to fetch the .env file,
containing database access, from the new openlmis-config repository
before each build. I’ve been wondering about the local development
flow though. Should we now manually create the .env files with
database access before starting the project? If so, I suppose we
should at least mention it in the “quick start” docs.

Best regards,

Sebastian Brudzinski.