From c21a086a9f5f9c096751bf3fb6e7fd1c7ead59e8 Mon Sep 17 00:00:00 2001 From: hoclun-rigsep Date: Fri, 31 Jan 2025 20:00:12 -0500 Subject: [PATCH] fix usage in README --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 577f6a0..cc9ec49 100644 --- a/README.md +++ b/README.md @@ -219,7 +219,7 @@ see [javadoc](https://cdimascio.github.io/dotenv-java/docs/javadoc/) **Q:** Should I deploy a `.env` to e.g. production? -**A**: Tenant III of the [12 factor app methodology](https://12factor.net/config) states "The twelve-factor app stores config in environment variables". Thus, it is not recommended to provide the .env file to such environments. dotenv, however, is super useful in e.g a local development environment as it enables a developer to manage the environment via a file which is more convenient. +**A**: Tenet III of the [12 factor app methodology](https://12factor.net/config) states "The twelve-factor app stores config in environment variables". Thus, it is not recommended to provide the .env file to such environments. dotenv, however, is super useful in e.g a local development environment as it enables a developer to manage the environment via a file which is more convenient. Using dotenv in production would be cheating. This type of usage, however is an anti-pattern.