When creating a new Umbraco Cloud instance projects start with a launchSettings.json that has the ASPNETCORE_ENVIRONMENT set to Development. This is pretty standard practice however when a project grows and a Development environment is added Umbraco Cloud uses "Development" for this environment too. So any local specific settings for this environment are also reused for the remote Development environment too.
Wouldn't it make more sense to start off on the right foot and include "Local" by default as launchSettings.json is only ever used for local development?
This is something that we change on our projects right away but it might be a nice quality of life feature for new projects.
Issue description
When creating a new Umbraco Cloud instance projects start with a launchSettings.json that has the ASPNETCORE_ENVIRONMENT set to Development. This is pretty standard practice however when a project grows and a Development environment is added Umbraco Cloud uses "Development" for this environment too. So any local specific settings for this environment are also reused for the remote Development environment too.
Wouldn't it make more sense to start off on the right foot and include "Local" by default as launchSettings.json is only ever used for local development?
This is something that we change on our projects right away but it might be a nice quality of life feature for new projects.