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

docs: update Developer Guide and Concepts sections in Olares (#1816)

Browse Source 
* Content modification

1. Hide Recommendation
2. Update link of LLDAP
3. Update content of Service system

* Jump link reset

* Additional changes
This commit is contained in:
Meow33
2025-09-10 21:01:31 +08:00
committed by GitHub
parent 255af9e472
commit 93a20fa397
37 changed files with 73 additions and 73 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
docs/developer/develop/tutorial/note/create.md
View File

@@ -4,10 +4,10 @@ outline: [2, 3]
# How to Start Developing an Application
## Install and Launch DevBox
## Install and Launch Studio
1. Install [DevBox](https://market.olares.com/app/devbox) from the Olares Market.
2. Find the DevBox icon in the launcher panel on the Olares Desktop.
1. Install [Studio](https://market.olares.com/app/studio) from the Olares Market.
2. Find the Studio icon in the launcher panel on the Olares Desktop.
3. Click on the icon to launch the application.
![main screen](/images/developer/develop/tutorial/create/home.jpg)
@@ -25,7 +25,7 @@ Click the **Create a new application** to create a blank Olares application from
## Setup App Config
After creating the application, you can see the Olares Application Chart files generated by DevBox under the **Files** Tab. You can add, delete, or rename various configuration files as needed.
After creating the application, you can see the Olares Application Chart files generated by Studio under the **Files** Tab. You can add, delete, or rename various configuration files as needed.
![upload icon](/images/developer/develop/tutorial/create/add-file.jpg)
@@ -115,7 +115,7 @@ volumes:
The `deployment.yaml` in the `templates` folder details the deployment configuration of your application.
If your app includes several containers, such as front-end and back-end, you can add multiple containers in the `deployment.yaml` file in the `templates`. DevBox will recognize these different containers and bind each of them separately to different development containers. For example:
If your app includes several containers, such as front-end and back-end, you can add multiple containers in the `deployment.yaml` file in the `templates`. Studio will recognize these different containers and bind each of them separately to different development containers. For example:
```yaml
containers:
@@ -184,7 +184,7 @@ After configuring the above details, navigate to the **Containers** page to bind
![containers](/images/developer/develop/tutorial/create/bind.jpg)
You can set a specified development environment for the bound **Dev Container**. Currently, DevBox supports `NodeJS`, `Golang`, and `Python` **Dev Container**. Let's bind a `NodeJS` **Dev Container** to the demo frontend container and a `Golang` **Dev Container** to the server container.
You can set a specified development environment for the bound **Dev Container**. Currently, Studio supports `NodeJS`, `Golang`, and `Python` **Dev Container**. Let's bind a `NodeJS` **Dev Container** to the demo frontend container and a `Golang` **Dev Container** to the server container.
We create a new **Dev Container** here. If you have previously created an unbound **Dev Container**, you can also choose an existing container for binding here.