Remove GCP content from docs (#3109)

Author: guimachiavelli

config/redirects.json

@@ -628,5 +628,10 @@
     "source": "/docs/reference",
     "destination": "/docs/reference/api/overview",
     "permanent": true
+  },
+  {
+    "source": "/docs/guides/deployment/gcp",
+    "destination": "/guides/deployment/running_production",
+    "permanent": true
   }
 ]

config/sidebar-guides.json

@@ -153,11 +153,6 @@
         "label": "Deploy on DigitalOcean",
         "slug": "digitalocean"
       },
-      {
-        "source": "guides/deployment/gcp.mdx",
-        "label": "Deploy on GCP",
-        "slug": "gcp"
-      },
       {
         "source": "guides/deployment/koyeb.mdx",
         "label": "Deploy on Koyeb",

guides/deployment/gcp.mdx

@@ -45,8 +45,6 @@ You can use Meilisearch API wrappers in your favorite language. These libraries
   - Guide: [How to deploy a Meilisearch instance on Amazon Web Services](/guides/deployment/aws)
 - [meilisearch-digitalocean](https://github.com/meilisearch/cloud-providers/)
   - Guide: [How to deploy a Meilisearch instance on DigitalOcean](/guides/deployment/digitalocean)
-- [meilisearch-gcp](https://github.com/meilisearch/cloud-providers/)
-  - Guide: [How to deploy a Meilisearch instance on Google Cloud Platform](/guides/deployment/gcp)
 - [meilisearch-kubernetes](https://github.com/meilisearch/meilisearch-kubernetes)
 
 ## Platform plugins

learn/resources/sdks.mdx

@@ -134,7 +134,7 @@ This list is liable to change with every new version of Meilisearch. It's not be
 | `system.cores`                                     | Number of cores                                                                             | 24
 | `system.ram_size`                                  | Total RAM capacity. Expressed in `KB`                                                       | 16777216
 | `system.disk_size`                                 | Total capacity of the largest disk. Expressed in `Bytes`                                    | 1048576000
-| `system.server_provider`                           | Users can tell us on which provider Meilisearch is hosted by filling the `MEILI_SERVER_PROVIDER` environment variable. This is also filled by our cloud deploy scripts, for example, [GCP cloud-config.yaml](https://github.com/meilisearch/cloud-scripts/blob/56a7c2630c1a508e5ad0c0ba1d8cfeb8d2fa9ae0/scripts/providers/gcp/cloud-config.yaml#L33) | GCP
+| `system.server_provider`                           | Users can tell us on which provider Meilisearch is hosted by filling the `MEILI_SERVER_PROVIDER` environment variable. This is also filled by Meilisearch cloud deploy scripts | AWS
 | `stats.database_size`                              | Database size. Expressed in `Bytes`                                                         | 2621440
 | `stats.indexes_number`                             | Number of indexes                                                                           | 2
 | `start_since_days`                                 | Number of days since instance was launched                                                  | 365

learn/resources/telemetry.mdx

@@ -157,12 +157,11 @@ chmod +x meilisearch
 
 ## Other cloud services
 
-To deploy Meilisearch on a cloud service, follow one of our dedicated guides:
+To deploy Meilisearch on a third-party cloud service, follow one of our dedicated guides:
 
 - [AWS](/guides/deployment/aws)
 - [Azure](/guides/deployment/azure)
 - [DigitalOcean](/guides/deployment/digitalocean)
-- [GCP](/guides/deployment/gcp)
 - [Koyeb](/guides/deployment/koyeb)
 - [Qovery](/guides/deployment/qovery)
 - [Railway](/guides/deployment/railway)

learn/self_hosted/install_meilisearch_locally.mdx

@@ -8,7 +8,7 @@ sidebarDepth: 3
 
 Currently, Meilisearch databases are only compatible with the version of Meilisearch used to create them. The following guide will walk you through using a [dump](/learn/advanced/dumps) to migrate an existing database from an older version of Meilisearch to the most recent one.
 
-If you're updating your Meilisearch instance on cloud platforms like DigitalOcean, AWS, or GCP, ensure that you can connect to your cloud instance via SSH. Depending on the user you are connecting with (root, admin, etc.), you may need to prefix some commands with `sudo`.
+If you're updating your Meilisearch instance on cloud platforms like DigitalOcean or AWS, ensure that you can connect to your cloud instance via SSH. Depending on the user you are connecting with (root, admin, etc.), you may need to prefix some commands with `sudo`.
 
 If migrating to the latest version of Meilisearch will cause you to skip multiple versions, this may require changes to your codebase. [Refer to our version-specific update warnings for more details](#version-specific-warnings).
 
@@ -99,7 +99,7 @@ Once the status is `processed`, you're good to go. Repeat this process for all i
 
 Before creating your dump, make sure that your [dump directory](/learn/self_hosted/configure_meilisearch_at_launch#dump-directory) is somewhere accessible. By default, dumps are created in a folder called `dumps` at the root of your Meilisearch directory.
 
-**Cloud platforms** like DigitalOcean, AWS, and GCP are configured to store dumps in the `/var/opt/meilisearch/dumps` directory.
+**Cloud platforms** like DigitalOcean and AWS are configured to store dumps in the `/var/opt/meilisearch/dumps` directory.
 
 If you're unsure where your Meilisearch directory is located, try this: