You can host Lasernet Core configurations on a single Lasernet Config server or on multiple Lasernet Config servers. However, each of these approaches has advantages and disadvantages. See the following options.
Option 1 - Single Config Server (Single Configuration)
In Lasernet 9, Lasernet Core 10, and Lasernet Core 11, you can host a configuration on a single Lasernet Config Server and use only that configuration. All changes are made to that configuration and it is deployed when needed to different Lasernet Core environments/servers. The advantage of this approach is that you do not need to export and import changes between configurations, or export and import configurations between Config Servers.
The disadvantages of this approach arise when multiple people change the configuration at the same time, because they must follow strict processes around committing changes. This is because it is crucial that a Lasernet developer does not commit untested changes that are not ready to be deployed to production environments/servers. When they commit changes, they must select only approved and tested configuration changes to form part of the new configuration revision.
For example, suppose you have made changes to a form that require testing. As it is untested, this form change must not be committed. You can use Patch (Lasernet Developer 10) or Deploy Workspace (Lasernet Developer 11) to send the change to a Test server/environment. You commit the change to create a new revision only after it has been tested and approved. The new configuration revision can be deployed to a Production environment/server because the form change has been tested.
If you committed the untested change, you would have to ensure that you did not deploy that commit to a Production environment/server, because it includes a change that is not approved for production use.
Using a single Config Server to support multiple environments (Test, Production, etc) can work if you have a clear process that controls when changes are committed.
Option 2 - Multiple Configuration Servers
Each environment/server (Test, Production, etc) has a dedicated Config Server. Users can export and import configurations between the Config Servers. Deployment from each Config Server to its corresponding environment/server is straightforward (unlike Option 1), because each Config Server and Lasernet Core environment/server pair is entirely separate.
Option 3 - Single Config Server (Configuration Variants for Each Environment/Server)
The setup consists of a single Lasernet Config server that hosts environment/server-specific variants of each configuration. For example, if the Lasernet Core configuration is known as Configuration1 and the Lasernet Core system has two environments (Test and Production), the Config Server hosts two configurations: Configuration1-Test and Configuration1-Production.
Each configuration is deployed only to the corresponding environment/server. In other words, the Configuration1-Test configuration is deployed only to the Test Lasernet Core environment/server.
Changes are committed only to the appropriate configuration. For example, if a change to a form will require testing, that change is made in a new revision of the Configuration1-Test revision. Then, that configuration is deployed to the Test environment/server.
After the change is approved through testing, that change is exported from the Configuration1-Test configuration and imported into the Configuration1-Production configuration. Now that the Configuration1-Production configuration contains the tested change, it can be deployed to the Production Lasernet Core environment/server.
Because you have environment/server-dedicated configurations, you do not have to tightly control when changes are committed to each environment/server.