From 767991afe38f9f26ebe26e664feb902698255353 Mon Sep 17 00:00:00 2001 From: David Heinemeier Hansson Date: Mon, 30 Jan 2023 16:59:44 +0100 Subject: [PATCH] Clearer still --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index a65ee4ee..2b1e5377 100644 --- a/README.md +++ b/README.md @@ -46,7 +46,7 @@ Kubernetes is a beast. Running it yourself on your own hardware is not for the f ## Configuration -### Using .env to load required environment variables +### Using .env file to load required environment variables MRSK uses [dotenv](https://github.com/bkeepers/dotenv) to automatically load environment variables set in the `.env` file present in the application root. This file can be used to set variables like `MRSK_REGISTRY_PASSWORD` or database passwords. But for this reason you must ensure that .env files are not checked into Git or included in your Dockerfile! The format is just key-value like: