From 2298af5ddac72aa4f4ec1f81d5f7720740994f54 Mon Sep 17 00:00:00 2001 From: allan-silverstein Date: Mon, 18 Apr 2022 15:34:37 -0400 Subject: [PATCH] Updated Deployment (markdown) --- Deployment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Deployment.md b/Deployment.md index 5f4301a..abf81de 100644 --- a/Deployment.md +++ b/Deployment.md @@ -5,7 +5,7 @@ But these techniques work equally well in the regular _docker-compose_-based app In this case, we encourage you to statically configure NetBox by starting from [NetBox's example config file][default-config], and mounting it into your container in the directory `/etc/netbox/config/` using the mechanism provided by your container platform (i.e. [Docker Swarm configs][swarm-config], [Kubernetes ConfigMap][k8s-config], [OpenShift ConfigMaps][openshift-config]). -But if you rather continue to configure your application through environment variables, you may continue to use [the built-in configuration file][docker-config]. +But if you'd rather continue to configure your application through environment variables, you may continue to use [the built-in configuration file][docker-config]. **We discourage storing secrets in environment variables**, as environment variable are passed on to all sub-processes and may leak easily into other systems, e.g. error collecting tools that often collect all environment variables whenever an error occurs. Therefore we *strongly advise* to make use of the secrets mechanism provided by your container platform (i.e. [Docker Swarm secrets][swarm-secrets], [Kubernetes secrets][k8s-secrets], [OpenShift secrets][openshift-secrets]).