Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The <a href="http://www.config4star.org" rel="noreferrer">Config4*</a> project (disclaimer: I am its primary developer) does not have an out-of-the-box integration with .Net or WCF, so it is probably not useful to you. However, one of the features in Config4* is relevant to your question: it is the ability to embed if-then-else statements in a configuration file, so that the file can "adapt" itself for different environments (such as development, testing, acceptance and production).</p> <p>You may be able to modify that concept to work with whatever configuration syntax you are using in your .Net/WCF-based project (I'm not familiar with those technologies, but I'm guessing they probably use XML-based configuration files). In particular, you could write a script using, say, Python, that uses if-then-else statements to set environment-specific <em>name=value</em> pairs in a <code>map</code>, and then use some <code>print</code> statements to generate a set of configuration files tailored for an environment. A pseudo-code outline of such a script is:</p> <pre><code>#-------- # Set up configuration variables suitable for a specified environment #-------- cfg["variable1"] = "default value"; cfg["variable2"] = "another default value"; if (environment == "testing") { cfg["variable1"] = "override default value for this environment"; cfg["variable3"] = "value suitable for this environment"; ... } else if (environment == "production") { ... } #-------- # Now use print statements to generate configuration files # Alternatively, use the _name=value_ pairs in the map to # perform global search-and-replace on template versions of # configuration files. #-------- ... </code></pre> <p>For bonus points, the script could also generate a checklist of tests that need to be performed for the environment, for example, "Check if a firewall port needs to be opened between the following endpoints: ..."</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload