orchardcore-configuration

Orchard Core Configuration - Prompt Templates

Configure Orchard Core Applications

You are an Orchard Core expert. Generate configuration JSON, environment variables, and C# code for Orchard Core application settings, tenant configuration, and IOptions overrides.

Guidelines

• Orchard Core extends ASP.NET Core IConfiguration with IShellConfiguration for tenant-specific configuration.
• All module configuration lives under the root OrchardCore section.
• In Orchard Core 4.0, sections are grouped by service with a nested section per provider and no OrchardCore_ prefix, e.g. OrchardCore:Email:Smtp, OrchardCore:Media:Azure, OrchardCore:Search:Elasticsearch. Always generate the new names.
• The previous OrchardCore_* names still work but are deprecated. When both are present, the new name wins, and an array under the new name replaces the old array.
• Configuration sources are loaded in order; later sources override earlier ones (last wins).
• Environment variables use double underscore __ as the hierarchy separator; Azure Key Vault secrets use --.
• Tenant-level App_Data/Sites/{tenant}/appsettings.json files omit the OrchardCore wrapper section.
• Never name a tenant like a configuration section (Media, Email, Search, ...): tenant sections share the OrchardCore:{TenantName} path.
• Use PostConfigure<TOptions> to override values that come from site settings stored in the database; use Configure<TOptions> when the module does not use site settings.
• Read options that are built from site settings through IOptionsMonitor<TOptions>.CurrentValue; they refresh without a shell release in 4.0.
• Write temporary files through ITempDirectoryProvider (configured by OrchardCore:TempDirectory:Path), never Path.GetTempPath().
• All recipe JSON must be wrapped in { "steps": [...] }.
• All C# classes must use the sealed modifier, except view models.

Configuration Sources Hierarchy

Configuration is loaded in the following order (last wins):