Hi Beatrix,

The first thing that comes to my mind is using something like sed in some script. Another one is changing it via SQL - "set property VERBOSELEVEL of server to 1" - it affects immediately.

In both cases I don't know if the server was installed totally new or just a new version over an existing one.

Yes, you don't know, but why it bothers you?

The first approach could be implemented in some post_install script running from the installer as a final step.
So, you know the installation directory, vServer actual name, and so, you know actual INI, and you may modify VERBOSELEVEL there using "sed".

The second approach is about to be implemented in your app, so any time it runs, it may check the VERBOSELEVEL and change it if needed. And VERBOSELEVEL changes are immediately applied to the vServer, so no need to restart vServer.

Regarding "what if the new vServer version has new/renamed variables" in the INI, but user has an "old" iNI.

"Renamed vars" - is always safe to keep "old" ones, internally it's implemented in this way - the "old" name becomes an alias to the "new" name.

"New vars" - each INI param has a default value, so if no "new var" is mentioned in the INI, it will be inited with the default value, so it would not be something like "missing new features" issue.

Thanks! I have been overthinking as usual. Then I'll just change the default ini file.

The users of the version of my app with Valentina Server are not really the sys admins I expected the app to use. Therefore, I do everything I can to simplify the installation.