From 4c8e5885d5f27088c1d817fa5cbac79ed4efc331 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Petra=20Va=C5=88kov=C3=A1?= Date: Sun, 18 Jan 2026 00:33:04 +0100 Subject: [PATCH] rename scaling file --- apps/docs/content/alpine/how-to/create.mdx | 2 +- apps/docs/content/bun/how-to/create.mdx | 2 +- apps/docs/content/clickhouse/overview.mdx | 2 +- apps/docs/content/deno/how-to/create.mdx | 2 +- apps/docs/content/dotnet/how-to/create.mdx | 2 +- apps/docs/content/elixir/how-to/create.mdx | 2 +- apps/docs/content/features/pipeline.mdx | 4 +- .../features/{scaling-ha.mdx => scaling.mdx} | 0 apps/docs/content/gleam/how-to/create.mdx | 2 +- apps/docs/content/go/how-to/create.mdx | 2 +- apps/docs/content/homepage.mdx | 2 +- apps/docs/content/java/how-to/create.mdx | 2 +- apps/docs/content/keydb/how-to/create.mdx | 2 +- apps/docs/content/keydb/how-to/scale.mdx | 6 +- apps/docs/content/mariadb/how-to/create.mdx | 2 +- apps/docs/content/mariadb/how-to/scale.mdx | 6 +- .../content/mariadb/tech-details/cluster.mdx | 2 +- .../mariadb/tech-details/limitations.mdx | 2 +- apps/docs/content/nodejs/how-to/create.mdx | 2 +- apps/docs/content/php/how-to/create.mdx | 2 +- .../docs/content/postgresql/how-to/create.mdx | 8 +- apps/docs/content/postgresql/how-to/scale.mdx | 6 +- apps/docs/content/python/how-to/create.mdx | 2 +- .../content/references/networking/ssh.mdx | 6 +- apps/docs/content/rust/how-to/create.mdx | 2 +- apps/docs/content/ubuntu/how-to/create.mdx | 2 +- apps/docs/sidebars.js | 2 +- .../src/components/content/create-scaling.mdx | 2 +- apps/docs/src/components/content/scaling.mdx | 18 ++--- apps/docs/static/llms-full.txt | 74 +++++++++---------- apps/docs/static/llms-small.txt | 68 ++++++++--------- apps/docs/static/llms.txt | 2 +- 32 files changed, 120 insertions(+), 120 deletions(-) rename apps/docs/content/features/{scaling-ha.mdx => scaling.mdx} (100%) diff --git a/apps/docs/content/alpine/how-to/create.mdx b/apps/docs/content/alpine/how-to/create.mdx index eb9cabb5..dbd449f4 100644 --- a/apps/docs/content/alpine/how-to/create.mdx +++ b/apps/docs/content/alpine/how-to/create.mdx @@ -161,7 +161,7 @@ S3_ACCESS_KEY_ID="P8cX1vVVb" S3_ACCESS_SECRET="ogFthuiLYki8XoL73opSCQ" ``` -The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling-ha#single-container-mode)(/features/scaling-ha#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set. +The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode)(/features/scaling#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set. #### Description of description.yaml parameters diff --git a/apps/docs/content/bun/how-to/create.mdx b/apps/docs/content/bun/how-to/create.mdx index c4456b78..0d68210e 100644 --- a/apps/docs/content/bun/how-to/create.mdx +++ b/apps/docs/content/bun/how-to/create.mdx @@ -165,7 +165,7 @@ S3_ACCESS_KEY_ID="P8cX1vVVb" S3_ACCESS_SECRET="ogFthuiLYki8XoL73opSCQ" ``` -The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling-ha#single-container-mode)(/features/scaling-ha#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set. +The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode)(/features/scaling#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set. #### Description of description.yaml parameters diff --git a/apps/docs/content/clickhouse/overview.mdx b/apps/docs/content/clickhouse/overview.mdx index 70c2be1d..8f929373 100644 --- a/apps/docs/content/clickhouse/overview.mdx +++ b/apps/docs/content/clickhouse/overview.mdx @@ -23,7 +23,7 @@ Our ClickHouse implementation features optimized default settings designed for a ### Resource Allocation -Zerops automatically allocates resources to your ClickHouse service based on demand within the limits defined in your [automatic scaling configuration](/features/scaling-ha). +Zerops automatically allocates resources to your ClickHouse service based on demand within the limits defined in your [automatic scaling configuration](/features/scaling). ## High Availability and Deployment Modes diff --git a/apps/docs/content/deno/how-to/create.mdx b/apps/docs/content/deno/how-to/create.mdx index 2c12bb1f..420682a6 100644 --- a/apps/docs/content/deno/how-to/create.mdx +++ b/apps/docs/content/deno/how-to/create.mdx @@ -160,7 +160,7 @@ S3_ACCESS_KEY_ID="P8cX1vVVb" S3_ACCESS_SECRET="ogFthuiLYki8XoL73opSCQ" ``` -The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling-ha#single-container-mode)(/features/scaling-ha#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set. +The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode)(/features/scaling#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set. #### Description of description.yaml parameters diff --git a/apps/docs/content/dotnet/how-to/create.mdx b/apps/docs/content/dotnet/how-to/create.mdx index b82aac4a..35a0f6ac 100644 --- a/apps/docs/content/dotnet/how-to/create.mdx +++ b/apps/docs/content/dotnet/how-to/create.mdx @@ -161,7 +161,7 @@ S3_ACCESS_KEY_ID="P8cX1vVVb" S3_ACCESS_SECRET="ogFthuiLYki8XoL73opSCQ" ``` -The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling-ha#single-container-mode)(/features/scaling-ha#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set. +The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode)(/features/scaling#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set. #### Description of description.yaml parameters diff --git a/apps/docs/content/elixir/how-to/create.mdx b/apps/docs/content/elixir/how-to/create.mdx index 2213fea9..3e0676fe 100644 --- a/apps/docs/content/elixir/how-to/create.mdx +++ b/apps/docs/content/elixir/how-to/create.mdx @@ -160,7 +160,7 @@ S3_ACCESS_KEY_ID="P8cX1vVVb" S3_ACCESS_SECRET="ogFthuiLYki8XoL73opSCQ" ``` -The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling-ha#single-container-mode)(/features/scaling-ha#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set. +The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode)(/features/scaling#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set. #### Description of description.yaml parameters diff --git a/apps/docs/content/features/pipeline.mdx b/apps/docs/content/features/pipeline.mdx index 92727791..33aba5c1 100644 --- a/apps/docs/content/features/pipeline.mdx +++ b/apps/docs/content/features/pipeline.mdx @@ -323,12 +323,12 @@ For [manual deployments](#manual-deploy-using-zerops-cli) using Zerops CLI, the Zerops uses the stored artifact to deploy identical versions of your application whenever a new container starts: - During new application version deployments -- When applications [scale horizontally](/features/scaling-ha#horizontal-scaling-runtime-services-linux-containers-and-docker) +- When applications [scale horizontally](/features/scaling#horizontal-scaling-runtime-services-linux-containers-and-docker) - When runtime containers fail and new containers start automatically ### First deploy -For initial deployments, Zerops starts one or more runtime containers based on your service [auto scaling settings](/features/scaling-ha). +For initial deployments, Zerops starts one or more runtime containers based on your service [auto scaling settings](/features/scaling). Zerops executes these steps for each new container: diff --git a/apps/docs/content/features/scaling-ha.mdx b/apps/docs/content/features/scaling.mdx similarity index 100% rename from apps/docs/content/features/scaling-ha.mdx rename to apps/docs/content/features/scaling.mdx diff --git a/apps/docs/content/gleam/how-to/create.mdx b/apps/docs/content/gleam/how-to/create.mdx index 0ad2bd99..4a85027c 100644 --- a/apps/docs/content/gleam/how-to/create.mdx +++ b/apps/docs/content/gleam/how-to/create.mdx @@ -161,7 +161,7 @@ S3_ACCESS_KEY_ID="P8cX1vVVb" S3_ACCESS_SECRET="ogFthuiLYki8XoL73opSCQ" ``` -The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling-ha#single-container-mode)(/features/scaling-ha#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set. +The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode)(/features/scaling#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set. #### Description of description.yaml parameters diff --git a/apps/docs/content/go/how-to/create.mdx b/apps/docs/content/go/how-to/create.mdx index 57709f3b..6cf36a85 100644 --- a/apps/docs/content/go/how-to/create.mdx +++ b/apps/docs/content/go/how-to/create.mdx @@ -161,7 +161,7 @@ S3_ACCESS_KEY_ID="P8cX1vVVb" S3_ACCESS_SECRET="ogFthuiLYki8XoL73opSCQ" ``` -The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling-ha#single-container-mode)(/features/scaling-ha#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set. +The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode)(/features/scaling#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set. #### Description of description.yaml parameters diff --git a/apps/docs/content/homepage.mdx b/apps/docs/content/homepage.mdx index fcf092e6..a26347b2 100644 --- a/apps/docs/content/homepage.mdx +++ b/apps/docs/content/homepage.mdx @@ -168,7 +168,7 @@ Zerops has fully automatic horizontal and vertical scaling with configuration st You won't ever overprovision or underprovision your resources and your services will always have the exact resources they need. There won't be any cutting corners like sharing too few CPU cores between too many services. You will be able to rely on professional, reliable and highly available database setups with auto-repairing abilities that will scale along with your applications. - + ::: diff --git a/apps/docs/content/java/how-to/create.mdx b/apps/docs/content/java/how-to/create.mdx index 300ce97f..7bbace2e 100644 --- a/apps/docs/content/java/how-to/create.mdx +++ b/apps/docs/content/java/how-to/create.mdx @@ -161,7 +161,7 @@ S3_ACCESS_KEY_ID="P8cX1vVVb" S3_ACCESS_SECRET="ogFthuiLYki8XoL73opSCQ" ``` -The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling-ha#single-container-mode)(/features/scaling-ha#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set. +The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode)(/features/scaling#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set. #### Description of description.yaml parameters diff --git a/apps/docs/content/keydb/how-to/create.mdx b/apps/docs/content/keydb/how-to/create.mdx index 6329199f..76edc6cc 100644 --- a/apps/docs/content/keydb/how-to/create.mdx +++ b/apps/docs/content/keydb/how-to/create.mdx @@ -55,7 +55,7 @@ Deployment mode cannot be changed after service creation. :::tip Learn More For detailed scaling configuration, deployment mode details, and troubleshooting, see: - [How Zerops scales KeyDB](/keydb/how-to/scale) - Database-specific scaling guide -- [Automatic Scaling and High Availability](/features/scaling-ha) - Complete technical details +- [Automatic Scaling and High Availability](/features/scaling) - Complete technical details ::: ## Create KeyDB using zCLI diff --git a/apps/docs/content/keydb/how-to/scale.mdx b/apps/docs/content/keydb/how-to/scale.mdx index 5feff01f..3d09e82e 100644 --- a/apps/docs/content/keydb/how-to/scale.mdx +++ b/apps/docs/content/keydb/how-to/scale.mdx @@ -9,7 +9,7 @@ import ResourceTable from '/src/components/ResourceTable'; Zerops automatically scales your KeyDB service based on actual database usage. When your database needs more power, resources increase. When demand drops, resources scale down to reduce costs. :::tip Read More -For complete scaling details across all services, see [Automatic Scaling and High Availability](/features/scaling-ha). +For complete scaling details across all services, see [Automatic Scaling and High Availability](/features/scaling). ::: ## How KeyDB scaling works @@ -77,7 +77,7 @@ Consider increasing these values if your database experiences memory-related iss :::info Read More -For detailed technical parameters and scaling behavior, see [Automatic Scaling and High Availability](/features/scaling-ha#resource-scaling-behavior). +For detailed technical parameters and scaling behavior, see [Automatic Scaling and High Availability](/features/scaling#resource-scaling-behavior). ::: ## Monitor usage @@ -97,7 +97,7 @@ For complete technical specifications including: - Scaling increments and steps - Detailed scaling behavior patterns -See [Resource Scaling Behavior](/features/scaling-ha#resource-scaling-behavior) in the general scaling documentation. +See [Resource Scaling Behavior](/features/scaling#resource-scaling-behavior) in the general scaling documentation. ## Common issues diff --git a/apps/docs/content/mariadb/how-to/create.mdx b/apps/docs/content/mariadb/how-to/create.mdx index aa887af5..234c2e68 100644 --- a/apps/docs/content/mariadb/how-to/create.mdx +++ b/apps/docs/content/mariadb/how-to/create.mdx @@ -64,7 +64,7 @@ Deployment mode cannot be changed after service creation. :::tip Learn More For detailed scaling configuration, deployment mode details, and troubleshooting, see: - [How Zerops scales MariaDB](/mariadb/how-to/scale) - Database-specific scaling guide -- [Automatic Scaling and High Availability](/features/scaling-ha) - Complete technical details +- [Automatic Scaling and High Availability](/features/scaling) - Complete technical details ::: ## Create MariaDB using zCLI diff --git a/apps/docs/content/mariadb/how-to/scale.mdx b/apps/docs/content/mariadb/how-to/scale.mdx index 3e75ad23..fd4d300c 100644 --- a/apps/docs/content/mariadb/how-to/scale.mdx +++ b/apps/docs/content/mariadb/how-to/scale.mdx @@ -9,7 +9,7 @@ import ResourceTable from '/src/components/ResourceTable'; Zerops automatically scales your MariaDB service based on actual database usage. When your database needs more power, resources increase. When demand drops, resources scale down to reduce costs. :::tip Read More -For complete scaling details across all services, see [Automatic Scaling and High Availability](/features/scaling-ha). +For complete scaling details across all services, see [Automatic Scaling and High Availability](/features/scaling). ::: ## How MariaDB scaling works @@ -81,7 +81,7 @@ Consider increasing these values if your database experiences memory-related iss :::info Read More -For detailed technical parameters and scaling behavior, see [Automatic Scaling and High Availability](/features/scaling-ha#resource-scaling-behavior). +For detailed technical parameters and scaling behavior, see [Automatic Scaling and High Availability](/features/scaling#resource-scaling-behavior). ::: ## Monitor usage @@ -101,7 +101,7 @@ For complete technical specifications including: - Scaling increments and steps - Detailed scaling behavior patterns -See [Resource Scaling Behavior](/features/scaling-ha#resource-scaling-behavior) in the general scaling documentation. +See [Resource Scaling Behavior](/features/scaling#resource-scaling-behavior) in the general scaling documentation. ## Common issues diff --git a/apps/docs/content/mariadb/tech-details/cluster.mdx b/apps/docs/content/mariadb/tech-details/cluster.mdx index 36dd25f5..c79d9ebb 100644 --- a/apps/docs/content/mariadb/tech-details/cluster.mdx +++ b/apps/docs/content/mariadb/tech-details/cluster.mdx @@ -3,7 +3,7 @@ title: Asynchronous behaviour of MariaDB cluster description: Learn how you can work with asynchronous behaviour of mariadb cluster in Zerops. --- -The following description applies only to the [highly available mode](/features/scaling-ha#highly-available-ha-mode) of the MariaDB service. +The following description applies only to the [highly available mode](/features/scaling#highly-available-ha-mode) of the MariaDB service. ## Description of MariaDB cluster diff --git a/apps/docs/content/mariadb/tech-details/limitations.mdx b/apps/docs/content/mariadb/tech-details/limitations.mdx index b3633ce9..dbf0aa8b 100644 --- a/apps/docs/content/mariadb/tech-details/limitations.mdx +++ b/apps/docs/content/mariadb/tech-details/limitations.mdx @@ -3,7 +3,7 @@ title: Limitations of MariaDB cluster description: Get to know the limitations of mariadb cluster in Zerops. --- -The following description applies only to the [highly available mode](/features/scaling-ha#highly-available-ha-mode) of the MariaDB service. +The following description applies only to the [highly available mode](/features/scaling#highly-available-ha-mode) of the MariaDB service. #### InnoDB only diff --git a/apps/docs/content/nodejs/how-to/create.mdx b/apps/docs/content/nodejs/how-to/create.mdx index ff531310..8ed5761a 100644 --- a/apps/docs/content/nodejs/how-to/create.mdx +++ b/apps/docs/content/nodejs/how-to/create.mdx @@ -160,7 +160,7 @@ S3_ACCESS_KEY_ID="P8cX1vVVb" S3_ACCESS_SECRET="ogFthuiLYki8XoL73opSCQ" ``` -The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling-ha#single-container-mode)(/features/scaling-ha#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set. +The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode)(/features/scaling#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set. #### Description of description.yaml parameters diff --git a/apps/docs/content/php/how-to/create.mdx b/apps/docs/content/php/how-to/create.mdx index d07f16be..c777e7b3 100644 --- a/apps/docs/content/php/how-to/create.mdx +++ b/apps/docs/content/php/how-to/create.mdx @@ -157,7 +157,7 @@ S3_ACCESS_KEY_ID="P8cX1vVVb" S3_ACCESS_SECRET="ogFthuiLYki8XoL73opSCQ" ``` -The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling-ha#single-container-mode)(/features/scaling-ha#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set. +The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode)(/features/scaling#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set. #### Description of description.yaml parameters diff --git a/apps/docs/content/postgresql/how-to/create.mdx b/apps/docs/content/postgresql/how-to/create.mdx index 9332ab3b..d84970c1 100644 --- a/apps/docs/content/postgresql/how-to/create.mdx +++ b/apps/docs/content/postgresql/how-to/create.mdx @@ -58,7 +58,7 @@ Deployment mode cannot be changed after service creation. :::tip Learn More For detailed scaling configuration, deployment mode details, and troubleshooting, see: - [How Zerops scales PostgreSQL](/postgresql/how-to/scale) - Database-specific scaling guide -- [Automatic Scaling and High Availability](/features/scaling-ha) - Complete technical details +- [Automatic Scaling and High Availability](/features/scaling) - Complete technical details ::: ## Create PostgreSQL using zCLI @@ -139,9 +139,9 @@ services: The YAML file describes your future project infrastructure. The project will contain two PostgreSQL services. -The hostname of the first service will be set to `postgresql1`. The [high availability](/features/scaling-ha#highly-available-ha-mode) mode will be chosen and the custom [auto scaling configuration](/postgresql/how-to/scale) will be set. +The hostname of the first service will be set to `postgresql1`. The [high availability](/features/scaling#highly-available-ha-mode) mode will be chosen and the custom [auto scaling configuration](/postgresql/how-to/scale) will be set. -The hostname of the second service will be set to `postgresql2`. The [single container](/features/scaling-ha#single-container-mode) mode will be chosen and the default [auto scaling configuration](/postgresql/how-to/scale) will be set. +The hostname of the second service will be set to `postgresql2`. The [single container](/features/scaling#single-container-mode) mode will be chosen and the default [auto scaling configuration](/postgresql/how-to/scale) will be set. #### Description of description.yaml parameters @@ -349,7 +349,7 @@ services: mode: NON_HA ``` -The YAML file describes the list of one or more services that you want to add to your existing project. In the example above, one PostgreSQL service in the [single container](/features/scaling-ha#single-container-mode) with default [auto scaling](/postgresql/how-to/scale) configuration will be added to your project. The hostname of the new service will be set to `postgresql1`. +The YAML file describes the list of one or more services that you want to add to your existing project. In the example above, one PostgreSQL service in the [single container](/features/scaling#single-container-mode) with default [auto scaling](/postgresql/how-to/scale) configuration will be added to your project. The hostname of the new service will be set to `postgresql1`. The content of the `services:` section of `import.yaml` is identical to the [project description file](#create-a-project-description-file). The `import.yaml` never contains the `project:` section because the project already exists. diff --git a/apps/docs/content/postgresql/how-to/scale.mdx b/apps/docs/content/postgresql/how-to/scale.mdx index 0162de7c..468f2e2b 100644 --- a/apps/docs/content/postgresql/how-to/scale.mdx +++ b/apps/docs/content/postgresql/how-to/scale.mdx @@ -9,7 +9,7 @@ import ResourceTable from '/src/components/ResourceTable'; Zerops automatically scales your PostgreSQL service based on actual database usage. When your database needs more power, resources increase. When demand drops, resources scale down to reduce costs. :::tip Read More -For complete scaling details across all services, see [Automatic Scaling and High Availability](/features/scaling-ha). +For complete scaling details across all services, see [Automatic Scaling and High Availability](/features/scaling). ::: ## How PostgreSQL scaling works @@ -85,7 +85,7 @@ Consider increasing these values if your database experiences memory-related iss :::info Read More -For detailed technical parameters and scaling behavior, see [Automatic Scaling and High Availability](/features/scaling-ha#resource-scaling-behavior). +For detailed technical parameters and scaling behavior, see [Automatic Scaling and High Availability](/features/scaling#resource-scaling-behavior). ::: ## Monitor usage @@ -105,7 +105,7 @@ For complete technical specifications including: - Scaling increments and steps - Detailed scaling behavior patterns -See [Resource Scaling Behavior](/features/scaling-ha#resource-scaling-behavior) in the general scaling documentation. +See [Resource Scaling Behavior](/features/scaling#resource-scaling-behavior) in the general scaling documentation. ## Common issues diff --git a/apps/docs/content/python/how-to/create.mdx b/apps/docs/content/python/how-to/create.mdx index f7c7dfde..1dead262 100644 --- a/apps/docs/content/python/how-to/create.mdx +++ b/apps/docs/content/python/how-to/create.mdx @@ -161,7 +161,7 @@ S3_ACCESS_KEY_ID="P8cX1vVVb" S3_ACCESS_SECRET="ogFthuiLYki8XoL73opSCQ" ``` -The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling-ha#single-container-mode)(/features/scaling-ha#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set. +The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode)(/features/scaling#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set. #### Description of description.yaml parameters diff --git a/apps/docs/content/references/networking/ssh.mdx b/apps/docs/content/references/networking/ssh.mdx index 6e8bf752..7b264bbc 100644 --- a/apps/docs/content/references/networking/ssh.mdx +++ b/apps/docs/content/references/networking/ssh.mdx @@ -14,7 +14,7 @@ Database services, message brokers, and object storage are **not accessible** vi :::warning Non-Persistent Changes SSH connections should not be used for making persistent changes to your service: -- In [HA mode](/features/scaling-ha#horizontal-scaling-runtime-services-linux-containers-and-docker), changes via SSH affect only the current container +- In [HA mode](/features/scaling#horizontal-scaling-runtime-services-linux-containers-and-docker), changes via SSH affect only the current container - Container replacements or scaling events will deploy the original application version - For persistent changes across all containers, use: - [`run.prepareCommands`](/zerops-yaml/specification#preparecommands--1) @@ -82,7 +82,7 @@ ssh node-id-1.runtime.app.zerops ``` :::note -When using [HA mode](/features/scaling-ha#horizontal-scaling-runtime-services-linux-containers-and-docker), connecting to the service hostname will route you to a random container within that service. +When using [HA mode](/features/scaling#horizontal-scaling-runtime-services-linux-containers-and-docker), connecting to the service hostname will route you to a random container within that service. ::: #### Container Naming Conventions @@ -92,7 +92,7 @@ Each container in your project has a unique hostname following these patterns: - Format 1: `node-id-.runtime.app.zerops` - Format 2: `node.runtime.app.zerops` -When your application [scales horizontally](/features/scaling-ha#horizontal-scaling-runtime-services-linux-containers-and-docker): +When your application [scales horizontally](/features/scaling#horizontal-scaling-runtime-services-linux-containers-and-docker): - New containers receive incremental hostnames - Decommissioned container hostnames are not recycled - You might see non-sequential container numbers (e.g., `node-id-5` and `node-id-12`) diff --git a/apps/docs/content/rust/how-to/create.mdx b/apps/docs/content/rust/how-to/create.mdx index c260348c..30aac3e7 100644 --- a/apps/docs/content/rust/how-to/create.mdx +++ b/apps/docs/content/rust/how-to/create.mdx @@ -161,7 +161,7 @@ S3_ACCESS_KEY_ID="P8cX1vVVb" S3_ACCESS_SECRET="ogFthuiLYki8XoL73opSCQ" ``` -The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling-ha#single-container-mode)(/features/scaling-ha#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set. +The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode)(/features/scaling#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set. #### Description of description.yaml parameters diff --git a/apps/docs/content/ubuntu/how-to/create.mdx b/apps/docs/content/ubuntu/how-to/create.mdx index 7eba7ca9..a4890e45 100644 --- a/apps/docs/content/ubuntu/how-to/create.mdx +++ b/apps/docs/content/ubuntu/how-to/create.mdx @@ -161,7 +161,7 @@ S3_ACCESS_KEY_ID="P8cX1vVVb" S3_ACCESS_SECRET="ogFthuiLYki8XoL73opSCQ" ``` -The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling-ha#single-container-mode)(/features/scaling-ha#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set. +The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode)(/features/scaling#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set. #### Description of description.yaml parameters diff --git a/apps/docs/sidebars.js b/apps/docs/sidebars.js index 84be27f6..39e72713 100644 --- a/apps/docs/sidebars.js +++ b/apps/docs/sidebars.js @@ -88,7 +88,7 @@ module.exports = { }, { type: 'doc', - id: 'features/scaling-ha', + id: 'features/scaling', label: 'Automatic Scaling & High Availability', customProps: { sidebar_icon: 'adjustments', diff --git a/apps/docs/src/components/content/create-scaling.mdx b/apps/docs/src/components/content/create-scaling.mdx index 8a764f35..fa4a2e73 100644 --- a/apps/docs/src/components/content/create-scaling.mdx +++ b/apps/docs/src/components/content/create-scaling.mdx @@ -36,6 +36,6 @@ These settings can significantly improve application performance and reliability :::tip Learn More For detailed scaling configuration, troubleshooting, and best practices, see: - How Zerops scales - Service-specific scaling guide -- [Automatic Scaling and High Availability](/features/scaling-ha) - Complete technical details +- [Automatic Scaling and High Availability](/features/scaling) - Complete technical details - [Zerops Pricing](https://zerops.io/#pricing) - Cost differences between CPU modes and resource usage rates ::: \ No newline at end of file diff --git a/apps/docs/src/components/content/scaling.mdx b/apps/docs/src/components/content/scaling.mdx index ec375c31..9bf55348 100644 --- a/apps/docs/src/components/content/scaling.mdx +++ b/apps/docs/src/components/content/scaling.mdx @@ -6,7 +6,7 @@ import { Var, VarLink } from '/src/components/content/var'; Zerops automatically scales your service based on actual usage. When your application needs more power, resources increase. When demand drops, resources scale down to reduce costs. :::tip Read More -For complete scaling details across all services, see [Automatic Scaling and High Availability](/features/scaling-ha). +For complete scaling details across all services, see [Automatic Scaling and High Availability](/features/scaling). ::: ## How it works @@ -16,7 +16,7 @@ For complete scaling details across all services, see [Automatic Scaling and Hig **Horizontal scaling** creates entirely new containers when vertical scaling reaches its configured limits. :::info Read More -Learn more about [vertical](/features/scaling-ha#part-1-resource-management) and [horizontal scaling](/features/scaling-ha#part-2-container-architecture--service-specific-approaches) and [complete technical details](/features/scaling-ha#resource-scaling-behavior) in our scaling guide. +Learn more about [vertical](/features/scaling#part-1-resource-management) and [horizontal scaling](/features/scaling#part-2-container-architecture--service-specific-approaches) and [complete technical details](/features/scaling#resource-scaling-behavior) in our scaling guide. ::: ## Configure scaling @@ -40,7 +40,7 @@ You can configure scaling settings at different stages: ### CPU Settings -**CPU mode**: Choose between shared (cost-effective, variable performance) or dedicated (consistent performance, higher cost). You can change CPU mode once per hour. See [pricing](https://zerops.io/#pricing) for costs or read more about [CPU mode](/features/scaling-ha#cpu-mode). +**CPU mode**: Choose between shared (cost-effective, variable performance) or dedicated (consistent performance, higher cost). You can change CPU mode once per hour. See [pricing](https://zerops.io/#pricing) for costs or read more about [CPU mode](/features/scaling#cpu-mode). **Minimum and Maximum CPU**: Configure the boundaries for CPU core allocation. Zerops will scale CPU resources within these limits based on actual usage. @@ -69,7 +69,7 @@ Set minimum = maximum to disable automatic CPU scaling. - **Dynamic free total %**: Triggers scaling when total free CPU across all cores drops below this percentage :::info Read More -More details on [CPU Settings](/features/scaling-ha#cpu-settings). +More details on [CPU Settings](/features/scaling#cpu-settings). ::: ### RAM Settings @@ -100,7 +100,7 @@ Set minimum = maximum to disable automatic RAM scaling. Consider increasing these values if your application experiences memory-related crashes. :::info Read More -More details on [RAM Settings](/features/scaling-ha#ram-settings). +More details on [RAM Settings](/features/scaling#ram-settings). :::