file-config | Store and read configuration values using files | Configuration Management library

In Helidon MP version 2.4.0, you'll need to follow Jersey's instructions for integrating with MicroProfile Config, bearing in mind that Helidon's MicroProfile Config implementation will already be taken care of so there's no need to duplicate that dependency.

In my opinion Helidon should take care of this for you, but in version 2.4.0 at least it does not.

This is a config issue, you are using io.helidon.Config.create() which doesn't support microprofile-config.properties.

If you use Server.create().start(), microprofile-config.properties will work out-of-the-box.

If you want to pass your own instance of config, you can do it like this:

You also need to install the extensions "org.wildfly.extension.microprofile.config-smallrye" and "org.wildfly.extension.microprofile.opentracing-smallrye" before adding the subsystems. Also wildfly provides a standalone-microprofile.xml that can server as example.

You were pretty close, just follow the rules mentioned in the docu:

1. Replace each character that is neither alphanumeric nor _ with _; then convert the name to upper case (i.e. COM_ACME_SIZE)

So given we have a config property named server.environments[0].apps[0].name when you replace each non-alfanumeric character with _ and convert to upper case you end up with: SERVER_ENVIRONMENTS_0__APPS_0__NAME. Note the double underscore between 0 and APPS as you substitute both . and [ for _. That will certainly not win any prize for the prettiest env var name but it does the job :).

You can check how exactly it is done in the Smallrye implementation of MP config - which is the implementation used by Quarkus.

Judging by the docs the filenames should have 2 underscores and you only have one:

The double-underscore (__) is used as a configuration key delimiter in file names. For example, the file name Logging__LogLevel__System produces the configuration key Logging:LogLevel:System.

Indeed you have a clash in RestEasy (transitive) dependencies in your project:

If you want to set mp.config.profile from server.env, you probably need to set MP_CONFIG_PROFILE instead.

Since dots aren't valid in environment variable names, MP Config defines some mapping rules when looking up config from environment variables. It will check for the requested name with non-alphanumeric characters converted to underscores, and then again also with all letters converted to uppercase.

Enforcing privacy for images is not as simple as documents for the reasons described in this issue:

https://github.com/wagtail/wagtail/issues/3880#issuecomment-332798643

That issue has been referenced more recently, so i believe is still the case. It is marked as 'someday' (valid but lower priority).

This is not a full answer, but hopefully helps articulate the problem.

You can try injecting the IOptions pattern from .NET Core into your class.

Do this as follows:

Suppose your appSettings.json is as shown: