Welcome to umbraco-servervariables Discussions!

[iOvergaard]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[thenexus00]

It is a bit dangerous having something that can expose appsettings through JSON. I had quick look and if you pick up this is used on a project it is very easy to expose all settings get the database connection and do some bad stuff with that with no issues at all. I do not like that.
In terms of views.. It is a very small helper function to make exposing the settings easier if you wanted but all you need to do is inject IConfiguration and then you have config access nativily.

[iOvergaard]

This package is an attempt to recreate the concept of "server variables" that was possible in Umbraco 13 and before: https://github.com/umbraco/Umbraco-CMS/blob/v13/dev/src/Umbraco.Core/Notifications/ServerVariablesParsingNotification.cs

It does not expose database settings, and although you can define variables in ServerVariables:vars in appsettings, it is not required to use appsettings at all. You inject the IServerVariablesService and can set the variables programmatically.

You can, of course, implement IConfiguration in your controllers and access settings that way as well, but this package helps you access those settings through the JavaScript code in the backoffice.

[thenexus00]

The new backoffice does offer the server variables up natively.
While your package does not expose database it exposes appsettings which will include the Database connection information thus giving you the entire database unless it has been properly locked to an IP access etc (Which most wont).