Products

Solutions

Resources

Partners

Community

About

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Connection strings as environment variablesConnection strings as environment variables
Previous
 
Next
New Post
10/31/2018 6:21 PM
 
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.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Connection strings as environment variablesConnection strings as environment variables


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out