Generic Host config root

[tmds]

Description

The generic host has the content root where it loads assets from. These assets fall into two separate categories:

• configuration files (appsettings.json)
• application resources (razor files, ...)

This is a request to be able to set the location for configuration files separate from the content root.

Use-Cases

For example, when placing a generic host app according to the Linux File Hierarchy, the config files can be under /etc/<app-name> and static assets under /usr/share/<app-name>.

Or when deploying an application using a container image, the config root would be a volume that enables changing and persisting settings.

API

No proposal yet.

[dotnet-policy-service]

Tagging subscribers to this area: @vitek-karas, @agocke, @VSadov
See info in area-owners.md if you want to be subscribed.

[tmds]

I ran into needing this more than once so I wrote it up as an issue to find out if others have needed it too.

[tmds]

It may be interesting to support the config root to be a set of directories where config files from. It is a common pattern for applications to use files from /etc and also from a user directory which overrides those settings.

[ericstj]

Also @halter73 since this would likely impact all hosting users. @tmds did you have an API suggestion you wanted to make?