Thanks to Mr Mick Thiele for reading the backlog of questions. I've added a couple of clarifications to the various posts below.
First, the boot.ini appsettings.{env,local} files are used by the boot process to, in the case of local mode, set the db_host and db_port values.
If you run a second winsome, you have only one copy of the boot.ini appsettings.{env,local} files. Both copies are used, and will each set the values in the other.
The result is that in any mode of operation (local, remote, shared), both winsome instances are using the same db_host and db_port. The local mode appsettings.{env,local} files are used to configure the db_host and db_port values.
So, for example, in shared mode, if you run two winsomes, each winsome will have its own db_host and db_port, but those values will be the same between the two winsomes. In local mode, both winsomes will have the same db_host and db_port values.
Another example, in shared mode, if you set the db_host value in one winsome, that will override the value for the same value in the other winsome.
Second, regarding the boot command, the appsettings.{env,local} files are not used by the boot process. The boot command sets db_host and db_port in the winmanager appsettings.local file.
Next, regarding boot command. I assume you mean the appsettings.{env,local} files are not used in local mode.
The boot command sets the db_host and db_port values in the winmanager appsettings.local file.
I guess I should clarify. The winmanager appsettings.local file (not the appsettings.{env,local} files) is read by the boot process. It is called by the boot process in the boot.ini appsettings.local file (in shared mode), and then later the winmanager.exe appsettings.local file (in local mode).
When in local mode, the winmanager appsettings.local file (not the appsettings.{env,local} files) is read by the boot process. It is called by the boot process in the boot
Related links:
Comments