Merge pull request #105 from skysqlinc/enterprise-community

NedPK · web-flow · commit 1b9f9bea6a99 · 2025-06-11T16:36:36.000+03:00
Rename Enterprise files to Community equivalents - Rename MariaDB Ent…
diff --git a/docs/Backup and Restore/MariaDB Backup.md b/docs/Backup and Restore/MariaDB Backup.md
diff --git a/docs/Backup and Restore/MariaDB Enterprise Backup.md b/docs/Backup and Restore/MariaDB Enterprise Backup.md
diff --git a/docs/Connecting to SkySQL DBs/Connect using ODBC.md b/docs/Connecting to SkySQL DBs/Connect using ODBC.md
@@ -213,7 +213,7 @@ An example of a failover host string:
 | --- | --- | --- |
 | DRIVER | • On Linux, the name of the driver, which is configured in the unixODBC driver template file. On macOS, the path to the driver's shared library, which is installed at /Library/MariaDB/MariaDB-Connector-ODBC/libmaodbc.dylib by default. |  |
 | SERVER | Host name, IPv4 address, or IPv6 address of the database server. | localhost |
-| SOCKET | The path to the socket file. On Linux, MariaDB Enterprise Server uses different default socket files on different Linux distributions. On Debian / Ubuntu, the default socket file is /var/run/mysqld/mysqld.sock or /run/mysqld/mysqld.sock. On CentOS / RHEL / Rocky Linux, the default socket file is /var/lib/mysql/mysql.sock. | /tmp/mysql.sock |
+| SOCKET | The path to the socket file. On Linux, MariaDB Mariadb Server uses different default socket files on different Linux distributions. On Debian / Ubuntu, the default socket file is /var/run/mysqld/mysqld.sock or /run/mysqld/mysqld.sock. On CentOS / RHEL / Rocky Linux, the default socket file is /var/lib/mysql/mysql.sock. | /tmp/mysql.sock |
 | DATABASE | Database name to select upon successful connection. The database must already exist, and the user account must have privileges to select it. |  |
 | PORT | TCP port of the database server. | 3306 |
 | USER | The username to use for authentication. |  |
diff --git a/docs/Connecting to SkySQL DBs/README.md b/docs/Connecting to SkySQL DBs/README.md
@@ -55,7 +55,7 @@ Applications can connect to SkySQL using any of the below MariaDB supported conn
 
 
 !!! Note
-    💡 For Enterprise Server With Replica(s), you can also use any MongoDB client and use the [NoSQL Interface](Connect%20from%20MongoDB%20clients.md)
+    💡 For <Mariadb> Server With Replica(s), you can also use any MongoDB client and use the [NoSQL Interface](Connect%20from%20MongoDB%20clients.md)
 
 
 ## Connecting from SQL tools
