eliott/Olares
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

rebrand docs content for beOS Pro

Browse Source
This commit is contained in:
Eliott van Nuffel
2026-03-09 10:19:35 +01:00
parent 150f4a8ef4
commit d4e933688d
616 changed files with 6294 additions and 6294 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/developer/develop/app-env-index.md
View File

@@ -1,11 +1,11 @@
---
outline: [2, 3]
description: Learn how variables are injected during Olares app deployment, including declarative environment variables (.Values.olaresEnv) and system-injected runtime Helm values (.Values.*).
description: Learn how variables are injected during beOS Pro app deployment, including declarative environment variables (.Values.olaresEnv) and system-injected runtime Helm values (.Values.*).
---
# Environment variables overview
Olares apps use app-service to inject runtime context and configuration into the app's `values.yaml`. In Helm templates, you can reference these values via `.Values.*`.
beOS Pro apps use app-service to inject runtime context and configuration into the app's `values.yaml`. In Helm templates, you can reference these values via `.Values.*`.
:::info Variables and Helm values
In this document, "variables" mainly refer to Helm values. They are not automatically passed into container environment variables. If you need them inside containers, explicitly map them to `env:` in your templates.
@@ -13,11 +13,11 @@ In this document, "variables" mainly refer to Helm values. They are not automati
## How variables are injected
Olares injects variables through two channels:
beOS Pro injects variables through two channels:
- **Declarative environment variables**: The developer declares variables under `envs` in `OlaresManifest.yaml`. At deployment, app-service resolves and injects the values into `.Values.olaresEnv` in `values.yaml`.
- **Declarative environment variables**: The developer declares variables under `envs` in `beOS ProManifest.yaml`. At deployment, app-service resolves and injects the values into `.Values.olaresEnv` in `values.yaml`.
- **System-injected runtime variables**: Injected automatically by Olares at deployment time. No declaration is required, though some values are only available after you declare the relevant dependency, such as middleware.
- **System-injected runtime variables**: Injected automatically by beOS Pro at deployment time. No declaration is required, though some values are only available after you declare the relevant dependency, such as middleware.
## Next steps