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

20
docs/developer/develop/tutorial/develop.md
View File

@@ -3,19 +3,19 @@ outline: [2, 3]
description: Learn how to use Studio to set up a dev container, access it via VS Code, and configure port forwarding.
---
# Develop in a dev container
Olares Studio allows you to spin up a pre-configured dev container to write and debug code (such as Node.js scripts or CUDA programs) without managing local infrastructure. This provides an isolated environment identical to the production runtime.
beOS Pro Studio allows you to spin up a pre-configured dev container to write and debug code (such as Node.js scripts or CUDA programs) without managing local infrastructure. This provides an isolated environment identical to the production runtime.
The following guide shows the development and setup workflow using a Node.js project as an example.
## Prerequisite
- Olares version 1.12.2 or later.
- beOS Pro version 1.12.2 or later.
## 1. Initialize the container
To start coding, you must provision the container resources and select your runtime environment.
1. Open Studio and select **Create a new application**.
2. Enter an **App name**, for example: `My Web`, and click **Confirm**.
3. Select **Coding on Olares** as the creation method.
![Coding on Olares](/images/manual/olares/studio-coding-on-olares.png#bordered)
3. Select **Coding on beOS Pro** as the creation method.
![Coding on beOS Pro](/images/manual/olares/studio-coding-on-olares.png#bordered)
4. Configure the **Dev Env**:
@@ -110,7 +110,7 @@ This example demonstrates creating a basic web page manually.
</head>
<body>
<h1>Hello World</h1>
<h1>Hello Olares</h1>
<h1>Hello beOS Pro</h1>
</body>
</html>
```
@@ -125,18 +125,18 @@ This example demonstrates creating a basic web page manually.
## 4. Configure port forwarding
If you need to expose additional ports after the container is created (e.g., adding port `8081`), you must manually edit the container configuration manifests.
:::tip
You can follow the same steps to modify `OlaresManifest.yaml` and `deployment.yaml` to change the port number.
You can follow the same steps to modify `beOS ProManifest.yaml` and `deployment.yaml` to change the port number.
:::
### Modify configuration manifests
1. In Studio, click **<span class="material-symbols-outlined">box_edit</span>Edit** in the top-right to open the editor.
2. Edit `OlaresManifest.yaml`.
2. Edit `beOS ProManifest.yaml`.
a. Append the new port to the `entrances` list:
```yaml
entrances:
- authLevel: private
host: myweb
icon: https://app.cdn.olares.com/appstore/default/defaulticon.webp
icon: https://app.cdn.beos.local/appstore/default/defaulticon.webp
invisible: true
name: myweb-dev-8080
openMethod: ""
@@ -146,7 +146,7 @@ You can follow the same steps to modify `OlaresManifest.yaml` and `deployment.ya
# Add the following
- authLevel: private
host: myweb # Must match Service metadata name
icon: https://app.cdn.olares.com/appstore/default/defaulticon.webp
icon: https://app.cdn.beos.local/appstore/default/defaulticon.webp
invisible: true
name: myweb-dev-8081 # Unique identifier
openMethod: ""
@@ -162,7 +162,7 @@ You can follow the same steps to modify `OlaresManifest.yaml` and `deployment.ya
annotations:
applications.app.bytetrade.io/default-thirdlevel-domains:
'[{"appName":"myweb","entranceName":"myweb-dev-8080"},{"appName":"myweb","entranceName":"myweb-dev-8081"}]'
# entranceName must match the name used in OlaresManifest.yaml
# entranceName must match the name used in beOS ProManifest.yaml
```
b. Update the `studio-expose-ports` annotation under `spec` > `template` > `metadata`:
```yaml