Move config to /etc/netbox/config (Fixes #54)
With this the configuration is moved to /etc/netbox/config and the default reports directory is set to /etc/netbox/reports. This enables the user to mount reports from a config map or persistent volume in OpenShift.
This commit is contained in:
parent
5b62a4c0ad
commit
b46bd58e0a
8 changed files with 11 additions and 11 deletions
|
@ -80,7 +80,7 @@ You should therefore adjust the configuration for production setups, at least th
|
|||
|
||||
You may run this image in a cluster such as Docker Swarm, Kubernetes or OpenShift, but this is advanced level.
|
||||
|
||||
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/` using the mechanism provided by your container platform (i.e. [Docker Swarm configs][swarm-config], [Kubernetes ConfigMap][k8s-config], [OpenShift ConfigMaps][openshift-config]).
|
||||
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].
|
||||
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.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue