Skip to content

Commit c419ded

Browse files
nermalcat69nermalcat69
committed
Merge branch 'main' into refine-llm-script
2 parents 2e92eb3 + 6dcf52a commit c419ded

File tree

4 files changed

+76
-22
lines changed

4 files changed

+76
-22
lines changed

‎apps/docs/content/nats/overview.mdx

Lines changed: 35 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -27,28 +27,54 @@ Our NATS implementation features optimized default settings designed for common
2727
- Secure authentication with automatically generated credentials
2828
- Optimized settings for performance and reliability
2929

30+
You can fine-tune your NATS service by adjusting **environment variables**:
31+
32+
### Available Configuration Options
33+
34+
:::note
35+
If certain variables are not visible in your configuration, they may have been introduced after your service was created. Simply add them as [secret variables](/features/env-variables#2-secret-variables) to access the functionality.
36+
:::
37+
38+
<table className="w-full my-1.5">
39+
<thead>
40+
<tr>
41+
<th className="w-fit">Variable</th>
42+
<th className="w-fit">Description</th>
43+
</tr>
44+
</thead>
45+
<tbody>
46+
<tr>
47+
<td className="w-fit whitespace-nowrap"><code>MAX_PAYLOAD</code></td>
48+
<td className="w-fit">Defines the maximum allowed message size for all NATS traffic. Default: <code>8MB</code>, Maximum: <code>64MB</code>. See <a href="https://docs.nats.io/running-a-nats-service/configuration#limits">NATS limits documentation</a> for details.</td>
49+
</tr>
50+
<tr>
51+
<td className="w-fit whitespace-nowrap"><code>JET_STREAM_ENABLED</code></td>
52+
<td className="w-fit">Controls whether JetStream functionality is enabled. Default: <code>1</code> (enabled), Set to <code>0</code> to disable. See <a href="#jetstream-configuration">JetStream Configuration</a> section below for more details.</td>
53+
</tr>
54+
</tbody>
55+
</table>
56+
57+
:::important
58+
Configuration changes require a service **restart** to take effect. While NATS itself supports configuration hot-reload, this feature will be implemented in a future Zerops update.
59+
:::
60+
61+
After restarting, check your service logs to confirm the changes were applied successfully.
62+
3063
### JetStream Configuration
3164

3265
The service includes [JetStream](https://docs.nats.io/nats-concepts/jetstream) functionality **enabled by default**, providing persistent storage capabilities for your messaging workloads:
3366
- **Memory store**: Up to 40GB for high-performance message caching
3467
- **File store**: Up to 250GB for persistent storage
3568
- **Regular sync intervals**: Ensures data durability and consistency
69+
3670
:::note
3771
In HA deployments, data persistence is further enhanced with 1-minute sync intervals across all nodes, ensuring robust data durability and high availability.
3872
:::
3973

4074
This configuration provides a robust foundation for message persistence while balancing performance and reliability.
4175

42-
#### Disabling JetStream
43-
44-
If you don't need message persistence, you can disable JetStream by setting the `JET_STREAM_ENABLED` environment variable to `0` in your service configuration. This can be done:
45-
46-
- During service creation through the [import configuration](/references/import)
47-
- In the Zerops GUI under service environment variables
48-
- Via the [Zerops API](/references/api) when creating a new service
49-
5076
:::tip
51-
Disabling JetStream may reduce resource usage when persistence isn't required for your application.
77+
Disabling JetStream can reduce resource utilization for applications that don't require message persistence.
5278
:::
5379

5480
### Deployment Modes

‎apps/docs/static/llms-full.txt

Lines changed: 20 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -17381,6 +17381,25 @@ Our NATS implementation features optimized default settings designed for common
1738117381
- HTTP monitoring interface `8222` for management
1738217382
- Secure authentication with automatically generated credentials
1738317383
- Optimized settings for performance and reliability
17384+
You can fine-tune your NATS service by adjusting **environment variables**:
17385+
### Available Configuration Options
17386+
:::note
17387+
If certain variables are not visible in your configuration, they may have been introduced after your service was created. Simply add them as [secret variables](/features/env-variables#2-secret-variables) to access the functionality.
17388+
:::
17389+
17390+
Variable
17391+
Description
17392+
17393+
MAX_PAYLOAD
17394+
Defines the maximum allowed message size for all NATS traffic. Default: 8MB, Maximum: 64MB. See NATS limits documentation for details.
17395+
17396+
JET_STREAM_ENABLED
17397+
Controls whether JetStream functionality is enabled. Default: 1 (enabled), Set to 0 to disable. See JetStream Configuration section below for more details.
17398+
17399+
:::important
17400+
Configuration changes require a service **restart** to take effect. While NATS itself supports configuration hot-reload, this feature will be implemented in a future Zerops update.
17401+
:::
17402+
After restarting, check your service logs to confirm the changes were applied successfully.
1738417403
### JetStream Configuration
1738517404
The service includes [JetStream](https://docs.nats.io/nats-concepts/jetstream) functionality **enabled by default**, providing persistent storage capabilities for your messaging workloads:
1738617405
- **Memory store**: Up to 40GB for high-performance message caching
@@ -17390,13 +17409,8 @@ The service includes [JetStream](https://docs.nats.io/nats-concepts/jetstream) f
1739017409
In HA deployments, data persistence is further enhanced with 1-minute sync intervals across all nodes, ensuring robust data durability and high availability.
1739117410
:::
1739217411
This configuration provides a robust foundation for message persistence while balancing performance and reliability.
17393-
#### Disabling JetStream
17394-
If you don't need message persistence, you can disable JetStream by setting the `JET_STREAM_ENABLED` environment variable to `0` in your service configuration. This can be done:
17395-
- During service creation through the [import configuration](/references/import)
17396-
- In the Zerops GUI under service environment variables
17397-
- Via the [Zerops API](/references/api) when creating a new service
1739817412
:::tip
17399-
Disabling JetStream may reduce resource usage when persistence isn't required for your application.
17413+
Disabling JetStream can reduce resource utilization for applications that don't require message persistence.
1740017414
:::
1740117415
### Deployment Modes
1740217416
:::warning

‎apps/docs/static/llms-small.txt

Lines changed: 20 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -17154,6 +17154,25 @@ Our NATS implementation features optimized default settings designed for common
1715417154
- HTTP monitoring interface `8222` for management
1715517155
- Secure authentication with automatically generated credentials
1715617156
- Optimized settings for performance and reliability
17157+
You can fine-tune your NATS service by adjusting **environment variables**:
17158+
### Available Configuration Options
17159+
:::note
17160+
If certain variables are not visible in your configuration, they may have been introduced after your service was created. Simply add them as [secret variables](/features/env-variables#2-secret-variables) to access the functionality.
17161+
:::
17162+
17163+
Variable
17164+
Description
17165+
17166+
MAX_PAYLOAD
17167+
Defines the maximum allowed message size for all NATS traffic. Default: 8MB, Maximum: 64MB. See NATS limits documentation for details.
17168+
17169+
JET_STREAM_ENABLED
17170+
Controls whether JetStream functionality is enabled. Default: 1 (enabled), Set to 0 to disable. See JetStream Configuration section below for more details.
17171+
17172+
:::important
17173+
Configuration changes require a service **restart** to take effect. While NATS itself supports configuration hot-reload, this feature will be implemented in a future Zerops update.
17174+
:::
17175+
After restarting, check your service logs to confirm the changes were applied successfully.
1715717176
### JetStream Configuration
1715817177
The service includes [JetStream](https://docs.nats.io/nats-concepts/jetstream) functionality **enabled by default**, providing persistent storage capabilities for your messaging workloads:
1715917178
- **Memory store**: Up to 40GB for high-performance message caching
@@ -17163,13 +17182,8 @@ The service includes [JetStream](https://docs.nats.io/nats-concepts/jetstream) f
1716317182
In HA deployments, data persistence is further enhanced with 1-minute sync intervals across all nodes, ensuring robust data durability and high availability.
1716417183
:::
1716517184
This configuration provides a robust foundation for message persistence while balancing performance and reliability.
17166-
#### Disabling JetStream
17167-
If you don't need message persistence, you can disable JetStream by setting the `JET_STREAM_ENABLED` environment variable to `0` in your service configuration. This can be done:
17168-
- During service creation through the [import configuration](/references/import)
17169-
- In the Zerops GUI under service environment variables
17170-
- Via the [Zerops API](/references/api) when creating a new service
1717117185
:::tip
17172-
Disabling JetStream may reduce resource usage when persistence isn't required for your application.
17186+
Disabling JetStream can reduce resource utilization for applications that don't require message persistence.
1717317187
:::
1717417188
### Deployment Modes
1717517189
:::warning

‎zerops-llm-script.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -175,4 +175,4 @@ async function generateLLMDocs() {
175175
console.log(`< Output '${outputTinyFile}' `)
176176
}
177177

178-
generateLLMDocs().catch(console.error)
178+
generateLLMDocs().catch(console.error)

0 commit comments

Comments
 (0)