Does Orchard support some form of configuration conversions?

What is the "Orchard way" for defining environment configurations and / or configuration transformations? Can regular Web.config transforms be used as in any other ASP.NET web application, or does Orchard have its own engine for this?

(I haven't been able to find any useful information on this topic in the official docs or in the wild.)

+3


source to share


1 answer


It is entirely possible to store this information in the web.config just like in any other ASP.NET application. In many cases, this is the only way (e.g. setting up IIS for the environment, etc.).



You can also store your custom preferences in the Orchard database by writing your custom preferences portion and associating it with the Site content type. This is the preferred way to go if you have data to store that shouldn't be stored in the web.config file (alternatively to create a custom config section).

+1


source







All Articles