resources update (#200)

zeropsio · Feb 21, 2025 · 97f554d · 97f554d
1 parent 96a800c
commit 97f554d
Show file tree

Hide file tree

Showing 33 changed files with 149 additions and 558 deletions.
diff --git a/apps/docs/content/bun/how-to/create.mdx b/apps/docs/content/bun/how-to/create.mdx
@@ -7,6 +7,7 @@ import Image from '/src/components/Image';
 import data from '@site/static/data.json';
 import UnorderedList from '@site/src/components/UnorderedList';
 import Video from '/src/components/Video';
+import ResourceTable from '/src/components/ResourceTable';
 
 Zerops provides a powerful Bun runtime service with extensive build support. The Bun runtime is highly scalable and customizable to suit your development and production needs. With just a few clicks or commands, you can have a production-ready Bun environment up and running in no time.
 
@@ -86,11 +87,7 @@ You can choose the CPU mode when starting a new service or change it later. The
 
 Vertical auto scaling has the following default configuration:
 
-| &nbsp;        | Minimum resource | Maximum resource |
-| ------------- | ---------------- | ---------------- |
-| **CPU cores** | 1                | 5                |
-| **RAM**       | 0.25 GB          | 32 GB            |
-| **Disk**      | 1 GB             | 100 GB           |
+<ResourceTable />
 
 Bun services always start with the minimal resources.
 

diff --git a/apps/docs/content/bun/how-to/scaling.mdx b/apps/docs/content/bun/how-to/scaling.mdx
@@ -4,6 +4,7 @@ description: Get to know how Zerops scales your node.js service.
 ---
 
 import Image from '/src/components/Image';
+import ResourceTable from '/src/components/ResourceTable';
 
 Zerops performs an automated scaling of hardware resources required to run your runtime application based on its usage. If the current use of your application does not require as much performance or disk space the auto scaling reduces the resources and thus reduces the costs. If your application is under heavy load or needs to store more data, then auto scaling increases the resources to make sure it runs smoothly.
 
@@ -66,11 +67,7 @@ The CPU mode doesn't change automatically.
 
 Vertical auto scaling has following default configuration:
 
-| &nbsp;        | Minimum resource | Maximum resource |
-| ------------- | ---------------- | ---------------- |
-| **CPU cores** | 1                | 5                |
-| **RAM**       | 0.25 GB          | 32 GB            |
-| **Disk**      | 1 GB             | 100 GB           |
+<ResourceTable />
 
 Bun service always starts with the minimal resources.
 
@@ -185,7 +182,7 @@ The scale up of RAM or disk is immediate. The scale up of CPU is configured to b
 The **minimum step** for the vertical scaling is
 
 - 1 CPU core
-- 0.25 GB RAM
+- 0.125 GB RAM
 - 0.5 GB disk
 
 When the application is under a heavy load and needs to scale up faster, the scaling step will increase automatically.

diff --git a/apps/docs/content/deno/how-to/create.mdx b/apps/docs/content/deno/how-to/create.mdx
@@ -7,6 +7,7 @@ import Image from '/src/components/Image';
 import data from '@site/static/data.json';
 import UnorderedList from '@site/src/components/UnorderedList';
 import Video from '@site/src/components/Video';
+import ResourceTable from '/src/components/ResourceTable';
 
 Zerops provides a powerful Deno runtime service with extensive build support. The Deno runtime is highly scalable and customizable to suit your development and production needs. With just a few clicks or commands, you can have a production-ready Deno environment up and running in no time.
 
@@ -81,11 +82,7 @@ You can choose the CPU mode when starting a new service or change it later. The
 
 Vertical auto scaling has the following default configuration:
 
-| &nbsp;        | Minimum resource | Maximum resource |
-| ------------- | ---------------- | ---------------- |
-| **CPU cores** | 1                | 5                |
-| **RAM**       | 0.25 GB          | 32 GB            |
-| **Disk**      | 1 GB             | 100 GB           |
+<ResourceTable />
 
 Deno services always start with the minimal resources.
 

diff --git a/apps/docs/content/deno/how-to/scaling.mdx b/apps/docs/content/deno/how-to/scaling.mdx
@@ -4,6 +4,7 @@ description: Get to know how Zerops scales your deno service.
 ---
 
 import Image from '/src/components/Image';
+import ResourceTable from '/src/components/ResourceTable';
 
 Zerops performs an automated scaling of hardware resources required to run your runtime application based on its usage. If the current use of your application does not require as much performance or disk space the auto scaling reduces the resources and thus reduces the costs. If your application is under heavy load or needs to store more data, then auto scaling increases the resources to make sure it runs smoothly.
 
@@ -66,11 +67,7 @@ The CPU mode doesn't change automatically.
 
 Vertical auto scaling has following default configuration:
 
-| &nbsp;        | Minimum resource | Maximum resource |
-| ------------- | ---------------- | ---------------- |
-| **CPU cores** | 1                | 5                |
-| **RAM**       | 0.25 GB          | 32 GB            |
-| **Disk**      | 1 GB             | 100 GB           |
+<ResourceTable />
 
 Deno service always starts with the minimal resources.
 
@@ -185,7 +182,7 @@ The scale up of RAM or disk is immediate. The scale up of CPU is configured to b
 The **minimum step** for the vertical scaling is
 
 - 1 CPU core
-- 0.25 GB RAM
+- 0.125 GB RAM
 - 0.5 GB disk
 
 When the application is under a heavy load and needs to scale up faster, the scaling step will increase automatically.

diff --git a/apps/docs/content/dotnet/how-to/create.mdx b/apps/docs/content/dotnet/how-to/create.mdx
@@ -7,6 +7,7 @@ import Image from '/src/components/Image';
 import data from '@site/static/data.json';
 import UnorderedList from '@site/src/components/UnorderedList';
 import Video from '@site/src/components/Video';
+import ResourceTable from '/src/components/ResourceTable';
 
 Zerops provides a .NET runtime service with extensive build support. .NET runtime is highly scalable and customisable to suit both development and production.
 
@@ -81,32 +82,7 @@ Choose the CPU mode when starting a new service or change it later. The CPU mode
 
 Vertical auto scaling has following default configuration:
 
-<table className="w-full my-1.5">
-   <thead>
-     <tr>
-       <th className="w-fit"><strong>Resources Type</strong></th>
-       <th className="w-fit"><strong>Minimum resource</strong></th>
-       <th className="w-fit"><strong>Maximum resource</strong></th>
-     </tr>
-   </thead>
-   <tbody>
-     <tr>
-       <td className="w-fit"><strong>CPU cores</strong></td>
-       <td className="w-fit">1</td>
-       <td className="w-fit">5</td>
-     </tr>
-     <tr>
-       <td className="w-fit"><strong>RAM</strong></td>
-       <td className="w-fit">0.25 GB</td>
-       <td className="w-fit">32 GB</td>
-     </tr>
-     <tr>
-       <td className="w-fit"><strong>Disk</strong></td>
-       <td className="w-fit">1 GB</td>
-       <td className="w-fit">100 GB</td>
-     </tr>
-   </tbody>
- </table>
+<ResourceTable />
 
 .NET service always starts with the minimal resources.
 

diff --git a/apps/docs/content/dotnet/how-to/scaling.mdx b/apps/docs/content/dotnet/how-to/scaling.mdx
@@ -4,7 +4,7 @@ description: Get to know how Zerops scales your dotnet service.
 ---
 
 import Image from '/src/components/Image';
-
+import ResourceTable from '/src/components/ResourceTable';
 
 Zerops performs an automated scaling of hardware resources required to run your runtime application based on its usage. If the current use of your application does not require as much performance or disk space the auto scaling reduces the resources and thus reduces the costs. If your application is under heavy load or needs to store more data, then auto scaling increases the resources to make sure it runs smoothly.
 
@@ -68,32 +68,7 @@ The CPU mode doesn't change automatically.
 
 Vertical auto scaling has following default configuration:
 
-<table className="w-full my-1.5">
-   <thead>
-     <tr>
-       <th className="w-fit"><strong>Resources Type</strong></th>
-       <th className="w-fit"><strong>Minimum resource</strong></th>
-       <th className="w-fit"><strong>Maximum resource</strong></th>
-     </tr>
-   </thead>
-   <tbody>
-     <tr>
-       <td className="w-fit"><strong>CPU cores</strong></td>
-       <td className="w-fit">1</td>
-       <td className="w-fit">5</td>
-     </tr>
-     <tr>
-       <td className="w-fit"><strong>RAM</strong></td>
-       <td className="w-fit">0.25 GB</td>
-       <td className="w-fit">32 GB</td>
-     </tr>
-     <tr>
-       <td className="w-fit"><strong>Disk</strong></td>
-       <td className="w-fit">1 GB</td>
-       <td className="w-fit">100 GB</td>
-     </tr>
-   </tbody>
- </table>
+<ResourceTable />
 
 .NET service always starts with the minimal resources.
 
@@ -208,7 +183,7 @@ The scale up of RAM or disk is immediate. The scale up of CPU is configured to b
 The **minimum step** for the vertical scaling is
 
 - 1 CPU core
-- 0.25 GB RAM
+- 0.125 GB RAM
 - 0.5 GB disk
 
 When the application is under a heavy load and needs to scale up faster, the scaling step will increase automatically.

diff --git a/apps/docs/content/elixir/how-to/create.mdx b/apps/docs/content/elixir/how-to/create.mdx
@@ -7,6 +7,7 @@ import Image from '/src/components/Image';
 import data from '@site/static/data.json';
 import UnorderedList from '@site/src/components/UnorderedList';
 import Video from '@site/src/components/Video';
+import ResourceTable from '/src/components/ResourceTable';
 
 Zerops provides a powerful Elixir runtime service with extensive build support. The Elixir runtime is highly scalable and customizable to suit your development and production needs. With just a few clicks or commands, you can have a production-ready Elixir environment up and running in no time.
 
@@ -81,11 +82,7 @@ You can choose the CPU mode when starting a new service or change it later. The
 
 Vertical auto scaling has the following default configuration:
 
-| &nbsp;        | Minimum resource | Maximum resource |
-| ------------- | ---------------- | ---------------- |
-| **CPU cores** | 1                | 5                |
-| **RAM**       | 0.25 GB          | 32 GB            |
-| **Disk**      | 1 GB             | 100 GB           |
+<ResourceTable />
 
 Elixir services always start with the minimal resources.
 

diff --git a/apps/docs/content/elixir/how-to/scaling.mdx b/apps/docs/content/elixir/how-to/scaling.mdx
@@ -4,6 +4,7 @@ description: Get to know how Zerops scales your Elixir service.
 ---
 
 import Image from '/src/components/Image';
+import ResourceTable from '/src/components/ResourceTable';
 
 Zerops performs an automated scaling of hardware resources required to run your runtime application based on its usage. If the current use of your application does not require as much performance or disk space the auto scaling reduces the resources and thus reduces the costs. If your application is under heavy load or needs to store more data, then auto scaling increases the resources to make sure it runs smoothly.
 
@@ -66,11 +67,7 @@ The CPU mode doesn't change automatically.
 
 Vertical auto scaling has following default configuration:
 
-| &nbsp;        | Minimum resource | Maximum resource |
-| ------------- | ---------------- | ---------------- |
-| **CPU cores** | 1                | 5                |
-| **RAM**       | 0.25 GB          | 32 GB            |
-| **Disk**      | 1 GB             | 100 GB           |
+<ResourceTable />
 
 Elixir service always starts with the minimal resources.
 
@@ -185,7 +182,7 @@ The scale up of RAM or disk is immediate. The scale up of CPU is configured to b
 The **minimum step** for the vertical scaling is
 
 - 1 CPU core
-- 0.25 GB RAM
+- 0.125 GB RAM
 - 0.5 GB disk
 
 When the application is under a heavy load and needs to scale up faster, the scaling step will increase automatically.

diff --git a/apps/docs/content/frameworks/laravel.mdx b/apps/docs/content/frameworks/laravel.mdx
@@ -14,7 +14,7 @@ import IconTwill from '@theme/Icon/Twill';
 Zerops implements what we call "transparent infrastructure" - you get enterprise-grade capabilities with development-friendly ergonomics. This means:
 
 - **Full system access** across all environments
-- **Granular resource control** starting at 0.25GB RAM
+- **Granular resource control** starting at 0.125GB RAM
 - **True environment parity** from local to production
 - **Zero-downtime deployments** by default
 

diff --git a/apps/docs/content/gleam/how-to/create.mdx b/apps/docs/content/gleam/how-to/create.mdx
@@ -7,6 +7,7 @@ import Image from '/src/components/Image';
 import data from '@site/static/data.json';
 import UnorderedList from '@site/src/components/UnorderedList';
 import Video from '@site/src/components/Video';
+import ResourceTable from '/src/components/ResourceTable';
 
 Zerops provides a powerful Gleam runtime service with extensive build support. The Gleam runtime is highly scalable and customizable to suit your development and production needs. With just a few clicks or commands, you can have a production-ready Gleam environment up and running in no time.
 
@@ -82,11 +83,7 @@ You can choose the CPU mode when starting a new service or change it later. The
 
 Vertical auto scaling has the following default configuration:
 
-| &nbsp;        | Minimum resource | Maximum resource |
-| ------------- | ---------------- | ---------------- |
-| **CPU cores** | 1                | 5                |
-| **RAM**       | 0.25 GB          | 32 GB            |
-| **Disk**      | 1 GB             | 100 GB           |
+<ResourceTable />
 
 Gleam services always start with the minimal resources.
 

diff --git a/apps/docs/content/gleam/how-to/scaling.mdx b/apps/docs/content/gleam/how-to/scaling.mdx
@@ -4,6 +4,7 @@ description: Get to know how Zerops scales your Gleam service.
 ---
 
 import Image from '/src/components/Image';
+import ResourceTable from '/src/components/ResourceTable';
 
 Zerops performs an automated scaling of hardware resources required to run your runtime application based on its usage. If the current use of your application does not require as much performance or disk space the auto scaling reduces the resources and thus reduces the costs. If your application is under heavy load or needs to store more data, then auto scaling increases the resources to make sure it runs smoothly.
 
@@ -66,11 +67,7 @@ The CPU mode doesn't change automatically.
 
 Vertical auto scaling has following default configuration:
 
-| &nbsp;        | Minimum resource | Maximum resource |
-| ------------- | ---------------- | ---------------- |
-| **CPU cores** | 1                | 5                |
-| **RAM**       | 0.25 GB          | 32 GB            |
-| **Disk**      | 1 GB             | 100 GB           |
+<ResourceTable />
 
 Gleam service always starts with the minimal resources.
 
@@ -185,7 +182,7 @@ The scale up of RAM or disk is immediate. The scale up of CPU is configured to b
 The **minimum step** for the vertical scaling is
 
 - 1 CPU core
-- 0.25 GB RAM
+- 0.125 GB RAM
 - 0.5 GB disk
 
 When the application is under a heavy load and needs to scale up faster, the scaling step will increase automatically.

diff --git a/apps/docs/content/go/how-to/create.mdx b/apps/docs/content/go/how-to/create.mdx
@@ -7,6 +7,7 @@ import Image from '/src/components/Image';
 import data from '@site/static/data.json';
 import UnorderedList from '@site/src/components/UnorderedList';
 import Video from '@site/src/components/Video';
+import ResourceTable from '/src/components/ResourceTable';
 
 Zerops provides a Go runtime service with extensive build support. Go runtime is highly scalable and customisable to suit both development and production.
 
@@ -81,32 +82,7 @@ Choose the CPU mode when starting a new service or change it later. The CPU mode
 
 Vertical auto scaling has following default configuration:
 
-<table className="w-full my-1.5">
-   <thead>
-     <tr>
-       <th className="w-fit"><strong>Resources Type</strong></th>
-       <th className="w-fit"><strong>Minimum resource</strong></th>
-       <th className="w-fit"><strong>Maximum resource</strong></th>
-     </tr>
-   </thead>
-   <tbody>
-     <tr>
-       <td className="w-fit"><strong>CPU cores</strong></td>
-       <td className="w-fit">1</td>
-       <td className="w-fit">5</td>
-     </tr>
-     <tr>
-       <td className="w-fit"><strong>RAM</strong></td>
-       <td className="w-fit">0.25 GB</td>
-       <td className="w-fit">32 GB</td>
-     </tr>
-     <tr>
-       <td className="w-fit"><strong>Disk</strong></td>
-       <td className="w-fit">1 GB</td>
-       <td className="w-fit">100 GB</td>
-     </tr>
-   </tbody>
- </table>
+<ResourceTable />
 
 
 Go service always starts with the minimal resources.