Differences

This shows you the differences between two versions of the page.

--- settings_instances [2022/12/27 12:00] – mehdi
+++ settings_instances [2023/11/22 15:37] (current) – chris
@@ Line 1: / Line 1: @@
 ===== Instances =====
-This page shows a list of configured instances of PMA.core. An instance of PMA.core is an installation of PMA.core that share the same database as part of a group of Instances. This section is particular relevant in the context of [[rootdir_geo_replication|geo-replication scenarios]].
+This page shows a list of configured instances of PMA.core. An Instance of PMA.core is an installation of PMA.core that shares the same database as part of a group of Instances. This section is particularly relevant in the context of [[rootdir_geo_replication|geo-replication scenarios]].
-Usually each instance is a replica of PMA.core at a different server and location. You can set an instance as the current running in this page by clicking on the //Edit -> Set current// button
+Usually each Instance is a replica of PMA.core at a different server and location. You can set an Instance as the current running in this page by clicking on the //Edit -> Set current// button
 {{::settings_instances.png?400|}}
-==== Adding a new instance ====
+==== Adding a new Instance ====
-Clicking on the //Add new instance// button will take you to the page to add a new Instance of PMA.core. The only needed information about an instance is a unique //Name// and a //Description//. After creating a new Instance you can set it as current via the index page by clicking on the //Edit -> Set current// button
+Clicking on the //Add new Instance// button will take you to the page to add a new Instance of PMA.core. The only required information about an Instance is a unique //Name// and a //Description//. After creating a new Instance you can set it as the current Instance via the index page by clicking on the //Edit -> Set current// button
 {{ :settings_instance_add.png?400 |}}
 ==== Warning ====
-PMA.core will not work correctly if the right instance is not selected as the current instance. This happens automatically when your PMA.core gets installed, but some scenarios after installation will cause the right instance not to be selected as the current instance.
+PMA.core will not work correctly if the right Instance is not selected as the current Instance. This happens automatically when your PMA.core gets installed, but there are some scenarios after installation that would cause the right Instance not to be selected as the current Instance.
-The first scenario is when a user adds an instance and selects it as the current instance. The newly created instance will not be linked to the request code, which will cause the root directories to not work. Learn more about [[rootdir|root directories]].
+The first scenario is when a user adds an Instance and selects it as the current Instance. The newly created Instance will not be linked to the request code, which will cause the root directories to stop working correctly. Learn more about [[rootdir|root directories]].
 {{ :root_dir_load_error.png?400 |}}
-In the second scenario, the PMA.core application folder gets moved. This causes PMA.core to generate a new request code and deselect the current instance because the current instance is still linked to the old request code. This will show an invalid license error message. Learn more about [[licensing|licensing]].
+In the second scenario, the PMA.core application folder gets moved. This causes PMA.core to generate a new request code and deselect the current Instance because the current Instance is still linked to the old request code. This will show an invalid license error message. Learn more about [[licensing|licensing]].
 {{ :invalid_license.png?400 |}}
-Please [[https://helpdesk.pathomation.com|contact us]] on our helpdesk if you encounter issues with your PMA.core.
+Please [[https://helpdesk.pathomation.com|contact us]] at our helpdesk if you encounter issues with your PMA.core.