Hi I have 2 servers, test and production. I setup my Umbraco with app settings as below appsettings.json - local development appsettingsDevelopment.json - test server appsettingsProduction.json - production server Local uses SQLLite. If I have different connection string settings in appsettings (for my local development) and development files my local version never works and throws an error. If I remove the connection string from development then everything works locally but it means I've got a development config file that is now wrong. Am I missing something?

use secrets appsettings for your local settings.

In .NET applications, the ASP.NET Core configuration system loads configuration in a specific order, which includes merging and overriding settings based on the environment.

Umbraco adds a appsettings.local.json to the config. I tend to use appSetting.json as production The environment versions to override good defaults. Modelsbuilder for example is only in my local version

@TigerMan Ambert has given you the answer but I just want to check you've seen the subtle difference. You said you have: appsettingsDevelopment.json - test server appsettingsProduction.json - production server These should be appsettings.Development.json - test server appsettings.Production.json - production server The environment variable is between the two dots - this might explain your confusion and why things aren't working as you'd expect (or you had a simple typo in your question).

Hi yes I noticed that.... My phone auto corrected it and I didn't change it back. Thanks for highlighting 👍

The typical scenario is - appSettings.json - global settings that apply to all environments (e.g., general Umbraco config) - appSettings.Development.json - settings that apply to all development environments (e.g., runtime mode development) - appSettings.[Environment].json - environment settings (e.g., runtime mode, connection strings) - user secrets - development-environment-specific config (e.g., connection strings, email addresses) Not sure if user secrets can get the Umbraco and other schemas, otherwise just copy a full appSettings and modify it. So, don't use appSettings.json for any "local development" config.

as the user secrets.appsettings exist at

C:\Users\mikec\AppData\Roaming\Microsoft\UserSecrets\{GUID}

as long as you update the schema to be an absolute path to the

./appsettings-schema.json

you can get the intellisence in the secrets. eg

"$schema": "D:\\_work\\PROJECT\\src\\www\\appsettings-schema.json",