You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: apps/docs/content/company/pricing.mdx
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,6 +73,10 @@ Services in Zerops require computing resources that are billed separately from y
73
73
</tbody>
74
74
</table>
75
75
76
+
:::note Daily Spending Control
77
+
You can set daily spending limits in GUI for your project to control costs and avoid unexpected charges. This provides an alternative to configuring automatic resource scaling ranges while keeping your services running optimally.
78
+
:::
79
+
76
80
## Additional Services
77
81
78
82
Enhance your deployment with these optional services to meet specific requirements for networking, storage, and data transfer.
Copy file name to clipboardExpand all lines: apps/docs/content/features/env-variables.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ You can define service-level variables in two ways:
17
17
18
18
#### 1. Build & Runtime Variables
19
19
20
-
These variables are defined with `envVariables` attribute in the `build` or `run` section of your [zerops.yaml](/zerops-yaml/specification) file and are accessible within their respective containers.
20
+
These variables are defined with `envVariables` attribute in the [build](/zerops-yaml/specification#envvariables-) or [run](/zerops-yaml/specification#envvariables--1) section of your `zerops.yaml` file and are accessible within their respective containers.
Copy file name to clipboardExpand all lines: apps/docs/content/references/networking/public-access.mdx
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,8 +52,6 @@ Zerops subdomains provide quick public access through `.zerops.app` addresses, i
52
52
53
53
Once enabled, Zerops assigns a unique subdomain for your application. If you've defined multiple [internal ports](/zerops-yaml/specification#ports-) with HTTP support in your `zerops.yaml`, each port receives its own unique `.zerops.app` subdomain.
54
54
55
-
<GroupCardsheading="Configure internal ports for your Runtime"items={languages} />
Copy file name to clipboardExpand all lines: apps/docs/static/llms-full.txt
+12-11Lines changed: 12 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -1309,6 +1309,9 @@ Services in Zerops require computing resources that are billed separately from y
1309
1309
$0.05 per 0.5 GB / 30 days
1310
1310
Storage space for your applications and data
1311
1311
1312
+
:::note Daily Spending Control
1313
+
You can set daily spending limits in GUI for your project to control costs and avoid unexpected charges. This provides an alternative to configuring automatic resource scaling ranges while keeping your services running optimally.
1314
+
:::
1312
1315
## Additional Services
1313
1316
Enhance your deployment with these optional services to meet specific requirements for networking, storage, and data transfer.
You can configure Elasticsearch plugins using a comma-separated list in your environment secrets:
@@ -5637,7 +5644,7 @@ Variables that are specific to individual [services](/features/infrastructure#se
5637
5644
### User-Defined Variables
5638
5645
You can define service-level variables in two ways:
5639
5646
#### 1. Build & Runtime Variables
5640
-
These variables are defined with `envVariables` attribute in the `build` or `run` section of your [zerops.yaml](/zerops-yaml/specification) file and are accessible within their respective containers.
5647
+
These variables are defined with `envVariables` attribute in the [build](/zerops-yaml/specification#envvariables-) or [run](/zerops-yaml/specification#envvariables--1) section of your `zerops.yaml` file and are accessible within their respective containers.
5641
5648
```yaml title="zerops.yaml"
5642
5649
...
5643
5650
build:
@@ -18583,6 +18590,7 @@ curl -L https://zerops.io/zcli/install.sh | sh
18583
18590
```
18584
18591
zCLI will be installed inside `/usr/bin` or `/usr/local/bin`.
18585
18592
### Windows
18593
+
Execute following command in PowerShell:
18586
18594
```powershell
18587
18595
irm https://zerops.io/zcli/install.ps1 | iex
18588
18596
```
@@ -21556,43 +21564,36 @@ Configure how the balancer communicates with backend services:
21556
21564
Parameter
21557
21565
Default
21558
21566
Range
21559
-
Description
21560
21567
21561
21568
Enable buffering of client request body
21562
21569
proxy_request_buffering
21563
21570
off
21564
21571
on/off
21565
-
Buffer client request bodies before forwarding
21566
21572
21567
21573
Enable buffering of responses from proxied server
21568
21574
proxy_buffering
21569
21575
on
21570
21576
on/off
21571
-
Buffer responses from backend services
21572
21577
21573
21578
Size of the buffer used for reading the first part of the response
21574
21579
proxy_buffer_size
21575
21580
32k
21576
21581
1k-256k
21577
-
Buffer size for first part of backend response
21578
21582
21579
21583
Number of buffers used for reading a response from the proxied server
21580
21584
proxy_buffers_number
21581
21585
4
21582
21586
1-16
21583
-
Number of buffers for reading backend responses
21584
21587
21585
21588
Size of buffers for reading a response from the proxied server
21586
21589
proxy_buffers_size
21587
21590
256k
21588
21591
1k-1m
21589
-
Size of buffers for reading backend responses
21590
21592
21591
21593
Size of buffers that can be busy sending response to the client
21592
21594
proxy_busy_buffers_size
21593
21595
256k
21594
21596
1k-1m
21595
-
Size of buffers for sending response to client
21596
21597
21597
21598
:::tip Recommendations
21598
21599
- **Real-time APIs**: Set `proxy_buffering` to off for lower latency
You can configure Elasticsearch plugins using a comma-separated list in your environment secrets:
@@ -5445,7 +5449,7 @@ Variables that are specific to individual [services](/features/infrastructure#se
5445
5449
### User-Defined Variables
5446
5450
You can define service-level variables in two ways:
5447
5451
#### 1. Build & Runtime Variables
5448
-
These variables are defined with `envVariables` attribute in the `build` or `run` section of your [zerops.yaml](/zerops-yaml/specification) file and are accessible within their respective containers.
5452
+
These variables are defined with `envVariables` attribute in the [build](/zerops-yaml/specification#envvariables-) or [run](/zerops-yaml/specification#envvariables--1) section of your `zerops.yaml` file and are accessible within their respective containers.
0 commit comments