We have our DNN application running in a Docker container. While we can build into the Docker container the values for the database connection into the web.config, best practices for containers is to have data such as connection strings available as environment variables.

This allows the container to dynamically determine the database connection at container startup time. Container management software, like Kubernetes, is able to spin up (or down) containers to account for traffic. So being able to dynamically determine the location of a database is valuable.

I have our application reading environment variables for it's database connection but it appears DNN does not have that capability?

Basically I'm looking for:

- A mechanism whereby DNN can read database connection strings from environment variables.

OR

- Can someone point me to the code that initially reads the connection string? I can then add logic to first look in environment variables.