diff --git a/docs/Data loading, Migration/Import-CSV-data.md b/docs/Data loading, Migration/Import-CSV-data.md
@@ -17,13 +17,13 @@ Support for local infiles must be enabled on the client side and on the SkySQL s
 
 To execute the [`LOAD DATA LOCAL INFILE`](https://mariadb.com/kb/en/load-data-infile/) statement, most clients and connectors require a specific option to be enabled.
 
-If you are using `mariadb` client, the [`--local-infile` option](https://mariadb.com/docs/server/data-operations/data-import/enterprise-server/load-data-local-infile/) must be specified.
+If you are using `mariadb` client, the [`--local-infile` option](https://mariadb.com/docs/skysql-previous-release/data-operations/data-import/load-data-local-infile/) must be specified.
 
 ### **Enable Local Infiles in SkySQL**
 
 Support for local infiles must be enabled on the SkySQL service.
 
-For SkySQL services that use MariaDB Enterprise Server, the [local_infile system variable](https://mariadb.com/kb/en/server-system-variables/#local_infile) must be enabled:
+For SkySQL services that use MariaDB Server, the [local_infile system variable](https://mariadb.com/kb/en/server-system-variables/#local_infile) must be enabled:
 
 - For Replicated Transactions and Single Node Transactions services, the `local_infile` system variable is `OFF` by default
 
@@ -32,7 +32,7 @@ For SkySQL services that use MariaDB Enterprise Server, the [local_infile syst
 ## **Import Data**
 
 1. Determine the [connection parameters](<../../Connecting to Sky DBs/>) for your SkySQL service.
-2. Connect with the `mariadb` client and specify the [-local-infile option](https://mariadb.com/docs/server/data-operations/data-import/enterprise-server/load-data-local-infile/), which is needed by the next step:
+2. Connect with the `mariadb` client and specify the [-local-infile option](https://mariadb.com/docs/skysql-previous-release/data-operations/data-import/load-data-local-infile/), which is needed by the next step:
 
 ```bash
 mariadb --host FULLY_QUALIFIED_DOMAIN_NAME --port TCP_PORT \
diff --git a/docs/Data loading, Migration/Migrating Using a Logical Dump and Replication.md b/docs/Data loading, Migration/Migrating Using a Logical Dump and Replication.md
@@ -5,7 +5,7 @@ To minimize downtime during migration, you can set up live replication from your
 # Prerequisites
 
 1. An active SkySQL account. Identify requirements for your SkySQL implementation prior to [deployment](<../Portal features/Launch page.md>), including:
-- Topology - Enterprise Server Single node or with Replica(s)
+- Topology - Mariadb Server Single node or with Replica(s)
 - [Instance size](<../Reference Guide/Instance Size Choices.md>)
 - Storage requirements
 - Desired server version
diff --git a/docs/Data loading, Migration/README.md b/docs/Data loading, Migration/README.md
@@ -21,7 +21,7 @@ Below are the most common scenarios for database migration to SkySQL.
 Ensure that your SkySQL servce deploymned configuration is compatible with your existing source database one, including:
 <ul>
    <li><b>Deployment region</b> - Ensure that the SkySQL deployment region is the same as the source database region.</li>
-   <li><b>Topology</b> - Enterprise Server Single node or with Replica(s)</li>
+   <li><b>Topology</b> - Mariadb Server Single node or with Replica(s)</li>
    <li> <b>Server version</b> - Ensure that the SkySQL server version is compatible with the source database version. </li>
    <li><b>Instance size</b> - Ensure that the SkySQL instance is compatible with the source database instance type and size</li>
    <li><b>Storage</b> - Ensure that the SkySQL storage type and size is compatible with the source database</li>
diff --git a/docs/Data loading, Migration/SkySQL-managed-migration.md b/docs/Data loading, Migration/SkySQL-managed-migration.md
@@ -3,7 +3,7 @@
 ## Prerequisites
 
 1. An active SkySQL account. Identify requirements for your SkySQL implementation prior to [deployment](../Portal%20features/Launch%20page.md), including:
-    - Topology: Enterprise Server Single node or with Replica(s)
+    - Topology: Mariadb Server Single node or with Replica(s)
     - [Instance size](../Reference%20Guide/Instance%20Size%20Choices.md)
     - Storage requirements
     - Desired server version
diff --git a/docs/Reference Guide/README.md b/docs/Reference Guide/README.md
@@ -4,9 +4,9 @@
 
 ## [Configurable MariaDB Server variables:](<../config/README.md>)
 
--  [MariaDB Server Single Node](<../config/Enterprise-Server-Single-Node.md>)
+-  [MariaDB Server Single Node](<../config/Mariadb-Server-Single-Node.md>)
 
--  [MariaDB Server With Replica(s)](<../config/Enterprise-Server-with-Replica(s).md>)
+-  [MariaDB Server With Replica(s)](<../config/Mariadb-Server-with-Replica(s).md>)
 
 -  [SkySQL Intelligent Proxy Configuration](<../config/SkySQL-Intelligent-Proxy.md>)
 
@@ -20,8 +20,8 @@
 
 ## [SkySQL Monitoring Metrics Reference](<./Monitoring Metrics Reference.md>)
 
-## [MariaDB Enterprise Server Reference Guide](https://mariadb.com/docs/server/ref/mdb/)
+## [MariaDB Server Reference Guide](https://mariadb.com/kb/en/documentation/)
 
 ## [MaxScale Reference Guide](https://mariadb.com/docs/skysql-previous-release/ref/mxs22.08/)
 
-## [Setting up MariaDB Enterprise Server, ColStore, MaxScale in your Env](https://mariadb.com/downloads/repo-setup/)
+## [Setting up MariaDB Server, ColStore, MaxScale in your Env](https://mariadb.org/download/)
diff --git a/docs/Security/Encryption.md b/docs/Security/Encryption.md
@@ -12,7 +12,7 @@ For information on how to connect with TLS, see ["Connect and Query"](<../../Con
 The "Disable SSL/TLS" option may be appropriate for some customers when also using AWS PrivateLink or GCP VPC Peering.
 
 ### Server-to-Server
-SkySQL services perform server-to-server communication between MariaDB MaxScale, MariaDB Enterprise Server, MariaDB Xpand nodes, and SkySQL infrastructure.
+SkySQL services perform server-to-server communication between MariaDB MaxScale, MariaDB Server, and SkySQL infrastructure.
 
 By default, these server-to-server communications are protected with data-in-transit encryption:
 
diff --git a/docs/config/Mariadb-Server-Single-Node.md b/docs/config/Mariadb-Server-Single-Node.md
@@ -1,4 +1,4 @@
-For cloud databases with the Enterprise Server Single Node topology, the following Configuration Manager parameters are used to configure MariaDB Enterprise Server behavior:
+For cloud databases with the Mariadb Server Single Node topology, the following Configuration Manager parameters are used to configure MariaDB Server behavior:
 
 | Name | Default Value |
 |------|---------------|
diff --git a/docs/config/Mariadb-Server-with-Replica(s).md b/docs/config/Mariadb-Server-with-Replica(s).md
@@ -1,6 +1,6 @@
-For cloud databases with the Enterprise Server With Replica(s) topology, Configuration Manager can be used to configure MariaDB Enterprise Server behavior and MariaDB MaxScale behavior.
+For cloud databases with the Mariadb Server With Replica(s) topology, Configuration Manager can be used to configure MariaDB Server behavior and MariaDB MaxScale behavior.
 
-The following Configuration Manager parameters are used to configure MariaDB Enterprise Server behavior:
+The following Configuration Manager parameters are used to configure MariaDB Server behavior:
 
 | Name | Default Value |
 |------|---------------|
diff --git a/docs/config/README.md b/docs/config/README.md
@@ -17,8 +17,8 @@ To access the Configuration Manager interface:
 
 Available configuration parameters differ by cloud database topology.
 
-[1. Enterprise Server Single Node](./Enterprise-Server-Single-Node.md)
+[1. Mariadb Server Single Node](./Mariadb-Server-Single-Node.md)
 
-[2. Enterprise Server With Replica(s)](./Enterprise-Server-with-Replica(s).md)
+[2. Mariadb Server With Replica(s)](./Mariadb-Server-with-Replica(s).md)
 
 [3. SkySQL Intelligent Proxy Configuration](./SkySQL-Intelligent-Proxy.md)
diff --git a/mkdocs.yml b/mkdocs.yml
@@ -125,7 +125,7 @@ nav:
           - 'Backup and Restore/Restore From Your Own Bucket.md'
           - 'Backup and Restore/Point-in-Time Restore.md'
           - 'Backup and Restore/Restore Delete Examples.md'
-      - 'Backup and Restore/MariaDB Enterprise Backup.md'
+      - 'Backup and Restore/MariaDB Backup.md'
   - 'Migrations, Data Loading' :
       - 'Migrations' :
           - 'Data loading, Migration/README.md'
@@ -159,8 +159,8 @@ nav:
   - 'Configure your Database Server(s)' :
       - 'config/README.md'
       - 'config/Mariadb-Serverless-Single-Node.md'
-      - 'config/Enterprise-Server-Single-Node.md'
-      - 'config/Enterprise-Server-with-Replica(s).md'
+      - 'config/Mariadb-Server-Single-Node.md'
+      - 'config/Mariadb-Server-with-Replica(s).md'
       - 'config/SkySQL-Intelligent-Proxy.md'
   - 'Using AWS/Azure/GCP Private VPC Connections' :
       - 'Using AWS Azure GCP private VPC connections/README.md'

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-For cloud databases with the Enterprise Server Single Node topology, the following Configuration Manager parameters are used to configure MariaDB Enterprise Server behavior:`
	`1`	`+For cloud databases with the Mariadb Server Single Node topology, the following Configuration Manager parameters are used to configure MariaDB Server behavior:`
`2`	`2`
`3`	`3`	`\| Name \| Default Value \|`
`4`	`4`	`\|------\|---------------\|`