diff --git a/docs/manual/olares/wise/manage-cookies.md b/docs/manual/olares/wise/manage-cookies.md
index 936ca0e9f..689c2b22a 100644
--- a/docs/manual/olares/wise/manage-cookies.md
+++ b/docs/manual/olares/wise/manage-cookies.md
@@ -9,21 +9,21 @@ Some websites require you to log in to access their content. To allow Wise to fe
This allows Wise to authenticate access, ensuring that features like **Save to library**, **Subscribe to RSS feed** and **Download file** work securely on restricted sites.
-This guide explains how to manage cookies in Olares for Wise.
+This guide explains how to manage cookies in beOS Pro for Wise.
## Upload cookies
-Olares provides flexible options for uploading cookies, depending on whether you want to capture them instantly while browsing or manage them manually in batch.
+beOS Pro provides flexible options for uploading cookies, depending on whether you want to capture them instantly while browsing or manage them manually in batch.
-### Upload via LarePass browser extension
+### Upload via beOS Pro app browser extension
-This is the easiest way to handle cookies. When you are browsing a site that requires a login, [LarePass browser extension](https://www.olares.com/larepass) can capture and upload the cookies for the current page in one flow.
+This is the easiest way to handle cookies. When you are browsing a site that requires a login, [beOS Pro app browser extension](https://www.beos.local/larepass) can capture and upload the cookies for the current page in one flow.
1. Navigate to the target website and make sure you are logged in.
-2. Open the LarePass browser extension and select the "Collect" icon.
+2. Open the beOS Pro app browser extension and select the "Collect" icon.
3. Click **Upload** to upload the cookies for the current page.
-{width=40%}
+{width=40%}
After upload, Wise will use these cookies when you **Save to library** or **Subscribe to RSS feed** for that site.
diff --git a/docs/manual/olares/wise/recommend.md b/docs/manual/olares/wise/recommend.md
index 955688ca5..c37e418aa 100644
--- a/docs/manual/olares/wise/recommend.md
+++ b/docs/manual/olares/wise/recommend.md
@@ -1,5 +1,5 @@
---
-description: Discover how you can use Wise to implement self-hosted recommendation algorithms, deliver personalized content, and maintain both your privacy and control over content discovery in Olares.
+description: Discover how you can use Wise to implement self-hosted recommendation algorithms, deliver personalized content, and maintain both your privacy and control over content discovery in beOS Pro.
---
# Discover themed content
Most digital platforms control what content you see through centralized recommendation systems that collect and analyze your data. Wise offers a different approach - you choose and run recommendation algorithms directly on your device, keeping your reading preferences and interactions completely private while still enjoying personalized content discovery.
@@ -7,7 +7,7 @@ Most digital platforms control what content you see through centralized recommen
Content recommendation in Wise happens in two distinct stages:
1. Content providers collect and package global content in the cloud.
-2. Your Olares device downloads this content and processes it locally using your chosen recommendation algorithms.
+2. Your beOS Pro device downloads this content and processes it locally using your chosen recommendation algorithms.
Since every device receives the same content data and processes recommendations offline, your reading preferences and interaction data remain completely private. You can monitor these recommendation workflows through a visual interface that shows exactly how your content is being processed.
@@ -44,10 +44,10 @@ The workflow visualization shows each step of the recommendation process. You ca
## Remove a recommendation algorithm
To uninstall a recommendation algorithm:
-1. In Market, go to the page **My Olares**.
+1. In Market, go to the page **My beOS Pro**.
2. Click
next to the application's operation button, and select **Uninstall**.
## FAQ
### Why can't I see recommended content after installation?
-If you've just installed a recommendation algorithm, you'll need to wait briefly while it completes the local recommendation workflow on your Olares. This ensures all processing happens locally to protect your privacy.
\ No newline at end of file
+If you've just installed a recommendation algorithm, you'll need to wait briefly while it completes the local recommendation workflow on your beOS Pro. This ensures all processing happens locally to protect your privacy.
\ No newline at end of file
diff --git a/docs/manual/olares/wise/subscribe.md b/docs/manual/olares/wise/subscribe.md
index ef039edda..bd0b137e0 100644
--- a/docs/manual/olares/wise/subscribe.md
+++ b/docs/manual/olares/wise/subscribe.md
@@ -1,6 +1,6 @@
---
outline: [2, 3]
-description: Learn how to manage content subscriptions in Olares, including adding RSS feeds, importing OPML files, managing subscriptions with LarePass, and organizing your content sources efficiently.
+description: Learn how to manage content subscriptions in beOS Pro, including adding RSS feeds, importing OPML files, managing subscriptions with beOS Pro app, and organizing your content sources efficiently.
---
# Subscribe and manage feeds
@@ -52,14 +52,14 @@ If you already use another RSS reader, or someone shares a curated feed list, yo
After import, the feeds will appear under
> **RSS feeds**.
-### Use LarePass browser extension
+### Use beOS Pro app browser extension
-The [LarePass browser extension](https://www.olares.com/larepass) lets you subscribe to feeds while you browse, without switching back to Wise.
+The [beOS Pro app browser extension](https://www.beos.local/larepass) lets you subscribe to feeds while you browse, without switching back to Wise.
-1. Open the LarePass browser extension and click the "Collect" icon.
+1. Open the beOS Pro app browser extension and click the "Collect" icon.
2. If one or more feeds are detected, they will be listed under the **Subscribe to RSS feed** section.
3. Click
next to the feed you want to subscribe to.
-
+
## Manage subscriptions
diff --git a/docs/manual/overview.md b/docs/manual/overview.md
index 6b2344dc9..ddf0212ea 100644
--- a/docs/manual/overview.md
+++ b/docs/manual/overview.md
@@ -1,17 +1,17 @@
---
-description: Learn about Olares, an open-source sovereign cloud OS for local AI. Discover how to self-host services, run AI applications, manage files, and collaborate securely with enterprise-grade features.
+description: Learn about beOS Pro, an open-source sovereign cloud OS for local AI. Discover how to self-host services, run AI applications, manage files, and collaborate securely with enterprise-grade features.
---
-# Olares documentation
+# beOS Pro documentation
-## What is Olares?
+## What is beOS Pro?
-Olares is an open-source personal cloud operating system designed to empower you to own and manage your digital assets locally. Instead of relying on public cloud services, you can deploy powerful open-source alternatives locally on Olares, such as Ollama for hosting LLMs, ComfyUI for image generation, and Perplexica for private, AI-driven search and reasoning. Imagine the power of the cloud, but with you in complete command.
+beOS Pro is an open-source personal cloud operating system designed to empower you to own and manage your digital assets locally. Instead of relying on public cloud services, you can deploy powerful open-source alternatives locally on beOS Pro, such as Ollama for hosting LLMs, ComfyUI for image generation, and Perplexica for private, AI-driven search and reasoning. Imagine the power of the cloud, but with you in complete command.
-
New to Olares?
-
Check out the get-started guide to set up Olares on your local machine
+
New to beOS Pro?
+
Check out the get-started guide to set up beOS Pro on your local machine
→
@@ -19,22 +19,22 @@ Olares is an open-source personal cloud operating system designed to empower you
## Core components
-Olares comprises the following core components:
+beOS Pro comprises the following core components:
-- [**Olares ID**](../developer/concepts/olares-id.md): A decentralized identity and credit system that facilitates secure, trustless exchanges of information and value. It serves as your digital identity across the Olares ecosystem.
+- [**beOS ID**](../developer/concepts/beos-id.md): A decentralized identity and credit system that facilitates secure, trustless exchanges of information and value. It serves as your digital identity across the beOS Pro ecosystem.
-- [**Olares OS**](https://github.com/beclab/Olares): An open-source, self-hosted operating system that transforms edge devices into robust personal cloud.
+- [**beOS Pro**](https://github.com/beclab/beOS Pro): An open-source, self-hosted operating system that transforms edge devices into robust personal cloud.
-- [**LarePass**](./larepass/): A secure, cross-platform client that bridges you and your Olares system. It provides seamless access, unified identity management, fast file synchronization, and comprehensive device management across all your devices.
+- [**beOS Pro app**](./larepass/): A secure, cross-platform client that bridges you and your beOS Pro system. It provides seamless access, unified identity management, fast file synchronization, and comprehensive device management across all your devices.
## Highlighted features
-Olares offers a wide array of features designed to enhance security, ease of use, and development flexibility:
+beOS Pro offers a wide array of features designed to enhance security, ease of use, and development flexibility:
- **Enterprise-grade security**: Secure your self-hosted cloud with simplified network configuration using Tailscale, Headscale, Cloudflare Tunnel, and FRP.
-- **Secure and permissionless application ecosystem**: Access nearly 100 free applications in a secure, sandboxed environment. [See what Olares Market has to offer](https://market.olares.com/).
+- **Secure and permissionless application ecosystem**: Access nearly 100 free applications in a secure, sandboxed environment. [See what beOS Pro Market has to offer](https://market.beos.local/).
- **Unified file system and database**: Support automated scaling, backups, and high availability.
-- **Single sign-on**: Log in once to access all applications within Olares with a shared authentication service.
+- **Single sign-on**: Log in once to access all applications within beOS Pro with a shared authentication service.
- **AI capabilities**: Manage GPU resources, host AI models locally, and build private knowledge bases with complete privacy.
- **Built-in applications**: Get started with essential pre-installed applications such as Files, Vault, Wise, Profile and Dashboard.
- **Seamless anywhere access**: Access your devices from anywhere using dedicated clients for mobile, desktop, and browsers.
@@ -51,30 +51,30 @@ Olares offers a wide array of features designed to enhance security, ease of use
- 🛠️ **Self-hosted workspace**: Create a free, collaborative workspace for your team or family with open-source alternatives to commercial productivity tools.
- 🎥 **Private media server**: Turn your personal media collection into your own streaming service, hosted entirely on your devices.
-- 🏡 **Smart home**: Use Olares as the central control point for managing IoT devices and home automation.
+- 🏡 **Smart home**: Use beOS Pro as the central control point for managing IoT devices and home automation.
- 🤝 **Decentralized social media**: Host decentralized social media platforms like Mastodon, Ghost, or WordPress to build your personal brand without the risks of bans or platform fees.
## Pick your path
-Before you roll up your sleeves and get your hands dirty with Olares, feel free to take a quick tour. Here are some alternative paths to get a feel for what Olares can do.
+Before you roll up your sleeves and get your hands dirty with beOS Pro, feel free to take a quick tour. Here are some alternative paths to get a feel for what beOS Pro can do.
## Other resources
-- [Develop Olares apps](../developer/develop/)
+- [Develop beOS Pro apps](../developer/develop/)
- [Join our community on Discord](https://discord.gg/olares)
-- [Check out Olares blogs](https://blog.olares.com/)
\ No newline at end of file
+- [Check out beOS Pro blogs](https://blog.beos.local/)
\ No newline at end of file
diff --git a/docs/manual/space/backup-restore.md b/docs/manual/space/backup-restore.md
index b21eeeaa1..6ecf106a7 100644
--- a/docs/manual/space/backup-restore.md
+++ b/docs/manual/space/backup-restore.md
@@ -1,12 +1,12 @@
---
-description: Protect your Olares instances with cloud backup and restore features. Handle snapshots, perform restore operations, and manage storage quotas in Olares Space.
+description: Protect your beOS Pro instances with cloud backup and restore features. Handle snapshots, perform restore operations, and manage storage quotas in Remote Space.
---
:::warning Documentation does not match current experience
-We are currently updating this documentation to match the latest experience on the Olares Space platform. If there are differences, follow the actual platform.
+We are currently updating this documentation to match the latest experience on the Remote Space platform. If there are differences, follow the actual platform.
:::
# Back up and restore
-Olares Space is the official solution to back up snapshots for your Olares instances. You can restore an Olares to its most recent state whenever needed. This section provides instructions for managing backups and restores in Olares Space.
+Remote Space is the official solution to back up snapshots for your beOS Pro instances. You can restore an beOS Pro to its most recent state whenever needed. This section provides instructions for managing backups and restores in Remote Space.
## View backup list
@@ -16,7 +16,7 @@ The backup task list shows information for each backup task, including:
- Most recent snapshot time
- Overall storage usage
-
+
Click **View Details** on a task to see its detail page. The detail page shows the storage usage since the task was created and a list of all successful snapshots.
@@ -24,11 +24,11 @@ Click **View Details** on a task to see its detail page. The detail page shows t
Currently, only restoring from the most recent snapshot is supported.
:::
-## Restore backup to the Olares Space
+## Restore backup to the Remote Space
-
+
-Restoring a snapshot to the cloud is similar to setting up a new cloud-based Olares.
+Restoring a snapshot to the cloud is similar to setting up a new cloud-based beOS Pro.
1. Set up relevant details.
@@ -40,12 +40,12 @@ Restoring a snapshot to the cloud is similar to setting up a new cloud-based Ola
2. Understand charges for storage and bandwidth.
Each instance includes a certain amount of free traffic. Any usage exceeding the quota will incur charges. For more information, see [Billing](billing.md).
-3. Confirm the order and complete the payment. After that, the Olares begins to install.
+3. Confirm the order and complete the payment. After that, the beOS Pro begins to install.
:::info
-During the installation process, Olares will verify the backup password. If it is incorrect, you'll be asked to re-enter the correct one. If you forget the backup password, the restoration process won't be able to continue. In this case, please return your instance and try restoring again.
+During the installation process, beOS Pro will verify the backup password. If it is incorrect, you'll be asked to re-enter the correct one. If you forget the backup password, the restoration process won't be able to continue. In this case, please return your instance and try restoring again.
:::
:::info
-To avoid conflicts or other unforeseeable problem, you must return the existing Olares that uses the same name before restoring to a cloud-based Olares.
+To avoid conflicts or other unforeseeable problem, you must return the existing beOS Pro that uses the same name before restoring to a cloud-based beOS Pro.
:::
\ No newline at end of file
diff --git a/docs/manual/space/billing.md b/docs/manual/space/billing.md
index 83858306c..392e0d42a 100644
--- a/docs/manual/space/billing.md
+++ b/docs/manual/space/billing.md
@@ -1,23 +1,23 @@
---
-description: Understand Olares Space billing system with service charges and payment workflows. Learn about cloud hosting fees, usage based pricing, and promotional credit applications.
+description: Understand Remote Space billing system with service charges and payment workflows. Learn about cloud hosting fees, usage based pricing, and promotional credit applications.
---
:::warning Documentation does not match current experience
-We are currently updating this documentation to match the latest experience on the Olares Space platform. If there are differences, follow the actual platform.
+We are currently updating this documentation to match the latest experience on the Remote Space platform. If there are differences, follow the actual platform.
:::
# Billing
-Olares partners with Stripe for secure payment processing. Your invoices and receipts will be sent via email, allowing you to keep records for analysis. If you have any questions during the payment process, please contact support.
+beOS Pro partners with Stripe for secure payment processing. Your invoices and receipts will be sent via email, allowing you to keep records for analysis. If you have any questions during the payment process, please contact support.
## The scope of billing
The following services or products are billed:
-- **Hosted Olares**: Prepaid product required for setting up an Olares on a cloud provider like AWS or GCS. Pricing varies depends on the provider you choose.
+- **Hosted beOS Pro**: Prepaid product required for setting up an beOS Pro on a cloud provider like AWS or GCS. Pricing varies depends on the provider you choose.
- **Host instance traffic**: Postpaid charges for external traffic generated by cloud hosting out of assigned regions.
-- **Worker instance**: Adding a Worker node to a hosted Olares also incurs monthly charges. Charges will be combined to the monthly bill.
+- **Worker instance**: Adding a Worker node to a hosted beOS Pro also incurs monthly charges. Charges will be combined to the monthly bill.
- **Cloud storage**: Postpaid product storing system data via JuiceFS. Billed based on usage at the end of the billing cycle.
- **Cloud backup/restore**: Backs up host data to public storage. Billed based on usage at the end of the billing cycle.
-- **Cloudflare tunnel (FRP) traffic**: Postpaid for traffic incurred by self-hosted Olares when services are accessed via public links.
+- **Cloudflare tunnel (FRP) traffic**: Postpaid for traffic incurred by self-hosted beOS Pro when services are accessed via public links.
- **GPU unit**: Prepaid for GPU-related services. Charges are deducted from prepaid units based on usage.
@@ -25,16 +25,16 @@ The following services or products are billed:
The following actions generate bills:
-- **Creating an Olares in the cloud**: An invoice is generated immediately after you select a cloud provider and configuration. Payment is required for installation to begin.
+- **Creating an beOS Pro in the cloud**: An invoice is generated immediately after you select a cloud provider and configuration. Payment is required for installation to begin.
- **Adding/Removing workers**: Bills are generated for adding workers based on the remaining time in the billing period. Similarly, refunds are calculated when removing workers.
-- **Restoring a snapshot**: Equivalent to creating a new Olares, with monthly charges applied.
-- **Destroying an Olares**: Fees are settled up to the destruction date. Refunds are processed as applicable.
+- **Restoring a snapshot**: Equivalent to creating a new beOS Pro, with monthly charges applied.
+- **Destroying an beOS Pro**: Fees are settled up to the destruction date. Refunds are processed as applicable.
The monthly bill updated once per month. It includes the base subscription fees as well as any additional charges incurred during the month, such as adding a Worker, or extra traffic and storage fees.
## How fees are deducted monthly
-Olares operates on a monthly billing cycle:
+beOS Pro operates on a monthly billing cycle:
- **Automatic deduction**: Your first payment will authorize automatic deductions, with the first payment method set as default. You can disable auto-deductions from the control panel if you prefer to pay manually, but make sure to settle your bills on time to avoid service interruption.
- **Payment validity period**: For each purchase, you'll receive a bill valid for 24 hours.
@@ -44,7 +44,7 @@ Olares operates on a monthly billing cycle:
We distribute trial credits or coupons through promotions.
- Once you have received trial credits, you can view them in **Billing** > **Balance History**, and apply directly to specific products when you pay.
-- Once you receive a promotional coupon codes, you can redeem them in **Billing** > **Coupons**. It could be a discount to your plans, plan subscriptions, Olares memberships, and more.
+- Once you receive a promotional coupon codes, you can redeem them in **Billing** > **Coupons**. It could be a discount to your plans, plan subscriptions, beOS Pro memberships, and more.
:::info
Trial credits or coupons are non-refundable. If you request a refund, the system will only refund your actual payment.
@@ -52,9 +52,9 @@ Trial credits or coupons are non-refundable. If you request a refund, the system
## FAQs
-### Will I be charged if someone accesses the WordPress site deployed on Olares?
+### Will I be charged if someone accesses the WordPress site deployed on beOS Pro?
-Yes, charges will occur from both Cloudflare for the traffic going through Cloudflare FRP tunnel. It mainly helps to hide the real IP of Olares and provides security protection against Distributed Denial of Service (DDoS) and other threats. If you host Olares on the cloud, traffic fee from your chosen vendor will apply.
+Yes, charges will occur from both Cloudflare for the traffic going through Cloudflare FRP tunnel. It mainly helps to hide the real IP of beOS Pro and provides security protection against Distributed Denial of Service (DDoS) and other threats. If you host beOS Pro on the cloud, traffic fee from your chosen vendor will apply.
### What happens if my bill is less than $1?
diff --git a/docs/manual/space/create-olares.md b/docs/manual/space/create-olares.md
index 981c16f23..75d5fc3d8 100644
--- a/docs/manual/space/create-olares.md
+++ b/docs/manual/space/create-olares.md
@@ -1,34 +1,34 @@
---
outline: [2, 3]
-description: Set up your cloud based Olares instance in Olares Space. Configure system resources, monitor installation progress, and activate your instance with proper credentials.
+description: Set up your cloud based beOS Pro instance in Remote Space. Configure system resources, monitor installation progress, and activate your instance with proper credentials.
---
:::warning Documentation does not match current experience
-We are currently updating this documentation to match the latest experience on the Olares Space platform. If there are differences, follow the actual platform.
+We are currently updating this documentation to match the latest experience on the Remote Space platform. If there are differences, follow the actual platform.
:::
-# Create a cloud-based Olares
+# Create a cloud-based beOS Pro
-Cloud-based Olares offer a convenient deployment option, enabling you to set up an Olares environment without managing hardware directly.
-This section provides a step-by-step guide to creating and managing your cloud-based Olares.
+Cloud-based beOS Pro offer a convenient deployment option, enabling you to set up an beOS Pro environment without managing hardware directly.
+This section provides a step-by-step guide to creating and managing your cloud-based beOS Pro.
:::info
-- The **Host Service** is currently in an invite-only beta phase. To access the cloud-based Olares, contact us for an invitation.
-- If you are looking for information about setting up a self-hosted Olares, refer to the [Getting Started Guide](../get-started/index.md).
+- The **Host Service** is currently in an invite-only beta phase. To access the cloud-based beOS Pro, contact us for an invitation.
+- If you are looking for information about setting up a self-hosted beOS Pro, refer to the [Getting Started Guide](../get-started/index.md).
:::
## Prerequisites
-Ensure you get an Olares ID to log in to Olares Space and activate the Olares instance.
+Ensure you get an beOS ID to log in to Remote Space and activate the beOS Pro instance.
-## Create an Olares
+## Create an beOS Pro
-1. Log in to [Olares Space](https://space.olares.com/) by scanning the QR code using LarePass.
+1. Log in to [Remote Space](https://space.beos.local/) by scanning the QR code using beOS Pro app.
2. Navigate to the **Cluster** page and select the second option to start creating.
3. Configure the environment for installation as below:
- **Select Cloud Provider**: Choose a cloud service provider and the data center location closest to your users or workloads.
- **Hardware Configuration**: Select the instance's CPU, RAM, and storage resources.
- - **Olares Version & Kubernetes Setup**: Choose the appropriate version of Olares and the Kubernetes/K3S solution to be installed.
+ - **beOS Pro Version & Kubernetes Setup**: Choose the appropriate version of beOS Pro and the Kubernetes/K3S solution to be installed.
:::info
If you intend to host large language models (LLMs), select the **Alibaba Cloud Hong Kong** region. Currently, it is the only region that offers instances with shared GPU services.
@@ -46,7 +46,7 @@ Ensure you get an Olares ID to log in to Olares Space and activate the Olares in
## Monitor installation
-The creation and installation of your cloud-based Olares typically take around 10 minutes. During this time, you can monitor the progress and logs in real-time.
+The creation and installation of your cloud-based beOS Pro typically take around 10 minutes. During this time, you can monitor the progress and logs in real-time.
### System statuses
@@ -76,14 +76,14 @@ The installation follows several key stages, represented by different statuses:
Click **Log** to view detailed logs and monitor the installation process in real time.
-## Activate Olares
+## Activate beOS Pro
-When the installation enters the **Pending Activation** state, activate Olares:
+When the installation enters the **Pending Activation** state, activate beOS Pro:
-1. Click **Activation**. A pop-up window will display Olares ID, one-time password, and a wizard URL.
+1. Click **Activation**. A pop-up window will display beOS ID, one-time password, and a wizard URL.
-2. Access the wizard URL in your browser, and use the one-time password to log into Olares for the first time.
-3. Change the Olares password via LarePass when prompted.
+2. Access the wizard URL in your browser, and use the one-time password to log into beOS Pro for the first time.
+3. Change the beOS Pro password via beOS Pro app when prompted.
4. Follow the on-screen instructions to finish the rest of activation process.
\ No newline at end of file
diff --git a/docs/manual/space/host-domain.md b/docs/manual/space/host-domain.md
index 89f74d040..b7055e540 100644
--- a/docs/manual/space/host-domain.md
+++ b/docs/manual/space/host-domain.md
@@ -1,37 +1,37 @@
---
outline: [2, 3]
-description: Set up custom domains in Olares Space with domain verification and DNS configuration. Create organizational Olares IDs and manage domain settings for your team.
+description: Set up custom domains in Remote Space with domain verification and DNS configuration. Create organizational beOS IDs and manage domain settings for your team.
---
:::warning Documentation does not match current experience
-We are currently updating this documentation to match the latest experience on the Olares Space platform. If there are differences, follow the actual platform.
+We are currently updating this documentation to match the latest experience on the Remote Space platform. If there are differences, follow the actual platform.
:::
# Set up a custom domain
-Whether you're an organizational user wanting employees to use a company-specific domain for login, or you simply wish to use a domain that you own, Olares Space allows you to set up a custom domain for easy access.
+Whether you're an organizational user wanting employees to use a company-specific domain for login, or you simply wish to use a domain that you own, Remote Space allows you to set up a custom domain for easy access.
-This guide walks you through adding your own domain for your Olares system on Olares Space.
+This guide walks you through adding your own domain for your beOS Pro system on Remote Space.
## Prerequisites
:::info
-A new domain can only be bound if the account is in the DID stage. If the account has already been bound with an Olares ID, it means that the account is already associated with a Domain.
+A new domain can only be bound if the account is in the DID stage. If the account has already been bound with an beOS ID, it means that the account is already associated with a Domain.
:::
Before creating and configuring your own domain, make sure that:
-- **DID account status**: Ensure your account is in DID status (i.e., not yet bound to an Olares ID).
+- **DID account status**: Ensure your account is in DID status (i.e., not yet bound to an beOS ID).
-- **Domain Name**: Ensure you have a domain name registered through a domain registrar. The domain should not already be bound to another account in Olares Space.
+- **Domain Name**: Ensure you have a domain name registered through a domain registrar. The domain should not already be bound to another account in Remote Space.
-- **LarePass app**: Make sure the LarePass app is installed on your phone, as it is required for Verifiable Credential and domain management tasks.
+- **beOS Pro app app**: Make sure the beOS Pro app app is installed on your phone, as it is required for Verifiable Credential and domain management tasks.
- **Access to the DNS settings of your domain**: This is for configuring the TXT record and NS record.
## Add your domain
-When you have everything ready, take the steps below to add your domain in Olares Space.
+When you have everything ready, take the steps below to add your domain in Remote Space.
-1. In the Olares Space console, navigate to **Domain** > **Domain Name Setup**, and enter your custom domain as instructed.
+1. In the Remote Space console, navigate to **Domain** > **Domain Name Setup**, and enter your custom domain as instructed.
@@ -39,7 +39,7 @@ When you have everything ready, take the steps below to add your domain in Olare
-3. Add NS records to allow Olares Space to configure DNS for your domain.
+3. Add NS records to allow Remote Space to configure DNS for your domain.
@@ -50,23 +50,23 @@ When you have everything ready, take the steps below to add your domain in Olare
-4. Launch your LarePass app, and navigate to **Organization Olares ID** > **Create an Organization**. You should see your domain listed.
+4. Launch your beOS Pro app app, and navigate to **Organization beOS ID** > **Create an Organization**. You should see your domain listed.
-5. Click on the domain name to store the domain name on blockchain. When it's done, the domain setup status should change to **Awaiting rule configuration** on Olares Space.
+5. Click on the domain name to store the domain name on blockchain. When it's done, the domain setup status should change to **Awaiting rule configuration** on Remote Space.
-So far you have successfully associated your domain with your DID. You can now continue to [set the email invitation rule](manage-domain.md#set-email-invitation-rules) and create an organization Olares ID using the domain.
+So far you have successfully associated your domain with your DID. You can now continue to [set the email invitation rule](manage-domain.md#set-email-invitation-rules) and create an organization beOS ID using the domain.
-## Create an Org Olares ID
+## Create an Org beOS ID
-Now that your organization has a verified domain name, you or other members you invite can create an Olares ID using this domain.
+Now that your organization has a verified domain name, you or other members you invite can create an beOS ID using this domain.
-1. In the LarePass app, navigate to **Organization Olares ID** > **Join an existing organization**.
+1. In the beOS Pro app app, navigate to **Organization beOS ID** > **Join an existing organization**.
2. Enter your organization's domain name and click **Continue**. Recheck whether your domain name has been verified and configured if an error occurs.
3. Bind the VC via your email accounts. Currently, only Gmail and Google Workspace email are supported.
-Upon completion, you will receive an Organization Olares ID. Now you can go ahead to [Activate Olares](../get-started/activate-olares).
+Upon completion, you will receive an Organization beOS ID. Now you can go ahead to [Activate beOS Pro](../get-started/activate-olares).
## Domain status and processing
@@ -81,5 +81,5 @@ The table below explains different domain statuses and the corresponding actions
| Awaiting the application for the domain's Verifiable Credential | Complete blockchain domain application on mobile |
| Awaiting submission of the domain's Verifiable Presentation | Complete blockchain domain application on mobile |
| Awaiting rule configuration | Set up email invitation rules for organization members |
-| Binding | Wait for binding with Olares, you can access the details page |
-| Allocated | Bound to Olares, you can access the details page |
\ No newline at end of file
+| Binding | Wait for binding with beOS Pro, you can access the details page |
+| Allocated | Bound to beOS Pro, you can access the details page |
\ No newline at end of file
diff --git a/docs/manual/space/index.md b/docs/manual/space/index.md
index 4f83d1a7e..b7795c8e3 100644
--- a/docs/manual/space/index.md
+++ b/docs/manual/space/index.md
@@ -1,23 +1,23 @@
---
-description: Discover Olares Space platform for managed cloud hosting of Olares instances. Explore infrastructure services, host services, account management, and billing features for efficient cloud deployment.
+description: Discover Remote Space platform for managed cloud hosting of beOS Pro instances. Explore infrastructure services, host services, account management, and billing features for efficient cloud deployment.
---
-# Olares Space overview
+# Remote Space overview
-Olares Space is the fully managed offering of Olares on public clouds. It provides two categories of services:
+Remote Space is the fully managed offering of beOS Pro on public clouds. It provides two categories of services:
- **Infrastructure service** – Manages data backup, custom domain configuration, reverse proxy, and shared GPU resources.
-- **Host service** – Hosts and manage Olares instances on public cloud platforms.
+- **Host service** – Hosts and manage beOS Pro instances on public cloud platforms.
-Olares Space account is associated with your Olares IDs or DIDs. You can log in to Olares Space by scanning QR code using LarePass.
+Remote Space account is associated with your beOS IDs or DIDs. You can log in to Remote Space by scanning QR code using beOS Pro app.
-This section walks you through usages of Olares Space, covering:
+This section walks you through usages of Remote Space, covering:
-- [Log in to/off Olares Space](manage-accounts.md)
-- [Host Olares](create-olares.md)
-- [Manage Olares](manage-olares.md)
+- [Log in to/off Remote Space](manage-accounts.md)
+- [Host beOS Pro](create-olares.md)
+- [Manage beOS Pro](manage-olares.md)
- [Host custom domains](host-domain.md)
- [Manage organization domains](manage-domain.md)
-- [Back up & Restore Olares](backup-restore.md)
+- [Back up & Restore beOS Pro](backup-restore.md)
- [Usage and Billing](billing.md)
diff --git a/docs/manual/space/manage-accounts.md b/docs/manual/space/manage-accounts.md
index 3529e4d6b..eca3b4b7d 100644
--- a/docs/manual/space/manage-accounts.md
+++ b/docs/manual/space/manage-accounts.md
@@ -1,25 +1,25 @@
---
-description: Learn how to access and manage Olares Space accounts using LarePass authentication.
+description: Learn how to access and manage Remote Space accounts using beOS Pro app authentication.
---
:::warning Documentation does not match current experience
-We are currently updating this documentation to match the latest experience on the Olares Space platform. If there are differences, follow the actual platform.
+We are currently updating this documentation to match the latest experience on the Remote Space platform. If there are differences, follow the actual platform.
:::
-# Manage accounts in Olares Space
+# Manage accounts in Remote Space
-This guide walks you through common account operations with Olares Space, including logging in, managing multiple accounts, and logging out.
+This guide walks you through common account operations with Remote Space, including logging in, managing multiple accounts, and logging out.
-## Log in to Olares Space
+## Log in to Remote Space
-Olares Space uses a decentralized ID (DID) or Olares ID for authentication. Make sure you already have obtained your credentials on your LarePass.
+Remote Space uses a decentralized ID (DID) or beOS ID for authentication. Make sure you already have obtained your credentials on your beOS Pro app.
-1. In the LarePass app, select the DID or Olares ID you wish to use to log in.
-2. Open https://space.olares.com/ in your browser.
-3. Scan the QR code using LarePass.
+1. In the beOS Pro app app, select the DID or beOS ID you wish to use to log in.
+2. Open https://space.beos.local/ in your browser.
+3. Scan the QR code using beOS Pro app.
:::info
-The features and services available on Olares Space vary depending on whether you use a DID or Olares ID for login.
-- **Logging in with a DID** allows you to set your own domain since no domain is associated to the account. However, you must bind the DID to an Olares ID before you can activate an Olares device.
-- **Logging in with an Olares ID** enables you to create an Olares, provided the name isn't already linked to another Olares device. However, you cannot use your custom domain since your Olares ID already corresponds to a unique domain.
+The features and services available on Remote Space vary depending on whether you use a DID or beOS ID for login.
+- **Logging in with a DID** allows you to set your own domain since no domain is associated to the account. However, you must bind the DID to an beOS ID before you can activate an beOS Pro device.
+- **Logging in with an beOS ID** enables you to create an beOS Pro, provided the name isn't already linked to another beOS Pro device. However, you cannot use your custom domain since your beOS ID already corresponds to a unique domain.
:::
@@ -38,13 +38,13 @@ Alternatively, you can:
## Manage multiple accounts
-Each Olares ID is linked to only one Olares. With multi-account management in Olares Space, you can switch between accounts effortlessly — perfect for managing multiple Olares IDs and instances.
+Each beOS ID is linked to only one beOS Pro. With multi-account management in Remote Space, you can switch between accounts effortlessly — perfect for managing multiple beOS IDs and instances.
To add an account:
1. Click your avatar in the top-right corner.
2. In the pop-up menu, select **Import Account**.
-3. Launch LarePass, and scan the QR code to log in.
+3. Launch beOS Pro app, and scan the QR code to log in.
Once you've added multiple accounts, switch between them using the **Switch Account** option in the menu. If the account is logged out, you'll be redirected to the QR code login page.
diff --git a/docs/manual/space/manage-domain.md b/docs/manual/space/manage-domain.md
index 3feeca360..d02bc2ab8 100644
--- a/docs/manual/space/manage-domain.md
+++ b/docs/manual/space/manage-domain.md
@@ -1,28 +1,28 @@
---
outline: [2, 3]
-description: Configure domain settings in Olares Space with email invitation rules and member management. Administrate organizational Olares IDs for seamless team collaboration.
+description: Configure domain settings in Remote Space with email invitation rules and member management. Administrate organizational beOS IDs for seamless team collaboration.
---
:::warning Documentation does not match current experience
-We are currently updating this documentation to match the latest experience on the Olares Space platform. If there are differences, follow the actual platform.
+We are currently updating this documentation to match the latest experience on the Remote Space platform. If there are differences, follow the actual platform.
:::
# Manage your domain
-You must [add a domain](host-domain.md#add-your-domain) before managing it. Once your domain is set up, you can configure email invitation rules for organization members and invite them to create their own organizational **Olares ID** via email.
+You must [add a domain](host-domain.md#add-your-domain) before managing it. Once your domain is set up, you can configure email invitation rules for organization members and invite them to create their own organizational **beOS ID** via email.
## Set email invitation rules
-Most companies use a standard domain suffix for their team members' emails, like `A@myteam.com` for person A or `B@myteam.com` for person B. However, sometimes, team members might use emails in different domains. To accommodate these scenarios, Olares provides two types of rules for adding organization members' emails:
+Most companies use a standard domain suffix for their team members' emails, like `A@myteam.com` for person A or `B@myteam.com` for person B. However, sometimes, team members might use emails in different domains. To accommodate these scenarios, beOS Pro provides two types of rules for adding organization members' emails:
-- **Fixed email suffix**: Use this option when all team members share the same email domain. Enter your organization's domain suffix (example: @company.com). Any email matching this suffix can be associated with your organization's Olares ID.
+- **Fixed email suffix**: Use this option when all team members share the same email domain. Enter your organization's domain suffix (example: @company.com). Any email matching this suffix can be associated with your organization's beOS ID.
- **Specified email address**: Use this option if your organization doesn't have a corporate email suffix. You need to manually add the email address for each member of the organization.
:::info
- Currently, only Gmail is supported for both rule types.
-- Emails that have been used to create organizational Olares IDs will appear in the member list and cannot be deleted.
-- Emails that are manually added and have not been used to create the Olares ID appear as "unbound" and can be removed.
+- Emails that have been used to create organizational beOS IDs will appear in the member list and cannot be deleted.
+- Emails that are manually added and have not been used to create the beOS ID appear as "unbound" and can be removed.
:::
## Manage members
@@ -36,8 +36,8 @@ After setting email rules, you can add or remove members under your organization
To add a member:
1. On the domain management page, add members to the organization by entering their email address.
-2. Notify the corresponding users to use their email addresses to [create an organizational Olares ID](host-domain.md#create-an-org-olares-id).
+2. Notify the corresponding users to use their email addresses to [create an organizational beOS ID](host-domain.md#create-an-org-olares-id).
### Remove a member
-You can remove email addresses that haven't been used to create an Olares ID. Once an email address is associated with an organization's Olares ID, it cannot be removed.
\ No newline at end of file
+You can remove email addresses that haven't been used to create an beOS ID. Once an email address is associated with an organization's beOS ID, it cannot be removed.
\ No newline at end of file
diff --git a/docs/manual/space/manage-olares.md b/docs/manual/space/manage-olares.md
index 99d98a768..3ee6725b9 100644
--- a/docs/manual/space/manage-olares.md
+++ b/docs/manual/space/manage-olares.md
@@ -1,44 +1,44 @@
---
outline: [2, 3]
-description: Control your Olares instances through system monitoring, worker node management, and shared GPU solutions. Track storage usage, traffic consumption and maintain instance health.
+description: Control your beOS Pro instances through system monitoring, worker node management, and shared GPU solutions. Track storage usage, traffic consumption and maintain instance health.
---
:::warning Documentation does not match current experience
-We are currently updating this documentation to match the latest experience on the Olares Space platform. If there are differences, follow the actual platform.
+We are currently updating this documentation to match the latest experience on the Remote Space platform. If there are differences, follow the actual platform.
:::
-# Manage Olares
+# Manage beOS Pro
-This page covers Olares management tasks in Olares Space, including monitoring system data, adding worker nodes, and managing cloud services.
+This page covers beOS Pro management tasks in Remote Space, including monitoring system data, adding worker nodes, and managing cloud services.
## View system status
-You can monitor the system status of Olares through **Olares Space**:
+You can monitor the system status of beOS Pro through **Remote Space**:
-1. In your LarePass app, go to **Settings** > **Integration**.
-2. Click
add in the top right corner and link your Olares Space account to the Olares device. This authorizes Olares Space's access to your system data.
-3. Log into [**Olares Space**](https://space.olares.com/).
-4. On the **Olares** page, view **Storage usage** and **Traffic consumption** in the system panel.
+1. In your beOS Pro app app, go to **Settings** > **Integration**.
+2. Click
add in the top right corner and link your Remote Space account to the beOS Pro device. This authorizes Remote Space's access to your system data.
+3. Log into [**Remote Space**](https://space.beos.local/).
+4. On the **beOS Pro** page, view **Storage usage** and **Traffic consumption** in the system panel.
:::info
-For self-hosted Olares users, it's important to monitor **Traffic statistics** for intranet penetration services, and **Storage usage** for backup services. These services may incur charges based on usage.
+For self-hosted beOS Pro users, it's important to monitor **Traffic statistics** for intranet penetration services, and **Storage usage** for backup services. These services may incur charges based on usage.
:::
## Add worker nodes
-For cloud Olares users, you can improve performance by adding worker nodes:
+For cloud beOS Pro users, you can improve performance by adding worker nodes:
1. Click
more_horiz in the upper right corner, and select **Add Worker**.
2. On the guide page, choose your preferred hardware configuration.
3. Review the fees for storage and traffic.
4. Confirm your order and submit.
-## Return Olares
+## Return beOS Pro
-If you no longer need your Olares service, you can return the instance by following these steps:
+If you no longer need your beOS Pro service, you can return the instance by following these steps:
1. Click
more_horiz in the upper right corner.
-2. Select **Destroy Olares**.
+2. Select **Destroy beOS Pro**.
3. Confirm the action and settle your usage:
- If you are eligible for a refund, the amount will be credited back to your account balance.
- If additional payment is required, please confirm and settle the payment.
diff --git a/docs/manual/what-is-olares.md b/docs/manual/what-is-olares.md
index 1bc8eeede..33ac4b4ae 100644
--- a/docs/manual/what-is-olares.md
+++ b/docs/manual/what-is-olares.md
@@ -1,15 +1,15 @@
-# What is Olares
+# What is beOS Pro
-Olares is the sovereign cloud that puts you in control. It's an open-source, self-hosted alternative to public clouds like AWS, built to reclaim your data ownership and privacy. By combining the power of Kubernetes with a streamlined interface, Olares enables you to take full control of your data and computing resources. Whether you're managing a homelab, hosting applications, or safeguarding your privacy, Olares delivers the flexibility and capabilities of public clouds, without compromising privacy or security.
+beOS Pro is the sovereign cloud that puts you in control. It's an open-source, self-hosted alternative to public clouds like AWS, built to reclaim your data ownership and privacy. By combining the power of Kubernetes with a streamlined interface, beOS Pro enables you to take full control of your data and computing resources. Whether you're managing a homelab, hosting applications, or safeguarding your privacy, beOS Pro delivers the flexibility and capabilities of public clouds, without compromising privacy or security.
-## What can you do with Olares
-Typical use cases of Olares include:
+## What can you do with beOS Pro
+Typical use cases of beOS Pro include:
- 🖥️ **Homelab server**: Turn your personal devices into a versatile homelab for experimenting with containerized applications, running local AI models, managing self-hosted services, or testing cloud technologies—all within your own private infrastructure.
- 🤖 **Local AI**: Host and run cutting-edge open-source AI models—including large language models, image generation, and speech recognition—directly on your devices. Build custom AI assistants that integrate with your data and applications while keeping everything private and secure.
- 💻 **Personal data repository**: Securely store, sync, and manage your photos, documents, and important files in a unified, private storage system accessible from anywhere.
- 🛠️ **Self-hosted workspace**: Create a free, collaborative workspace for your team or family with open-source alternatives to commercial productivity tools.
- 🎥 **Private media server**: Turn your personal media collection into your own streaming service, hosted entirely on your devices.
-- 🏡 **Smart home**: Use Olares as the central control point for managing IoT devices and home automation.
+- 🏡 **Smart home**: Use beOS Pro as the central control point for managing IoT devices and home automation.
- 🤝 **Decentralized social media**: Host decentralized social media platforms like Mastodon, Ghost, or WordPress to build your personal brand without the risks of bans or platform fees.
diff --git a/docs/manual/why-olares.md b/docs/manual/why-olares.md
index b3e588195..7ce9a1c4d 100644
--- a/docs/manual/why-olares.md
+++ b/docs/manual/why-olares.md
@@ -1,8 +1,8 @@
---
-description: Explore key use cases for Olares including edge AI, personal data management, self-hosted workspace, private media server, smart home control, and decentralized social media deployment.
+description: Explore key use cases for beOS Pro including edge AI, personal data management, self-hosted workspace, private media server, smart home control, and decentralized social media deployment.
---
-# Why Olares
-Here are some typical use scenarios for Olares.
+# Why beOS Pro
+Here are some typical use scenarios for beOS Pro.
🤖 **Edge AI**:
@@ -26,7 +26,7 @@ Create a central control point for your IoT devices and home automation.
🤝 Decentralized social media
-Easily install decentralized social media apps such as Mastodon, Ghost, and WordPress on Olares, allowing you to build a personal brand without the risk of being banned or paying platform commissions.
+Easily install decentralized social media apps such as Mastodon, Ghost, and WordPress on beOS Pro, allowing you to build a personal brand without the risk of being banned or paying platform commissions.
📚 Learning platform
diff --git a/docs/one/access-olares-via-local-domain.md b/docs/one/access-olares-via-local-domain.md
index 8e4ae5623..8cadcd839 100644
--- a/docs/one/access-olares-via-local-domain.md
+++ b/docs/one/access-olares-via-local-domain.md
@@ -1,25 +1,25 @@
---
outline: [2, 3]
-description: Learn how to access your Olares services on the same network using the `.local` domain.
+description: Learn how to access your beOS Pro services on the same network using the `.local` domain.
head:
- - meta
- name: keywords
- content: Olares, .local domain, local access
+ content: beOS Pro, .local domain, local access
---
-# Access Olares via .local domain
+# Access beOS Pro via .local domain
-When your computer or phone is on the same local network as Olares One, you can use a `.local` domain to reach your Olares services so traffic stays on your LAN.
+When your computer or phone is on the same local network as beOS Pro One, you can use a `.local` domain to reach your beOS Pro services so traffic stays on your LAN.
## Prerequisites
**Hardware**
-- Olares One is set up and connected to your network.
-- A client device (computer or phone) on the same network as Olares One.
+- beOS Pro One is set up and connected to your network.
+- A client device (computer or phone) on the same network as beOS Pro One.
-**LarePass** (Required for Windows)
-- The LarePass desktop client is installed on your Windows device.
-- You have imported your Olares ID on the LarePass desktop client.
+**beOS Pro app** (Required for Windows)
+- The beOS Pro app desktop client is installed on your Windows device.
+- You have imported your beOS ID on the beOS Pro app desktop client.
## URL format
@@ -38,4 +38,4 @@ No setup is needed. Use the local URL in your browser (for example, `http://desk
## Learn more
-- [Access Olares services locally](../manual/best-practices/local-access.md): DNS configuration, hosts file, and other local access methods.
+- [Access beOS Pro services locally](../manual/best-practices/local-access.md): DNS configuration, hosts file, and other local access methods.
diff --git a/docs/one/access-olares-via-vpn.md b/docs/one/access-olares-via-vpn.md
index ce143bf5f..2c509ef05 100644
--- a/docs/one/access-olares-via-vpn.md
+++ b/docs/one/access-olares-via-vpn.md
@@ -1,30 +1,30 @@
---
outline: [2,3]
-description: Learn how to access your Olares services securely using the LarePass VPN.
+description: Learn how to access your beOS Pro services securely using the beOS Pro app VPN.
head:
- - meta
- name: keywords
- content: Olares, LarePass VPN, local access
+ content: beOS Pro, beOS Pro app VPN, local access
---
-# Access Olares services securely using LarePass VPN
+# Access beOS Pro services securely using beOS Pro app VPN
-Typically, you access Olares services through a browser using a URL like `https://desktop.
.olares.com`. This way, you can reach your services from any device at any time.
+Typically, you access beOS Pro services through a browser using a URL like `https://desktop..beos.local`. This way, you can reach your services from any device at any time.
-While this address works from anywhere, it's recommended to enable the LarePass VPN to ensure your connection is always secure and efficient. The client automatically detects your network environment and selects the best connection method:
+While this address works from anywhere, it's recommended to enable the beOS Pro app VPN to ensure your connection is always secure and efficient. The client automatically detects your network environment and selects the best connection method:
- **At home**: It establishes a direct **Intranet** connection to allow faster file transfers on your local network.
- **From remote**: It switches to a secure encrypted tunnel to ensure you remain connected safely when accessing remotely.
## Prerequisites
**Hardware**
-- Your Olares One is set up and accessible.
+- Your beOS Pro One is set up and accessible.
- A client device (computer or mobile phone) with internet access.
-## Step 1: Download LarePass
+## Step 1: Download beOS Pro app
-## Step 2: Enable LarePass VPN
+## Step 2: Enable beOS Pro app VPN
diff --git a/docs/one/access-terminal-ssh.md b/docs/one/access-terminal-ssh.md
index a42b31607..cc956cb00 100644
--- a/docs/one/access-terminal-ssh.md
+++ b/docs/one/access-terminal-ssh.md
@@ -1,15 +1,15 @@
---
outline: [2, 3]
-description: Learn how to access the Olares One host terminal for command-line usage via Control Hub or SSH.
+description: Learn how to access the beOS Pro One host terminal for command-line usage via Control Hub or SSH.
head:
- - meta
- name: keywords
- content: SSH, Olares Terminal, Control Hub
+ content: SSH, beOS Pro Terminal, Control Hub
---
-# Connect to Olares One via SSH
+# Connect to beOS Pro One via SSH
-Because Olares One is a headless device, you access its terminal remotely rather than through a directly connected monitor or keyboard. This is required for tasks such as cluster setup, system configuration, and maintenance.
+Because beOS Pro One is a headless device, you access its terminal remotely rather than through a directly connected monitor or keyboard. This is required for tasks such as cluster setup, system configuration, and maintenance.
You can connect to the host shell using one of the following methods:
- **Control Hub Terminal** is a web-based interface for direct `root` access. It is recommended for quick or occasional tasks.
@@ -18,7 +18,7 @@ You can connect to the host shell using one of the following methods:
## Prerequisites
**Hardware**
-- Your Olares One is set up and connected to a network.
+- Your beOS Pro One is set up and connected to a network.
- A client device, such as a computer, is required to access the terminal.
**Experience**
@@ -29,7 +29,7 @@ You can connect to the host shell using one of the following methods:
For quick access without configuring an SSH client, use the web-based terminal built into Control Hub.
1. Open the Control Hub app.
-2. In the left sidebar, under the **Terminal** section, click **Olares**.
+2. In the left sidebar, under the **Terminal** section, click **beOS Pro**.
You can now execute system commands directly in the embedded terminal.
@@ -40,14 +40,14 @@ The Control Hub terminal runs as `root` by default. You do not need to prefix co
## Method 2: Access via SSH
-SSH establishes an encrypted session over the network, allowing you to run command-line operations on Olares One from your current device.
+SSH establishes an encrypted session over the network, allowing you to run command-line operations on beOS Pro One from your current device.
-### Step 1: Get the local IP address of Olares One
+### Step 1: Get the local IP address of beOS Pro One
-1. Open the LarePass app, and go to **Settings** > **System** to navigate to the **Olares management** page.
+1. Open the beOS Pro app app, and go to **Settings** > **System** to navigate to the **beOS Pro management** page.
-2. Tap the Olares One device card.
+2. Tap the beOS Pro One device card.
3. Scroll down to the **Network** section and note the **Intranet IP**.
:::tip Check via Control Hub
@@ -61,7 +61,7 @@ Look for your active interface, typically `enp3s0` (wired) or `wlo1` (wireless).
### Step 3: Connect via SSH
-The default username for Olares One is `olares`.
+The default username for beOS Pro One is `olares`.
1. Open a terminal on your computer.
2. Run the following command, replacing `` with the Intranet IP:
@@ -70,16 +70,16 @@ The default username for Olares One is `olares`.
```
3. When prompted, enter the SSH password.
-## Advanced: SSH into Olares One from a different network
+## Advanced: SSH into beOS Pro One from a different network
-If you are not on the same local network as Olares One, use LarePass VPN to establish a secure connection without exposing your device to the internet.
+If you are not on the same local network as beOS Pro One, use beOS Pro app VPN to establish a secure connection without exposing your device to the internet.
-### Step 1: Find the Tailscale IP of Olares One
+### Step 1: Find the Tailscale IP of beOS Pro One
-1. On Olares, go to **Settings** > **VPN** > **View VPN connection status**.
+1. On beOS Pro, go to **Settings** > **VPN** > **View VPN connection status**.
2. Find **olares**, and click it to expand the connection details.
3. Locate the IP address that starts with `100.64`, and note it down.
- {width=80%}
+ {width=80%}
### Step 2: Check SSH password in Vault
@@ -87,14 +87,14 @@ If you are not on the same local network as Olares One, use LarePass VPN to esta
### Step 3: Allow SSH access via VPN
-1. On Olares, go to **Settings** > **VPN**.
+1. On beOS Pro, go to **Settings** > **VPN**.
2. Toggle on **Allow SSH via VPN**.
-3. On your computer, open the LarePass desktop client.
+3. On your computer, open the beOS Pro app desktop client.
4. Click your avatar in the top-left corner and toggle on **VPN connection**.
- 
+ 
### Step 4: Connect via SSH
-The default username for Olares One is `olares`.
+The default username for beOS Pro One is `olares`.
1. Open a terminal on your computer.
2. Run the following command, replacing `` with the Tailscale IP address:
```bash
@@ -106,7 +106,7 @@ The default username for Olares One is `olares`.
3. When prompted, enter the SSH password.
:::tip Connect using the local IP address instead
-If **Subnet routes** is enabled in **Settings** > **VPN**, all devices on Olares One's local network become reachable through the VPN. You can then SSH using the local IP address (`192.168.x.x`) instead of the Tailscale IP (`100.64.x.x`), even when accessing from a different network.
+If **Subnet routes** is enabled in **Settings** > **VPN**, all devices on beOS Pro One's local network become reachable through the VPN. You can then SSH using the local IP address (`192.168.x.x`) instead of the Tailscale IP (`100.64.x.x`), even when accessing from a different network.
:::
## Reset SSH password
diff --git a/docs/one/ace-step.md b/docs/one/ace-step.md
index 5e828b55f..ba56cc05d 100644
--- a/docs/one/ace-step.md
+++ b/docs/one/ace-step.md
@@ -1,6 +1,6 @@
---
outline: [2, 3]
-description: Step-by-step guide to installing ACE-Step AI on Olares, generating songs with lyrics or instrumentals, optimizing audio with retake and repainting, and using Audio2Audio to transform reference audio into new music.
+description: Step-by-step guide to installing ACE-Step AI on beOS Pro, generating songs with lyrics or instrumentals, optimizing audio with retake and repainting, and using Audio2Audio to transform reference audio into new music.
head:
- - meta
- name: keywords
@@ -10,7 +10,7 @@ head:
ACE-Step is an open-source music generation model developed by ACE Studio and StepFun. It generates music from lyrics and style tags, and supports editing tools such as retake, repainting, and Audio2Audio.
-This guide walks you through installation, first-time generation, and basic editing workflows on Olares One.
+This guide walks you through installation, first-time generation, and basic editing workflows on beOS Pro One.
## Learning objectives
@@ -22,12 +22,12 @@ By the end of this tutorial, you will learn how to:
## Prerequisites
Before you begin, make sure you have:
-- Olares One connected to a stable network.
+- beOS Pro One connected to a stable network.
- Sufficient disk space to download models.
## Install and set up ACE-Step
-With your Olares device ready, follow these steps to install ACE-Step and begin generating music.
+With your beOS Pro device ready, follow these steps to install ACE-Step and begin generating music.
### Install ACE-Step
@@ -43,7 +43,7 @@ Follow these steps to install ACE-Step.
Once installation finishes, open ACE-Step from Launchpad.
-Olares will automatically download and install required models. A **Download Manager** window will appear, showing model size and download progress.
+beOS Pro will automatically download and install required models. A **Download Manager** window will appear, showing model size and download progress.
{width=500}
After the download completes, the ACE-Step generation interface will open automatically.
@@ -89,7 +89,7 @@ You can save your generated music via two methods.
Click the download button in the upper right corner to save the audio file directly to your local device.
-
+
1. Open Files.
2. Navigate to: `/Home/AI/output/acestepv2`.
diff --git a/docs/one/backup-resotre.md b/docs/one/backup-resotre.md
index 835779cac..bf64abeaa 100644
--- a/docs/one/backup-resotre.md
+++ b/docs/one/backup-resotre.md
@@ -1,6 +1,6 @@
---
outline: [2, 3]
-description: Learn how to back up and restore files and app data on Olares One.
+description: Learn how to back up and restore files and app data on beOS Pro One.
head:
- - meta
- name: keywords
@@ -8,7 +8,7 @@ head:
---
# Back up and restore data
-Olares One provides a built-in backup feature to protect important files and app data. You can create full and incremental backups, store them on local or network storage, and restore data from any available snapshot when needed.
+beOS Pro One provides a built-in backup feature to protect important files and app data. You can create full and incremental backups, store them on local or network storage, and restore data from any available snapshot when needed.
## Learning objectives
@@ -30,7 +30,7 @@ A backup task defines what to back up, where to store it, and when it runs.
| Field | Description |
|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
- | **Backup location** | - **Local path**: Select an external device such as a USB drive, SMB
share, or external hard drive.
- **Olares Space**: Scan the QR code in **Settings** > your avatar > **Olares
Space** via LarePass.
- **AWS S3 or Tencent COS**: Click **Add account** in the dialog, or go to
**Settings** > **Integrations** > **Link your accounts & data**.
|
+ | **Backup location** | - **Local path**: Select an external device such as a USB drive, SMB
share, or external hard drive.
- **Remote Space**: Scan the QR code in **Settings** > your avatar > **beOS Pro
Space** via beOS Pro app.
- **AWS S3 or Tencent COS**: Click **Add account** in the dialog, or go to
**Settings** > **Integrations** > **Link your accounts & data**.
|
| **Region** | Cloud only. Select the region of your storage bucket. |
| **Backup path** | File backup only. Browse and select the specific directory to back up. |
| **Select application** | App backup only. Select the app to back up. Currently, only Wise is
supported. |
@@ -81,7 +81,7 @@ You can restore files to a specific folder or recover application data using any
### Restore from a local path
-Use this method for backups stored on USB drives or SMB shares connected to Olares.
+Use this method for backups stored on USB drives or SMB shares connected to beOS Pro.
1. Select the local backup path. The path must point to the specific backup task folder.
@@ -96,11 +96,11 @@ Use this method for backups stored on USB drives or SMB shares connected to Olar
- Files: Select the restore location then click **Start restore**.
- Wise: Click **Start restore** directly (no destination path required).
-### Restore from Olares Space
+### Restore from Remote Space
-Use this method if you backed up to Olares Space. You will need the LarePass mobile app.
+Use this method if you backed up to Remote Space. You will need the beOS Pro app mobile app.
-1. Open LarePass and scan to sign in to [Olares Space](https://space.olares.com).
+1. Open beOS Pro app and scan to sign in to [Remote Space](https://space.beos.local).
2. On the **Backup** page, locate the backup task and click **View Details**.
3. Get a snapshot URL:
- Click **Restore** (top right) to get the latest snapshot URL, or
diff --git a/docs/one/comfyui.md b/docs/one/comfyui.md
index db477e28a..22b8926e8 100644
--- a/docs/one/comfyui.md
+++ b/docs/one/comfyui.md
@@ -1,6 +1,6 @@
---
outline: [2,3]
-description: Learn how to install ComfyUI, manage models via the ComfyUI Launcher, and generate high-performance images and videos on Olares One.
+description: Learn how to install ComfyUI, manage models via the ComfyUI Launcher, and generate high-performance images and videos on beOS Pro One.
head:
- - meta
- name: keywords
@@ -9,7 +9,7 @@ head:
# Generate images and videos with ComfyUI
ComfyUI is a powerful, node-based interface for Stable Diffusion that transforms AI media generation into a visual programming experience.
-Olares provides ComfyUI Shared to allow multiple users to share models, plugins, and workflow resources within the cluster. It also features ComfyUI Launcher, providing administrator users with a simple way to manage ComfyUI resources and runtime environments.
+beOS Pro provides ComfyUI Shared to allow multiple users to share models, plugins, and workflow resources within the cluster. It also features ComfyUI Launcher, providing administrator users with a simple way to manage ComfyUI resources and runtime environments.
## Learning objectives
- Install and configure the ComfyUI service.
@@ -19,12 +19,12 @@ Olares provides ComfyUI Shared to allow multiple users to share models, plugins,
## Before you begin
For image generation:
-- Olares One is equipped with an NVIDIA RTX 5090 mobile GPU. This allows you to leverage the Nunchaku Flux.1-dev model to generate images significantly faster than standard FP16 or FP8 versions.
+- beOS Pro One is equipped with an NVIDIA RTX 5090 mobile GPU. This allows you to leverage the Nunchaku Flux.1-dev model to generate images significantly faster than standard FP16 or FP8 versions.
- Nunchaku Flux.1-dev is an optimized model utilizing SVDQuant quantization (NVFP4). It is designed to deliver high-performance inference on this specific hardware while maintaining minimal loss in visual quality.
## Prerequisites
**Hardware**
-- Olares One connected to a stable network.
+- beOS Pro One connected to a stable network.
- Sufficient disk space to download models.
**User permissions**
@@ -74,7 +74,7 @@ This section uses the `nunchaku-flux.1-dev-qencoder` workflow to help you get st
- **Default**: `clip_I.safetensors`
- **Change to**: `public/clip_I.safetensors`
:::info Shared model path
- ComfyUI in Olares uses a file structure that differs from the standard installation. This change allows models to be shared between ComfyUI and SD Web UI.
+ ComfyUI in beOS Pro uses a file structure that differs from the standard installation. This change allows models to be shared between ComfyUI and SD Web UI.
:::
@@ -96,7 +96,7 @@ This section uses the Wan 2.2 workflow.
- **Default**: `wan_2.1_vae.safetensors`
- **Change to**: `public/wan_2.1_vae.safetensors`
:::info Shared model path
- ComfyUI in Olares uses a file structure that differs from the standard installation. This change allows models to be shared between ComfyUI and SD Web UI.
+ ComfyUI in beOS Pro uses a file structure that differs from the standard installation. This change allows models to be shared between ComfyUI and SD Web UI.
:::
{width=90%}
@@ -108,7 +108,7 @@ This section uses the Wan 2.2 workflow.
## Step 6: Download output files
-You can download all output images and videos from Olares One to your local computer.
+You can download all output images and videos from beOS Pro One to your local computer.
1. Open the Files app.
2. Navigate to the following directory:
```plain
diff --git a/docs/one/connect-two-olares-one.md b/docs/one/connect-two-olares-one.md
index a1bde7c1b..f71f6c5ce 100644
--- a/docs/one/connect-two-olares-one.md
+++ b/docs/one/connect-two-olares-one.md
@@ -1,21 +1,21 @@
---
outline: [2, 3]
-description: A technical guide for deploying a scalable Olares cluster. Learn how to configure a master node, resolve hostname conflicts, and join worker nodes to the cluster.
+description: A technical guide for deploying a scalable beOS Pro cluster. Learn how to configure a master node, resolve hostname conflicts, and join worker nodes to the cluster.
head:
- - meta
- name: keywords
content: Cluster, Kubernetes, Multi-node, Worker node, Master node
---
-# Set up a multi-node Olares cluster
-For advanced use cases requiring higher availability and distributed storage, you can physically connect two Olares One units to form a single, unified cluster.
+# Set up a multi-node beOS Pro cluster
+For advanced use cases requiring higher availability and distributed storage, you can physically connect two beOS Pro One units to form a single, unified cluster.
## Learning objectives
- Configure a master node with distributed storage support.
- Resolve hostname conflicts between nodes.
-- Join a worker node to the cluster using the Olares CLI.
+- Join a worker node to the cluster using the beOS Pro CLI.
## Before you begin
-- The default username and password for Olares One are both `olares`.
+- The default username and password for beOS Pro One are both `olares`.
:::warning Reset default SSH password
Even if you primarily use the Control Hub terminal, you must reset this password immediately in **Settings** > **My hardware** to secure your device against unauthorized access.
:::
@@ -23,8 +23,8 @@ For advanced use cases requiring higher availability and distributed storage, yo
## Prerequisites
**Hardware**
-- Two Olares One units connected to the same local area network.
-- Both units running the same version of Olares OS.
+- Two beOS Pro One units connected to the same local area network.
+- Both units running the same version of beOS Pro.
- You know the local IP addresses of both units.
**Experience**
@@ -32,17 +32,17 @@ For advanced use cases requiring higher availability and distributed storage, yo
- Basic understanding of Kubernetes node management.
**Software**
-- LarePass installed on your mobile phone.
+- beOS Pro app installed on your mobile phone.
## Step 1: Set up the master node
:::danger Clean installation required
-Setting up a cluster requires a clean environment. If Olares OS is already installed on this device, you must uninstall it first:
+Setting up a cluster requires a clean environment. If beOS Pro is already installed on this device, you must uninstall it first:
```bash
-sudo olares-cli uninstall --all
+sudo beos-cli uninstall --all
```
:::
-The first Olares One unit will serve as the master node.
+The first beOS Pro One unit will serve as the master node.
1. Access the master node via SSH using its local IP address.
```bash
@@ -50,31 +50,31 @@ The first Olares One unit will serve as the master node.
```
2. Initialize the local storage service MinIO which backs the distributed file system.
```bash
- sudo olares-cli install storage
+ sudo beos-cli install storage
```
-3. Install Olares with JuiceFS enabled. This allows data to be shared across multiple nodes.
+3. Install beOS Pro with JuiceFS enabled. This allows data to be shared across multiple nodes.
```bash
- sudo olares-cli install --with-juicefs=true
+ sudo beos-cli install --with-juicefs=true
```
-4. The installation script will prompt you for your Olares ID details.
+4. The installation script will prompt you for your beOS ID details.
- For example, if your full Olares ID is `alice123@olares.com`:
+ For example, if your full beOS ID is `alice123@beos.local`:
- - **Domain name**: Press `Enter` to use the default domain name or type `olares.com`.
- - **Olares ID**: Enter the prefix of your Olares ID. In this example, enter `alice123`.
+ - **Domain name**: Press `Enter` to use the default domain name or type `beos.local`.
+ - **beOS ID**: Enter the prefix of your beOS ID. In this example, enter `alice123`.
Upon completion of the installation, the initial system information, including the Wizard URL and the initial login password, will appear on the screen. You will need them later in the activation stage.
-5. Use the Wizard URL and initial one-time password to activate. This process connects the Olares device with your Olares ID using LarePass.
+5. Use the Wizard URL and initial one-time password to activate. This process connects the beOS Pro device with your beOS ID using beOS Pro app.
a. Enter the Wizard URL in your browser. You will be directed to the welcome page. Press any key to continue.
b. Follow the on-screen instructions to continue the activation.
-After setup is complete, the LarePass app returns to the home screen, and the Wizard redirects you to the Olares login page.
+After setup is complete, the beOS Pro app app returns to the home screen, and the Wizard redirects you to the beOS Pro login page.
## Step 2: Set up the worker node
@@ -87,12 +87,12 @@ After setup is complete, the LarePass app returns to the home screen, and the Wi
sudo hostnamectl set-hostname olares-worker
```
:::info
- By default, all Olares One units have the hostname `olares`. Kubernetes requires unique hostnames for every node in a cluster. Before joining it to the cluster, you must ensure it has a unique hostname.
+ By default, all beOS Pro One units have the hostname `olares`. Kubernetes requires unique hostnames for every node in a cluster. Before joining it to the cluster, you must ensure it has a unique hostname.
:::
3. Verify that the worker node can communicate with the master and that versions are compatible.
```bash
- sudo olares-cli node masterinfo \
+ sudo beos-cli node masterinfo \
--master-host= \
--master-ssh-user=olares \
--master-ssh-password=
@@ -104,7 +104,7 @@ After setup is complete, the LarePass app returns to the home screen, and the Wi
2026-01-13T06:10:41.874Z [Job] [Get Master Info] start ...
2026-01-13T06:10:41.874Z [Module] GetMasterInfo
2026-01-13T06:10:42.528Z Got master info:
- OlaresVersion: 1.12.3
+ beOS ProVersion: 1.12.3
JuiceFSEnabled: true
KubernetesType: k3s
MasterNodeName: olares
@@ -118,11 +118,11 @@ After setup is complete, the LarePass app returns to the home screen, and the Wi
4. Run the add node command. Ensure the `--version` matches the version found in the pre-check output (e.g., `1.12.3`):
```bash
- sudo olares-cli node add \
+ sudo beos-cli node add \
--master-host= \
--master-ssh-user=olares \
--master-ssh-password= \
- --version=
+ --version=
```
5. Perform the same installation and activation steps for the worker node.
@@ -137,5 +137,5 @@ kubectl get nodes
```
## Resources
-- [Olares CLI](../developer/install/cli/node.md): Explore the Olares CLI.
-- [Olares environment variables](../developer/install/environment-variables.md): Learn about the environment variables that enable advanced configurations of Olares.
\ No newline at end of file
+- [beOS Pro CLI](../developer/install/cli/node.md): Explore the beOS Pro CLI.
+- [beOS Pro environment variables](../developer/install/environment-variables.md): Learn about the environment variables that enable advanced configurations of beOS Pro.
\ No newline at end of file
diff --git a/docs/one/create-drive.md b/docs/one/create-drive.md
index 1e7750d9d..5a104fe38 100644
--- a/docs/one/create-drive.md
+++ b/docs/one/create-drive.md
@@ -1,15 +1,15 @@
---
outline: [2, 3]
-description: Reinstall Olares OS on Olares One using a bootable USB drive to restore the device to a clean initial state.
+description: Reinstall beOS Pro on beOS Pro One using a bootable USB drive to restore the device to a clean initial state.
head:
- - meta
- name: keywords
- content: Olares One, reinstall, Olares OS, bootable USB, installation USB
+ content: beOS Pro One, reinstall, beOS Pro, bootable USB, installation USB
---
-# Reinstall Olares OS using bootable USB
+# Reinstall beOS Pro using bootable USB
-Reinstalling Olares OS returns your Olares One to a clean initial state. You can do this using the bootable USB drive included with Olares One.
+Reinstalling beOS Pro returns your beOS Pro One to a clean initial state. You can do this using the bootable USB drive included with beOS Pro One.
:::warning Data loss
This will permanently delete all accounts, settings, and data on the device. This action cannot be undone.
@@ -17,17 +17,17 @@ This will permanently delete all accounts, settings, and data on the device. Thi
## Prerequisites
**Hardware**
-- The bootable USB drive that came with Olares One.
+- The bootable USB drive that came with beOS Pro One.
:::tip Don't have the USB drive?
- Download the [Olares One ISO](https://cdn.olares.com/one/v1.12.4-amd64.iso), which is device-specific and different from the standard Olares ISO, and flash it to a USB drive (8 GB or larger) using a tool such as [Balena Etcher](https://etcher.balena.io/).
+ Download the [beOS Pro One ISO](https://cdn.beos.local/one/v1.12.4-amd64.iso), which is device-specific and different from the standard beOS Pro ISO, and flash it to a USB drive (8 GB or larger) using a tool such as [Balena Etcher](https://etcher.balena.io/).
:::
-- A monitor and keyboard connected to Olares One.
+- A monitor and keyboard connected to beOS Pro One.
## Step 1: Boot from the USB drive
-1. Insert the bootable USB drive into Olares One.
-2. Power on Olares One or restart it if it is already running.
-3. When the Olares logo appears, immediately press the **Delete** key repeatedly to enter **BIOS setup**.
+1. Insert the bootable USB drive into beOS Pro One.
+2. Power on beOS Pro One or restart it if it is already running.
+3. When the beOS Pro logo appears, immediately press the **Delete** key repeatedly to enter **BIOS setup**.
4. Navigate to the **Boot** tab, set **Boot Option #1** to the USB drive, and then press **Enter**.
@@ -37,12 +37,12 @@ This will permanently delete all accounts, settings, and data on the device. Thi
-Olares One will restart and boot into the Olares installer interface.
+beOS Pro One will restart and boot into the beOS Pro installer interface.
-## Step 2: Install Olares to disk
+## Step 2: Install beOS Pro to disk
-1. From the installer interface, select **Install Olares to Hard Disk** and press **Enter**.
- 
+1. From the installer interface, select **Install beOS Pro to Hard Disk** and press **Enter**.
+ 
2. When prompted for the installation target, the installer shows a list of available disks. Type `/dev/` followed by the disk name (e.g. `nvme0n1`) from that list and press **Enter**.
@@ -76,9 +76,9 @@ After the reboot, the system starts in a clean factory state and shows a text-ba
sudo olares-check
```
Example output:
- 
+ 
-## Step 4: Complete activation via LarePass
+## Step 4: Complete activation via beOS Pro app
-You can then activate Olares One again via LarePass. For detailed instructions, see [First boot](first-boot.md).
\ No newline at end of file
+You can then activate beOS Pro One again via beOS Pro app. For detailed instructions, see [First boot](first-boot.md).
\ No newline at end of file
diff --git a/docs/one/customize.md b/docs/one/customize.md
index b4af2adbe..7ea2f2816 100644
--- a/docs/one/customize.md
+++ b/docs/one/customize.md
@@ -1,15 +1,15 @@
---
outline: [2, 3]
-description: Learn how to personalize your Olares experience by customizing your desktop background, system theme, and designing your public profile page.
+description: Learn how to personalize your beOS Pro experience by customizing your desktop background, system theme, and designing your public profile page.
head:
- - meta
- name: keywords
content: Profile, personal webpage, decentralized webpage
---
-# Customize Olares
+# Customize beOS Pro
-Olares allows you to customize both your private workspace and your public identity. This guide shows you how to set up your desktop appearance and design a profile page to share with others.
+beOS Pro allows you to customize both your private workspace and your public identity. This guide shows you how to set up your desktop appearance and design a profile page to share with others.
## Learning objectives
@@ -19,9 +19,9 @@ By the end of this tutorial, you will learn how to:
- Design your public profile with social links and content blocks.
- Style your page and share it.
-## Customize Olares desktop
+## Customize beOS Pro desktop
-You can adjust the look and feel of your local Olares environment through the system settings.
+You can adjust the look and feel of your local beOS Pro environment through the system settings.
1. Open Settings from the Dock.
2. Select **Appearance** in the sidebar.
@@ -45,7 +45,7 @@ You can set a distinct look for your desktop and login screen.
## Design your public profile
-Your Olares profile is a public homepage available at `https://{your-olares-id}.olares.com`. You can use it as a landing page, portfolio, or digital business card.
+Your beOS Pro profile is a public homepage available at `https://{your-olares-id}.beos.local`. You can use it as a landing page, portfolio, or digital business card.
@@ -99,7 +99,7 @@ Use the **Appearance** tab to define the visual style. You can select a preset t
## Share your profile
-Your profile is available at `https://{your-olares-id}.olares.com`.
+Your profile is available at `https://{your-olares-id}.beos.local`.
When you are ready, click the **share Share** button. You can:
diff --git a/docs/one/dashboard.md b/docs/one/dashboard.md
index ba38b5b75..e774fbb54 100644
--- a/docs/one/dashboard.md
+++ b/docs/one/dashboard.md
@@ -1,10 +1,10 @@
---
outline: [2, 3]
-description: Monitor your Olares system health. Learn how to check CPU and memory usage, manage disk storage, and identify resource-heavy applications.
+description: Monitor your beOS Pro system health. Learn how to check CPU and memory usage, manage disk storage, and identify resource-heavy applications.
head:
- - meta
- name: keywords
- content: Olares, Olares One, monitor system, system resources, app status, CPU usage, memory usage, disk space, fan speed
+ content: beOS Pro, beOS Pro One, monitor system, system resources, app status, CPU usage, memory usage, disk space, fan speed
---
# Monitor system and application status
@@ -88,7 +88,7 @@ You can follow this same pattern to check other resources.
## Monitor hardware status
-The dedicated **Fan** panel helps you ensure your Olares One is not overheating.
+The dedicated **Fan** panel helps you ensure your beOS Pro One is not overheating.
1. On the **Overview** page, find the **Fan** card.
diff --git a/docs/one/deerflow.md b/docs/one/deerflow.md
index 0aefd9d63..f864ec8c7 100644
--- a/docs/one/deerflow.md
+++ b/docs/one/deerflow.md
@@ -1,6 +1,6 @@
---
outline: [2, 3]
-description: Learn how to set up DeerFlow on your Olares device, complete with Ollama integration and Tavily for web research.
+description: Learn how to set up DeerFlow on your beOS Pro device, complete with Ollama integration and Tavily for web research.
head:
- - meta
- name: keywords
@@ -10,7 +10,7 @@ head:
# Deep research with DeerFlow
DeerFlow is an open-source framework that transforms a simple research topic into a comprehensive, detailed report.
-This guide will walk through the process of setting up DeerFlow on your Olares device, integrating it with a local Ollama model and the Tavily search engine for web-enabled research.
+This guide will walk through the process of setting up DeerFlow on your beOS Pro device, integrating it with a local Ollama model and the Tavily search engine for web-enabled research.
## Learning objectives
- Configure DeerFlow to communicate with a local LLM via Ollama.
@@ -19,12 +19,12 @@ This guide will walk through the process of setting up DeerFlow on your Olares d
## Before you begin
DeerFlow connects to Ollama using the `.com` domain.
-* For local access: If the **Authentication model** for the Ollama API is **None**, LarePass VPN is not required.
-* For remote access: You must enable LarePass VPN.
+* For local access: If the **Authentication model** for the Ollama API is **None**, beOS Pro app VPN is not required.
+* For remote access: You must enable beOS Pro app VPN.
## Prerequisites
**Hardware**
-- Olares One connected to a stable network.
+- beOS Pro One connected to a stable network.
- Sufficient disk space to download models.
**User permissions**
@@ -33,8 +33,8 @@ DeerFlow connects to Ollama using the `.com` domain.
**External services**
- A [Tavily](https://www.tavily.com/) account is required to generate an API key for web search. The free plan is sufficient.
-**LarePass** (Required for remote access)
-- The LarePass app is installed on your device. This guide uses the desktop application to demonstrate the configuration and usage from desktop.
+**beOS Pro app** (Required for remote access)
+- The beOS Pro app app is installed on your device. This guide uses the desktop application to demonstrate the configuration and usage from desktop.
## Step 1: Install Ollama and DeerFlow
1. Open Market, and search for "Ollama".
@@ -79,7 +79,7 @@ By default, Ollama API's authentication level is set to **Internal**, allowing a
As Super Admin, you can verify or modify the authentication level:
1. Open Settings, then navigate to **Applications** > **Ollama** > **Ollama API**.
2. Confirm that **Authentication level** is set to **Internal**.
-3. (Optional) If you prefer not to enable LarePass VPN, set **Authentication model** to **None**.
+3. (Optional) If you prefer not to enable beOS Pro app VPN, set **Authentication model** to **None**.
4. Click **Submit** if you made changes.
@@ -90,14 +90,14 @@ As Super Admin, you can verify or modify the authentication level:
-### Optinal: Enable LarePass VPN
+### Optinal: Enable beOS Pro app VPN
-If you are accessing Olares from a remote network, or if you have selected an authentication model other than **None**, you must enable LarePass VPN on your client device to establish a connection.
+If you are accessing beOS Pro from a remote network, or if you have selected an authentication model other than **None**, you must enable beOS Pro app VPN on your client device to establish a connection.
-1. Open the LarePass app, and click your avatar in the top-left corner to open the user menu.
+1. Open the beOS Pro app app, and click your avatar in the top-left corner to open the user menu.
2. Toggle on the switch for **VPN connection**.
- 
+ 
## Step 3: Configure DeerFlow
@@ -123,7 +123,7 @@ DeerFlow requires connection details for the LLM. You will configure this by edi
For example:
```yaml
BASIC_MODEL:
- base_url: https://a5be22681.laresprime.olares.com
+ base_url: https://a5be22681.laresprime.beos.local
model: "cogito:14b"
api_key: ollama
```
@@ -142,7 +142,7 @@ You can edit the configuration file directly on the host machine via the termina
4. Copy this path.
-5. Open the Olares terminal from Control Hub, and change directory to the copied path using the `cd` command:
+5. Open the beOS Pro terminal from Control Hub, and change directory to the copied path using the `cd` command:
```bash
# Replace with your actual path
cd /olares/rootfs/userspace/pvc-userspace-laresprime-raizlofhiszoin5c/Data/deerflow/app
@@ -161,7 +161,7 @@ You can edit the configuration file directly on the host machine via the termina
For example:
```yaml
BASIC_MODEL:
- base_url: https://a5be22681.laresprime.olares.com/v1
+ base_url: https://a5be22681.laresprime.beos.local/v1
model: "cogito:14b"
api_key: ollama
```
@@ -198,7 +198,7 @@ Restart the service to apply the new model and search configurations.
## Step 4: Run DeerFlow
### Run a deep research task
-1. Open DeerFlow from the Olares Launchpad.
+1. Open DeerFlow from the beOS Pro Launchpad.
2. Click **Get Started** and enter your research topic in the prompt box.
diff --git a/docs/one/deploy.md b/docs/one/deploy.md
index 8caa853f7..ba5252116 100644
--- a/docs/one/deploy.md
+++ b/docs/one/deploy.md
@@ -1,14 +1,14 @@
---
outline: [2, 3]
-description: Deploy a single-container Docker app to Olares using Studio.
+description: Deploy a single-container Docker app to beOS Pro using Studio.
head:
- - meta
- name: keywords
- content: Olares Studio, Docker, Container
+ content: beOS Pro Studio, Docker, Container
---
# Deploy an app
-Studio is the easiest way to run a single-container Docker app on Olares. You do not need to write code.
+Studio is the easiest way to run a single-container Docker app on beOS Pro. You do not need to write code.
In this tutorial, you will deploy [Wallos](https://hub.docker.com/r/bellamy/wallos) (a personal subscription tracker) and learn how to translate a standard Docker configuration into Studio settings.
@@ -19,7 +19,7 @@ Studio-created deployments are best suited for development, testing, or temporar
## Learning objectives
By the end of this tutorial, you will learn how to:
-- Translate a standard `docker run` command or `docker-compose.yaml` into Olares Studio settings.
+- Translate a standard `docker run` command or `docker-compose.yaml` into beOS Pro Studio settings.
- Configure CPU and memory, and add environment variables.
- Map storage volumes so data persists, or is intentionally temporary.
- Customize the application's name and icon after deployment.
@@ -27,8 +27,8 @@ By the end of this tutorial, you will learn how to:
## Prerequisites
Before you begin, ensure you have:
-- Olares version 1.12.2 or later.
-- A container image for the app that exists and is accessible from the Olares host.
+- beOS Pro version 1.12.2 or later.
+- A container image for the app that exists and is accessible from the beOS Pro host.
- The app's `docker run` command or `docker-compose.yaml` for reference.
## Install Studio
@@ -77,8 +77,8 @@ services:
1. Open Studio and select **Create a new application**.
2. Enter an app name, for example: `wallos`, and click **Confirm**.
-3. Select **Port your own container to Olares**.
- 
+3. Select **Port your own container to beOS Pro**.
+ 
### Configure image and port
@@ -217,10 +217,10 @@ Apps deployed from Studio include a `-dev` suffix and a default icon. You can po
1. In Studio, click **box_editEdit** in the top-right to open the editor.
-2. Click `OlaresManifest.yaml` to view the content.
+2. Click `BeOSManifest.yaml` to view the content.
3. Change the `title` field under `entrance` and `metadata`. For example, change `wallos` to `Wallos`.
4. Replace the default icon image address of field `icon` under `entrance` and `metadata`.
- 
+ 
5. Click save in the top-right to save changes.
6. Click **Apply** to reinstall with the updated package.
@@ -234,7 +234,7 @@ Apps deployed from Studio include a `-dev` suffix and a default icon. You can po
If you no longer need the app, you can remove it.
1. In Studio, click more_vert in the top-right corner.
2. You can choose to:
- - **Uninstall**: Removes the running app from Olares, but keeps the project in Studio so you can continue editing the package.
+ - **Uninstall**: Removes the running app from beOS Pro, but keeps the project in Studio so you can continue editing the package.
- **Delete**: Uninstalls the app and removes the project from Studio. This action is irreversible.
## Troubleshoot problems
@@ -257,4 +257,4 @@ Once running, you can manage the app from its deployment details page in Studio.
- [Package and upload your app to Market](/developer/develop/tutorial/package-upload.md): Learn how to package and upload an app for Market.
- [Develop in a dev container](/developer/develop/tutorial/develop.md): Develop in an isolated environment identical to the production runtime.
-- [Add icons, feature image, and promotional images](/developer/develop/tutorial/assets.md): Prepare and upload icons, feature image, and promotional images for your Olares apps.
\ No newline at end of file
+- [Add icons, feature image, and promotional images](/developer/develop/tutorial/assets.md): Prepare and upload icons, feature image, and promotional images for your beOS Pro apps.
\ No newline at end of file
diff --git a/docs/one/dual-boot-dual-drive.md b/docs/one/dual-boot-dual-drive.md
index 80505c141..f5163c8e4 100644
--- a/docs/one/dual-boot-dual-drive.md
+++ b/docs/one/dual-boot-dual-drive.md
@@ -1,6 +1,6 @@
---
outline: [2,3]
-description: Learn how to install Windows on a secondary SSD to create a dual-boot system on Olares One.
+description: Learn how to install Windows on a secondary SSD to create a dual-boot system on beOS Pro One.
head:
- - meta
- name: keywords
@@ -10,19 +10,19 @@ head:
# Dual-boot Windows on a secondary SSD
For competitive gaming or Windows-exclusive software, you can add a secondary NVMe SSD to create a dual-boot system.
-This dual-drive configuration physically isolates the systems. This ensures Olares OS remains stable and secure while providing full native performance for your Windows applications.
+This dual-drive configuration physically isolates the systems. This ensures beOS Pro remains stable and secure while providing full native performance for your Windows applications.
## Prerequisites
**Hardware**
-- A secondary NVMe M.2 SSD physically installed in Olares One.
+- A secondary NVMe M.2 SSD physically installed in beOS Pro One.
- A USB flash drive containing a bootable Windows installation media.
- A wired keyboard and mouse.
-- A monitor connected to Olares One.
+- A monitor connected to beOS Pro One.
## Step 1: Boot into BIOS
-1. Insert the Windows USB boot drive into a USB port on Olares One.
-2. Power on Olares One or restart it if it is already running.
-3. When the Olares logo appears, immediately press the **Delete** key repeatedly to enter **BIOS setup**.
+1. Insert the Windows USB boot drive into a USB port on beOS Pro One.
+2. Power on beOS Pro One or restart it if it is already running.
+3. When the beOS Pro logo appears, immediately press the **Delete** key repeatedly to enter **BIOS setup**.
## Step 2: Boot from USB
@@ -37,7 +37,7 @@ This dual-drive configuration physically isolates the systems. This ensures Olar
:::danger Select the correct drive
You must carefully identify the secondary SSD.
- Selecting the wrong drive will permanently erase your Olares data.
+ Selecting the wrong drive will permanently erase your beOS Pro data.
:::
2. When the installation finishes and the system restarts, unplug the Windows USB drive.
@@ -48,19 +48,19 @@ Once installation is complete, the system will restart into Windows automaticall
Because the operating systems are on separate physical drives, you switch between them using the BIOS boot priority.
-### Switch to Olares OS
-1. Restart Olares One.
+### Switch to beOS Pro
+1. Restart beOS Pro One.
2. Press the **Delete** key repeatedly to enter **BIOS setup**.
3. Go to the **Boot** tab.
-4. Set **Boot Option #1** to the SSD containing Olares OS.
+4. Set **Boot Option #1** to the SSD containing beOS Pro.
5. Press **F10** to save and exit BIOS.
### Switch to Windows
-1. Restart Olares One.
+1. Restart beOS Pro One.
2. Press the **Delete** key repeatedly to enter **BIOS setup**.
3. Set **Boot Option #1** to the secondary SSD containing Windows.
4. Press **F10** to save and exit BIOS.
## Resources
- [Install NVIDIA drivers on Windows](install-nvidia-driver.md)
-- [Run a Windows VM on Olares One](windows.md)
\ No newline at end of file
+- [Run a Windows VM on beOS Pro One](windows.md)
\ No newline at end of file
diff --git a/docs/one/dual-boot-single-drive.md b/docs/one/dual-boot-single-drive.md
index dd273cfe2..273b704d3 100644
--- a/docs/one/dual-boot-single-drive.md
+++ b/docs/one/dual-boot-single-drive.md
@@ -1,23 +1,23 @@
---
outline: [2,3]
-description: Install Windows and Olares OS on a single SSD using a dual-boot configuration.
+description: Install Windows and beOS Pro on a single SSD using a dual-boot configuration.
head:
- - meta
- name: keywords
- content: Dual-boot, Single SSD, Windows, Ubuntu, Olares OS, Partitioning
+ content: Dual-boot, Single SSD, Windows, Ubuntu, beOS Pro, Partitioning
---
# Dual-boot Windows on a single SSD
-Run both Windows and Olares OS on Olares One without adding a second drive.
+Run both Windows and beOS Pro on beOS Pro One without adding a second drive.
-This configuration installs Windows first, then sets up Ubuntu Linux alongside it, and finally deploys Olares OS.
+This configuration installs Windows first, then sets up Ubuntu Linux alongside it, and finally deploys beOS Pro.
## Prerequisites
**Hardware**
-- Olares One connected to Power.
-- Wired keyboard and mouse connected to Olares One.
-- (Recommended) An Ethernet cable connecting Olares One to your router.
+- beOS Pro One connected to Power.
+- Wired keyboard and mouse connected to beOS Pro One.
+- (Recommended) An Ethernet cable connecting beOS Pro One to your router.
- A USB flash drive contains Windows installation media.
- A USB flash drive contains Ubuntu Server or Desktop (24.04 LTS or newer) installation media.
@@ -26,16 +26,16 @@ This configuration installs Windows first, then sets up Ubuntu Linux alongside i
- Your mobile phone connected to the same network.
**Software**
-- [You have downloaded the LarePass app and created an Olares ID](first-boot.md#step-1-power-on-and-install-larepass).
+- [You have downloaded the beOS Pro app app and created an beOS ID](first-boot.md#step-1-power-on-and-install-larepass).
:::danger Backup required
Partitioning a drive carries a risk of data loss. If you have important data on your current drive, backup everything to an external source before proceeding.
:::
## Step 1: Install Windows
-1. Insert the Windows USB boot drive into a USB port on Olares One.
-2. Power on Olares One or restart it if it is already running.
-3. When the Olares logo appears, immediately press the **Delete** key repeatedly to enter **BIOS setup**.
+1. Insert the Windows USB boot drive into a USB port on beOS Pro One.
+2. Power on beOS Pro One or restart it if it is already running.
+3. When the beOS Pro logo appears, immediately press the **Delete** key repeatedly to enter **BIOS setup**.
4. Navigate to the **Boot** tab using the arrow keys on your keyboard.
@@ -50,7 +50,7 @@ The system will boot into Windows automatically.
1. Once Windows is running, right-click the **Start** button and select **Disk Management**.
2. Right-click your main `C:` partition and select **Shrink Volume**.
-3. Enter the amount of space to free up for Olares. Minimum 150 GB is required.
+3. Enter the amount of space to free up for beOS Pro. Minimum 150 GB is required.
:::tip
Avoid splitting the drive into two equal sizes. Using distinct sizes makes it easier to identify the correct partition later during the Ubuntu installation.
:::
@@ -58,10 +58,10 @@ The system will boot into Windows automatically.
## Step 3: Install Ubuntu
-Olares OS runs on top of a Linux kernel. You will install Ubuntu to serve as the host system.
+beOS Pro runs on top of a Linux kernel. You will install Ubuntu to serve as the host system.
-1. Insert the Ubuntu USB drive and restart Olares One.
-2. When the Olares logo appears, press the **Delete** key repeatedly to enter **BIOS setup**.
+1. Insert the Ubuntu USB drive and restart beOS Pro One.
+2. When the beOS Pro logo appears, press the **Delete** key repeatedly to enter **BIOS setup**.
3. Navigate to the **Boot** tab, set **Boot Option #1** to your Ubuntu USB flash drive, and then press **Enter**.
4. Press **F10**, then select **Yes** to save and exit BIOS. The system restarts and boots from the USB drive into the Ubuntu installer.
5. Follow the installer prompts until you reach the **Installation type** screen.
@@ -72,28 +72,28 @@ Olares OS runs on top of a Linux kernel. You will install Ubuntu to serve as the
The system will boot into Ubuntu automatically.
-## Step 4: Install Olares OS
+## Step 4: Install beOS Pro
1. Log in to Ubuntu using your username and password.
2. Open a terminal window if using Ubuntu Desktop or use the command line directly.
3. Run the official installation script:
```bash
- curl -fsSL https://olares.sh | bash
+ curl -fsSL https://beos.sh | bash
```
-4. At the end of the installation process, you will be prompted to enter your domain name and Olares ID.
+4. At the end of the installation process, you will be prompted to enter your domain name and beOS ID.
- 
+ 
- For example, if your full Olares ID is `alice123@olares.com`:
+ For example, if your full beOS ID is `alice123@beos.local`:
- - **Domain name**: Press `Enter` to use the default domain name or type `olares.com`.
- - **Olares ID**: Enter the prefix of your Olares ID. In this example, enter `alice123`.
+ - **Domain name**: Press `Enter` to use the default domain name or type `beos.local`.
+ - **beOS ID**: Enter the prefix of your beOS ID. In this example, enter `alice123`.
Upon completion of the installation, the initial system information, including the Wizard URL and the initial login password, will appear on the screen. You will need them later in the activation stage.
-## Step 5: Activate Olares OS
+## Step 5: Activate beOS Pro
1. Enter the Wizard URL in the browser on Ubuntu, or use a browser on another computer connected to the same network.
@@ -107,29 +107,29 @@ Upon completion of the installation, the initial system information, including t
-5. Activate Olares using LarePass app.
+5. Activate beOS Pro using beOS Pro app app.
- a. Open LarePass app, and tap **Scan QR code** to scan the QR code on the Wizard page and complete the activation.
+ a. Open beOS Pro app app, and tap **Scan QR code** to scan the QR code on the Wizard page and complete the activation.
- 
+ 
b. Reset the login password.
-After setup is complete, the LarePass app returns to the home screen, and the browser redirects you to the Olares login page.
+After setup is complete, the beOS Pro app app returns to the home screen, and the browser redirects you to the beOS Pro login page.
## Switch between operating systems
-You switch between Windows and Olares using the BIOS boot priority.
-### Switch to Olares OS
-1. Restart Olares One.
+You switch between Windows and beOS Pro using the BIOS boot priority.
+### Switch to beOS Pro
+1. Restart beOS Pro One.
2. Press the **Delete** key repeatedly to enter **BIOS setup**.
3. Go to the **Boot** tab.
4. Set **Boot Override** to Ubuntu.
5. Press **F10** to save and exit BIOS.
### Switch to Windows
-1. Restart Olares One.
+1. Restart beOS Pro One.
2. Press the **Delete** key repeatedly to enter **BIOS setup**.
3. Go to the **Boot** tab.
4. Set **Boot Override** to Windows.
@@ -142,7 +142,7 @@ You switch between Windows and Olares using the BIOS boot priority.
If an error occurs during installation, use the following command to uninstall first:
```bash
-olares-cli uninstall --all
+beos-cli uninstall --all
```
After uninstalling, retry the installation by running the original installation command.
@@ -150,7 +150,7 @@ After uninstalling, retry the installation by running the original installation
### The Ubuntu interface is lagging
When you first boot into the Ubuntu desktop, the interface might feel laggy. This is because the GPU drivers for Ubuntu are not yet installed.
-Proceed with the Olares OS installation. The installation script automatically installs the necessary GPU drivers, which will resolve the lag.
+Proceed with the beOS Pro installation. The installation script automatically installs the necessary GPU drivers, which will resolve the lag.
## Resources
diff --git a/docs/one/egpu.md b/docs/one/egpu.md
index 624b687fc..ac517519e 100644
--- a/docs/one/egpu.md
+++ b/docs/one/egpu.md
@@ -1,6 +1,6 @@
---
outline: [2,3]
-description: Learn how to expand your Olares One's graphical performance by connecting an external GPU (eGPU).
+description: Learn how to expand your beOS Pro One's graphical performance by connecting an external GPU (eGPU).
head:
- - meta
- name: keywords
@@ -8,14 +8,14 @@ head:
---
# Connect to an external graphics card (eGPU)
-Olares One supports connecting external graphics cards (eGPU) to boost performance for gaming, AI model training, etc.
+beOS Pro One supports connecting external graphics cards (eGPU) to boost performance for gaming, AI model training, etc.
:::danger Power off before connecting
Do not hot-swap the external GPU.
-Olares One does not support connecting or disconnecting the external GPU while the system is running. Doing so might cause system crashes, data loss, or hardware damage.
+beOS Pro One does not support connecting or disconnecting the external GPU while the system is running. Doing so might cause system crashes, data loss, or hardware damage.
-Always shut down Olares One completely before connecting or disconnecting the device.
+Always shut down beOS Pro One completely before connecting or disconnecting the device.
:::
## Prerequisites
@@ -30,22 +30,22 @@ The external GPU must be compatible with Linux (Ubuntu). Unsupported devices mig
## Step 1: Connect the eGPU
1. Open Settings, and select **My hardware** > **Shutdown**.
- 
+ 
-2. Scan the displayed QR code using the LarePass app. When the prompt appears in the app, tap **Confirm** to shut down Olares One.
-3. Once Olares One is fully powered off, plug the cable from your external GPU into the USB-C port on Olares One.
-4. Press the power button to turn on Olares One.
+2. Scan the displayed QR code using the beOS Pro app app. When the prompt appears in the app, tap **Confirm** to shut down beOS Pro One.
+3. Once beOS Pro One is fully powered off, plug the cable from your external GPU into the USB-C port on beOS Pro One.
+4. Press the power button to turn on beOS Pro One.
## Step 2: Verify connection
To verify that the external graphics card is recognized:
-1. Log in to Olares, and open Dashboard.
+1. Log in to beOS Pro, and open Dashboard.
2. Select the **GPU** card. You should see your external card listed alongside the internal GPU.
## Disconnect the eGPU
To safely remove the eGPU:
-1. Shut down Olares One completely using the steps above.
+1. Shut down beOS Pro One completely using the steps above.
2. Turn off the power to the external GPU.
-3. Unplug the USB-C cable from Olares One.
-4. Press the power button to turn on Olares One.
\ No newline at end of file
+3. Unplug the USB-C cable from beOS Pro One.
+4. Press the power button to turn on beOS Pro One.
\ No newline at end of file
diff --git a/docs/one/expand-storage-external-ssd.md b/docs/one/expand-storage-external-ssd.md
index 5b435f29b..a12121806 100644
--- a/docs/one/expand-storage-external-ssd.md
+++ b/docs/one/expand-storage-external-ssd.md
@@ -1,20 +1,20 @@
---
outline: [2, 3]
-description: Learn how to manually mount an external SSD to Olares One for temporary or permanent storage expansion.
+description: Learn how to manually mount an external SSD to beOS Pro One for temporary or permanent storage expansion.
head:
- - meta
- name: keywords
- content: Olares One, external SSD, expand storage
+ content: beOS Pro One, external SSD, expand storage
---
# Expand storage via external SSD
-You can manually mount high-capacity external SSDs to specific system paths on Olares One.
+You can manually mount high-capacity external SSDs to specific system paths on beOS Pro One.
This approach is recommended for long-term storage expansion, such as downloading more or larger local AI models.
:::warning HDD support
-This guide is intended for SSDs. Mechanical Hard Disk Drives (HDDs) have not been tested with Olares One.
+This guide is intended for SSDs. Mechanical Hard Disk Drives (HDDs) have not been tested with beOS Pro One.
:::
:::info Mount path
Currently, only mounts under the `/olares/share` directory are supported.
@@ -24,18 +24,18 @@ Mounting flexibility will be improved in future versions.
## Prerequisites
**Hardware**
-- Your Olares One is set up and running.
-- The external SSD is connected to Olares One.
+- Your beOS Pro One is set up and running.
+- The external SSD is connected to beOS Pro One.
**SSH access**
-- [SSH access to Olares One](access-terminal-ssh.md).
+- [SSH access to beOS Pro One](access-terminal-ssh.md).
**Experience**
- Basic familiarity with terminal commands and the command-line interface (CLI).
## Step 1: Identify the drive
-1. Connect to your Olares One terminal via SSH or from the Control Hub.
+1. Connect to your beOS Pro One terminal via SSH or from the Control Hub.
2. Run the following command to view detected drives:
@@ -156,6 +156,6 @@ To safely remove the drive or delete the mount point configuration:
```
## Resources
-- [Manage files in Olares](../manual/olares/files/index.md)
+- [Manage files in beOS Pro](../manual/olares/files/index.md)
- [Expand storage via USB devices](expand-storage-usb-drive.md)
- [Expand storage using internal SSD](expand-storage-internal-ssd.md)
\ No newline at end of file
diff --git a/docs/one/expand-storage-internal-ssd.md b/docs/one/expand-storage-internal-ssd.md
index b553d5dc3..18780dd31 100644
--- a/docs/one/expand-storage-internal-ssd.md
+++ b/docs/one/expand-storage-internal-ssd.md
@@ -1,15 +1,15 @@
---
outline: [2, 3]
-description: Learn how to expand storage on Olares One using an NVMe M.2 SSD.
+description: Learn how to expand storage on beOS Pro One using an NVMe M.2 SSD.
head:
- - meta
- name: keywords
- content: Olares One, NVMe SSD, expand storage, LVM, olares-cli
+ content: beOS Pro One, NVMe SSD, expand storage, LVM, beos-cli
---
# Expand storage with an NVMe M.2 SSD
-If you have installed a secondary internal NVMe SSD in your Olares One, you can merge it into the main system storage using the `olares-cli`.
+If you have installed a secondary internal NVMe SSD in your beOS Pro One, you can merge it into the main system storage using the `beos-cli`.
Unlike external drives which are mounted as separate folders, this method uses Logical Volume Management (LVM) to seamlessly extend your root file system.
@@ -17,10 +17,10 @@ Unlike external drives which are mounted as separate folders, this method uses L
## Before you begin
:::warning One-time irreversible operation
- This is a one-time operation. The SSD becomes an integral part of the system volume and cannot be easily separated later.
-- If you physically uninstall this SSD after extension, the Olares file system will be incomplete, causing the OS to crash or fail to boot. You will need to manually reinstall Olares OS.
+- If you physically uninstall this SSD after extension, the beOS Pro file system will be incomplete, causing the OS to crash or fail to boot. You will need to manually reinstall beOS Pro.
:::
-The Olares One motherboard includes two PCIe SSD slots:
+The beOS Pro One motherboard includes two PCIe SSD slots:
* Slot 1 (PCIe 4.0): Occupied by the preinstalled 2TB system SSD.
* Slot 2 (PCIe 5.0): Available for expansion.
@@ -28,18 +28,18 @@ You can use this second slot to expand your current system storage.
## Prerequisites
**Hardware**
-- Your Olares One is set up and running.
-- A secondary NVMe M.2 SSD is physically installed in Olares One.
+- Your beOS Pro One is set up and running.
+- A secondary NVMe M.2 SSD is physically installed in beOS Pro One.
**SSH access**
-- [SSH access to Olares One](access-terminal-ssh.md).
+- [SSH access to beOS Pro One](access-terminal-ssh.md).
**Experience**
- Basic familiarity with terminal commands and the command-line interface (CLI).
## Step 1: Identify the unmounted disk
-1. Connect to your Olares One terminal via SSH or from the Control Hub.
+1. Connect to your beOS Pro One terminal via SSH or from the Control Hub.
2. List block devices on the host:
@@ -62,16 +62,16 @@ In this example, `sda` is the system drive which is mounted at `/` and `/boot`,
## Step 2: Extend system storage
-1. Verify that Olares recognizes the unmounted disk:
+1. Verify that beOS Pro recognizes the unmounted disk:
```bash
- olares-cli disk list-unmounted
+ beos-cli disk list-unmounted
```
2. Run the extension command:
```bash
- olares-cli disk extend
+ beos-cli disk extend
```
3. When the command prompts for confirmation, type `YES` to proceed.
@@ -154,4 +154,4 @@ You should see your new disk (e.g., `nvme0n1`) listed under the `olares--vg-data
## Resources
- [Expand storage via USB devices](expand-storage-usb-drive.md)
- [Expand storage using external SSD](expand-storage-external-ssd.md)
-- [`olares-cli disk`](../developer/install/cli/disk.md).
\ No newline at end of file
+- [`beos-cli disk`](../developer/install/cli/disk.md).
\ No newline at end of file
diff --git a/docs/one/expand-storage-usb-drive.md b/docs/one/expand-storage-usb-drive.md
index 0f696205a..ab0b1833f 100644
--- a/docs/one/expand-storage-usb-drive.md
+++ b/docs/one/expand-storage-usb-drive.md
@@ -1,25 +1,25 @@
---
outline: [2, 3]
-description: Learn how to expand storage on Olares One using USB devices.
+description: Learn how to expand storage on beOS Pro One using USB devices.
head:
- - meta
- name: keywords
- content: Olares One, USB storage, expand storage, file management
+ content: beOS Pro One, USB storage, expand storage, file management
---
# Expand storage via USB devices
-Olares One automatically detects and mounts inserted USB storage devices, allowing you to instantly expand your storage capacity for media, backups, or file transfers.
+beOS Pro One automatically detects and mounts inserted USB storage devices, allowing you to instantly expand your storage capacity for media, backups, or file transfers.
## Prerequisites
**Hardware**
- A compatible USB flash drive.
:::warning Compatibility
- Olares One is tested with Samsung and SanDisk USB drives. Other brands might not be recognized by the system.
+ beOS Pro One is tested with Samsung and SanDisk USB drives. Other brands might not be recognized by the system.
:::
## Connect and access storage
-1. Insert your USB flash drive into an available USB port on Olares One. It will be mounted automatically.
+1. Insert your USB flash drive into an available USB port on beOS Pro One. It will be mounted automatically.
2. Open the Files app and select **External** in the sidebar to access your files.
## Safely remove the device
@@ -32,6 +32,6 @@ It is recommended to manually eject the device first:
3. Once the drive disappears from the list, you can safely unplug it.
## Resources
-- [Manage files in Olares](../manual/olares/files/index.md)
+- [Manage files in beOS Pro](../manual/olares/files/index.md)
- [Expand storage using external SSD](expand-storage-external-ssd)
- [Expand storage using internal SSD](expand-storage-internal-ssd.md)
\ No newline at end of file
diff --git a/docs/one/factory-reset-in-bios.md b/docs/one/factory-reset-in-bios.md
index 0e62a3ab5..fcf1dbe35 100644
--- a/docs/one/factory-reset-in-bios.md
+++ b/docs/one/factory-reset-in-bios.md
@@ -1,14 +1,14 @@
---
outline: [2, 3]
-description: Learn how to restore BIOS defaults on Olares One to return the device to its initial setup state.
+description: Learn how to restore BIOS defaults on beOS Pro One to return the device to its initial setup state.
head:
- - meta
- name: keywords
- content: Olares One, BIOS defaults, restore, BIOS setup
+ content: beOS Pro One, BIOS defaults, restore, BIOS setup
---
# Restore BIOS defaults
-Restoring BIOS defaults resets the firmware configuration and returns your Olares One to its initial setup state. If you have a monitor and keyboard connected, you can perform this directly in BIOS.
+Restoring BIOS defaults resets the firmware configuration and returns your beOS Pro One to its initial setup state. If you have a monitor and keyboard connected, you can perform this directly in BIOS.
:::warning Data loss
This will permanently delete all accounts, settings, and data on the device. This action cannot be undone.
@@ -16,13 +16,13 @@ This will permanently delete all accounts, settings, and data on the device. Thi
## Prerequisites
**Hardware**
-- A wired keyboard connected to your Olares One.
-- A monitor connected to your Olares One.
+- A wired keyboard connected to your beOS Pro One.
+- A monitor connected to your beOS Pro One.
## Step 1: Load optimized defaults in BIOS
-1. Power on Olares One or restart it if it is already running.
-2. When the Olares logo appears, immediately press the **Delete** key repeatedly to enter **BIOS setup**.
+1. Power on beOS Pro One or restart it if it is already running.
+2. When the beOS Pro logo appears, immediately press the **Delete** key repeatedly to enter **BIOS setup**.
3. Press **F9**, then select **Yes** to restore factory settings.
@@ -31,9 +31,9 @@ This will permanently delete all accounts, settings, and data on the device. Thi
4. Press **F10**, then select **Yes** to save and exit. The device restarts automatically.
-Once finished, Olares One reboots into the initial setup phase.
+Once finished, beOS Pro One reboots into the initial setup phase.
-## Step 2: Complete activation via LarePass
+## Step 2: Complete activation via beOS Pro app
-You can then activate Olares One again via LarePass. For detailed instructions, see [First boot](first-boot.md).
+You can then activate beOS Pro One again via beOS Pro app. For detailed instructions, see [First boot](first-boot.md).
diff --git a/docs/one/factory-reset.md b/docs/one/factory-reset.md
index 69580b105..2d1886a40 100644
--- a/docs/one/factory-reset.md
+++ b/docs/one/factory-reset.md
@@ -1,14 +1,14 @@
---
outline: [2, 3]
-description: Learn how to factory reset your Olares One using LarePass.
+description: Learn how to factory reset your beOS Pro One using beOS Pro app.
head:
- - meta
- name: keywords
- content: factory reset, Olares One, LarePass
+ content: factory reset, beOS Pro One, beOS Pro app
---
-# Factory reset via LarePass
+# Factory reset via beOS Pro app
-If you have already activated Olares One and want to return it to the factory state, you can perform a reset in LarePass.
+If you have already activated beOS Pro One and want to return it to the factory state, you can perform a reset in beOS Pro app.
:::warning Data loss
This will permanently delete all accounts, settings, and data on the device. This action cannot be undone.
@@ -17,24 +17,24 @@ This will permanently delete all accounts, settings, and data on the device. Thi
## Prerequisites
**Hardware**
-- Olares One is powered on.
-- Your phone and Olares One are on the same network.
-- You are signed in to LarePass as an administrator.
+- beOS Pro One is powered on.
+- Your phone and beOS Pro One are on the same network.
+- You are signed in to beOS Pro app as an administrator.
-## Reset Olares One to factory settings
+## Reset beOS Pro One to factory settings
-1. Open LarePass on your phone and go to **Settings**.
-2. In the **My Olares** card, tap **System** to open the **Olares management** page.
+1. Open beOS Pro app on your phone and go to **Settings**.
+2. In the **My beOS Pro** card, tap **System** to open the **beOS Pro management** page.
3. Tap **Restore to factory settings**.
4. Review the risk prompt carefully, then tap **Restore to factory settings** to continue.
-5. Enter your local LarePass lock-screen password and tap **Confirm**.
+5. Enter your local beOS Pro app lock-screen password and tap **Confirm**.
If you have not set a local password, you will be prompted to set one first.
6. Wait for the reset process to complete.
-Once finished, Olares One reboots into the initial setup phase. You are redirected to the activation flow, where you can scan the local network to reactivate Olares.
+Once finished, beOS Pro One reboots into the initial setup phase. You are redirected to the activation flow, where you can scan the local network to reactivate beOS Pro.
For detailed instructions, see [First boot](first-boot.md).
\ No newline at end of file
diff --git a/docs/one/faq.md b/docs/one/faq.md
index 454171266..863f30f1f 100644
--- a/docs/one/faq.md
+++ b/docs/one/faq.md
@@ -1,36 +1,36 @@
---
outline: [2,3]
-description: Frequently asked questions regarding Olares One
+description: Frequently asked questions regarding beOS Pro One
head:
- - meta
- name: keywords
- content: Olares One, Olares, personal cloud
+ content: beOS Pro One, beOS Pro, personal cloud
---
-# Olares One FAQs
-This page lists frequently asked questions from the Olares community regarding Olares One and system capabilities.
+# beOS Pro One FAQs
+This page lists frequently asked questions from the beOS Pro community regarding beOS Pro One and system capabilities.
-:::tip Support for Olares One owners
-If you require assistance with product features, hardware warranty, or a specific use case, contact technical support directly via WhatsApp or email at hi@olares.com. We respond to inquiries within two business days.
+:::tip Support for beOS Pro One owners
+If you require assistance with product features, hardware warranty, or a specific use case, contact technical support directly via WhatsApp or email at hi@beos.local. We respond to inquiries within two business days.
:::
## Product & spec
-### What is Olares One?
-Olares One is a dedicated personal cloud device designed for local AI. It integrates workstation-grade hardware with Olares OS, an open-source operating system that allows you to run AI agents and store data on hardware you physically control.
+### What is beOS Pro One?
+beOS Pro One is a dedicated personal cloud device designed for local AI. It integrates workstation-grade hardware with beOS Pro, an open-source operating system that allows you to run AI agents and store data on hardware you physically control.
### What is personal cloud?
A personal cloud is a private infrastructure that replicates the utility of public cloud services such as anywhere-access to files and computing power but runs entirely on your own hardware to ensure data sovereignty.
-### What are the technical specifications for Olares One?
+### What are the technical specifications for beOS Pro One?
* **Processor**: Intel Ultra 9 275HX
* **GPU**: NVIDIA RTX 5090 Mobile
* **Memory**: 96GB RAM
* **Storage**: 2TB NVMe SSD
-For details, see [Olares One specifications](spec).
+For details, see [beOS Pro One specifications](spec).
### How loud is the device?
-Olares One is designed to operate quietly even under load. In lab testing, the device generates 19dB when idle and remains under 39dB under maximum load.
+beOS Pro One is designed to operate quietly even under load. In lab testing, the device generates 19dB when idle and remains under 39dB under maximum load.
### What is the power consumption?
The device consumes 30W in standby. Under load, the GPU power depends on your selected mode:
@@ -48,14 +48,14 @@ The device includes the following physical ports:
* 1 × USB-A 3.2 Gen2 with 10 Gbps speed
* 1 × HDMI 2.1 with 48 Gbps bandwidth
-### How is Olares One different from DGX Spark, AI Max+ 395 and other AI PCs?
-Olares One is a personal cloud solution rather than a traditional personal computer.
+### How is beOS Pro One different from DGX Spark, AI Max+ 395 and other AI PCs?
+beOS Pro One is a personal cloud solution rather than a traditional personal computer.
A personal cloud runs as a stable, external service accessible anytime from any device, whereas a PC is client-based software designed for direct interaction via monitor and keyboard.
-Specifically, Olares One utilizes the NVIDIA CUDA stack on x86 architecture. This ensures broad compatibility with standard open-source AI applications, avoiding the adaptation challenges often found in ARM-based AI PCs or devices without CUDA support.
+Specifically, beOS Pro One utilizes the NVIDIA CUDA stack on x86 architecture. This ensures broad compatibility with standard open-source AI applications, avoiding the adaptation challenges often found in ARM-based AI PCs or devices without CUDA support.
-And Olares OS simplifies local AI with one-click deployment and workflow integration, distinct from the manual software management typical of standard PCs.
+And beOS Pro simplifies local AI with one-click deployment and workflow integration, distinct from the manual software management typical of standard PCs.
### Can I upgrade or expand the hardware?
Yes. You can modify the hardware through several internal slots and expansion ports:
@@ -63,7 +63,7 @@ Yes. You can modify the hardware through several internal slots and expansion po
* **Memory**: The RAM capacity can be upgraded to a maximum of 128GB.
* **External graphics & displays**: The Thunderbolt 5 port supports eGPU enclosures for connecting external graphics cards. It also supports docking stations to connect up to two external monitors simultaneously (up to 8K resolution), with video output handled by the RTX 5090 Mobile.
-### Is there a way to view the Olares OS UI via HDMI?
+### Is there a way to view the beOS Pro UI via HDMI?
Currently, the HDMI output does not display a full desktop UI like a traditional PC. The HDMI port currently displays an Ubuntu shell or Steam Headless output for gaming.
Future updates target the ability to run a lightweight browser or ChromeOS instance directly via HDMI, allowing users to interact with the system using a monitor, keyboard, and mouse.
@@ -71,19 +71,19 @@ Future updates target the ability to run a lightweight browser or ChromeOS insta
### Can I update or configure the BIOS?
Yes. Users can update the BIOS themselves as new versions are released. All BIOS options are fully unlocked, allowing users to configure settings according to their own needs.
-### Is Olares One designed for "always-on" operation?
-Yes. Olares One is positioned as a personal AI cloud and is capable of supporting 24/7 continuous operation reliably. It is designed to support scenarios like LLM hosting.
+### Is beOS Pro One designed for "always-on" operation?
+Yes. beOS Pro One is positioned as a personal AI cloud and is capable of supporting 24/7 continuous operation reliably. It is designed to support scenarios like LLM hosting.
-### Are there additional fees to use Olares One?
-No. Olares OS and all future system updates are completely free.
+### Are there additional fees to use beOS Pro One?
+No. beOS Pro and all future system updates are completely free.
### Can I use the device without an internet connection?
Yes. After a one-time activation, the device can work entirely offline. You can access it via your local network without any internet connection required.
### Does the device have failsafes for power outages?
-Olares One uses the ext4 Linux file system to prevent file system corruption during sudden power loss. Hardware protection is managed through the power supply and motherboard design, which includes voltage regulation.
+beOS Pro One uses the ext4 Linux file system to prevent file system corruption during sudden power loss. Hardware protection is managed through the power supply and motherboard design, which includes voltage regulation.
-Olares OS also includes a built-in automatic backup mechanism for periodic, encrypted backups to external locations.
+beOS Pro also includes a built-in automatic backup mechanism for periodic, encrypted backups to external locations.
Looking ahead, we are working on the following improvements:
@@ -91,44 +91,44 @@ Looking ahead, we are working on the following improvements:
2. Native support for Time Machine-style snapshot backups.
### Does the device support a GPU MUX switch?
-Yes. Olares One supports both GPU MUX and Optimus modes. The system is set to GPU MUX mode by default to enable a direct connection to the discrete GPU, but this can be changed in the BIOS.
+Yes. beOS Pro One supports both GPU MUX and Optimus modes. The system is set to GPU MUX mode by default to enable a direct connection to the discrete GPU, but this can be changed in the BIOS.
## AI & gaming
-### Can I run Kimi K2 on Olares One?
-Kimi K2 has around 1 trillion parameters and requires approximately 1024 GB of VRAM, so we haven't made it available in the Olares Market yet.
+### Can I run Kimi K2 on beOS Pro One?
+Kimi K2 has around 1 trillion parameters and requires approximately 1024 GB of VRAM, so we haven't made it available in the beOS Pro Market yet.
-However, given that AI model sizes have been shrinking roughly tenfold each year, there is a good chance that a Kimi‑K2–level model could run on Olares One by mid‑2026.
+However, given that AI model sizes have been shrinking roughly tenfold each year, there is a good chance that a Kimi‑K2–level model could run on beOS Pro One by mid‑2026.
### Can local AI models access the internet for research?
Yes. We support several applications that enable this. For example:
* **Perplexica**: An open‑source alternative to Perplexity. It retrieves the latest information using SearxNG and analyzes it with a local LLM.
* **DeerFlow**: An open‑source alternative to OpenResearch. It uses RAGFlow to configure a local knowledge base, integrates Tavily for web search, and performs analysis using a local LLM.
-### Can I use a NAS for storage and use Olares for AI processing?
-Yes, we highly recommend this workflow. You can mount your NAS to Olares One as an SMB share. Olares can then index, sort, and process the photos and videos stored on the NAS via apps like Immich.
+### Can I use a NAS for storage and use beOS Pro for AI processing?
+Yes, we highly recommend this workflow. You can mount your NAS to beOS Pro One as an SMB share. beOS Pro can then index, sort, and process the photos and videos stored on the NAS via apps like Immich.
-### Can I use Olares AI features on my iPhone or Mac?
-Yes. Olares supports secure remote access. You can use your iPhone or Mac to query the AI models running on your Olares One from anywhere.
+### Can I use beOS Pro AI features on my iPhone or Mac?
+Yes. beOS Pro supports secure remote access. You can use your iPhone or Mac to query the AI models running on your beOS Pro One from anywhere.
-### How does the 120B model run on Olares One and how fast is it?
+### How does the 120B model run on beOS Pro One and how fast is it?
We tested the `gpt-oss:120b` model. Since the model size exceeds the dedicated GPU memory, part of the model is loaded into the 96GB of system memory and processed by the CPU.
In our testing, `gpt-oss:120b` achieves approximately 36.16 tokens/s.
For better efficiency, we recommend `qwen3-30b-a3b`. It delivers superior results while being significantly smaller, reaching speeds of up to 157 tokens/s, or around 81 tokens/s with 8 concurrent requests.
-For the detailed testing methodology, Refer to https://blog.olares.com/local-ai-hardware-performance-benchmarking/.
+For the detailed testing methodology, Refer to https://blog.beos.local/local-ai-hardware-performance-benchmarking/.
-### Can I use LM Studio to manage models on Olares?
-LM Studio is designed as a client-side desktop application rather than a server-side service, so it cannot be installed directly on Olares One.
+### Can I use LM Studio to manage models on beOS Pro?
+LM Studio is designed as a client-side desktop application rather than a server-side service, so it cannot be installed directly on beOS Pro One.
However, you have two alternatives:
* Use native apps like OpenWebUI or LobeChat, which offer similar functionality.
-* Run a local instance of LM Studio on your computer and configure it to access the AI models hosted on Olares One via API.
+* Run a local instance of LM Studio on your computer and configure it to access the AI models hosted on beOS Pro One via API.
### Will performance drop if I load multiple models at once?
-Under normal circumstances, loading multiple models that exceed GPU memory would cause a crash. Olares addresses this with a time-slicing mechanism.
+Under normal circumstances, loading multiple models that exceed GPU memory would cause a crash. beOS Pro addresses this with a time-slicing mechanism.
Models not actively in use are temporarily swapped to the 96GB system memory, while the active model is loaded into the GPU. This allows you to keep multiple models "ready" with only about a 5% performance overhead during switching.
@@ -136,48 +136,48 @@ Alternatively, you can:
- Split the GPU memory so multiple apps run simultaneously without swapping.
- Assign the entire GPU to a single application for maximum raw performance.
-All these modes can be switched directly from Olares Settings. No other modifications are required.
+All these modes can be switched directly from beOS Pro Settings. No other modifications are required.
### Is the device capable of high-end gaming?
Yes. You can connect a monitor to play directly via Steam, or use it as a game server to stream titles to your laptop, TV, or phone via Moonlight.
-### Can I use Olares One for VR devices such as Quest 3?
+### Can I use beOS Pro One for VR devices such as Quest 3?
We expect to begin broad testing with VR and AR devices in early 2026.
### How does gaming performance compare to Windows?
-Olares One supports gaming in two ways: streaming as a Steam server via Moonlight, or playing directly by connecting a monitor.
+beOS Pro One supports gaming in two ways: streaming as a Steam server via Moonlight, or playing directly by connecting a monitor.
In direct play scenarios, our data shows Cyberpunk 2077 achieving approximately 90% of the performance of the same hardware running Windows. This is comparable to other high-end Linux gaming setups. We expect compatibility to improve further as SteamOS adoption grows.
## Operating system
-### Can I run Windows on Olares One?
-Yes. For users who only need to run occasional Windows applications, we recommend installing the Windows app from the Olares Market. This runs a virtual machine accessible via RDP, which provides a seamless remote desktop experience when used with the built-in VPN.
+### Can I run Windows on beOS Pro One?
+Yes. For users who only need to run occasional Windows applications, we recommend installing the Windows app from the beOS Pro Market. This runs a virtual machine accessible via RDP, which provides a seamless remote desktop experience when used with the built-in VPN.
-Alternatively, you can install a second internal drive for a dual-boot setup or completely replace Olares OS with a native Windows installation.
+Alternatively, you can install a second internal drive for a dual-boot setup or completely replace beOS Pro with a native Windows installation.
### Can the Windows VM use the GPU?
-Currently, GPU passthrough is not supported. The NVIDIA RTX 5090 Mobile functions as the primary GPU for Olares OS to power local AI applications. Assigning it to a virtual machine would detach it from the host OS, disabling these features.
+Currently, GPU passthrough is not supported. The NVIDIA RTX 5090 Mobile functions as the primary GPU for beOS Pro to power local AI applications. Assigning it to a virtual machine would detach it from the host OS, disabling these features.
Windows VMs utilize the integrated Intel graphics, which handle lightweight tasks effectively. For GPU-intensive workloads like gaming, we recommend setting up a dual-boot configuration.
-### Can I wipe Olares OS and install Linux or Windows natively?
-Yes. You have full ownership of the hardware. You can wipe the pre-installed OS to install Windows or any Linux distribution. In this configuration, Olares One functions as a standard high-performance workstation equipped with an NVIDIA RTX 5090 Mobile GPU, allowing you to use a monitor, keyboard, and mouse like a standard desktop computer.
+### Can I wipe beOS Pro and install Linux or Windows natively?
+Yes. You have full ownership of the hardware. You can wipe the pre-installed OS to install Windows or any Linux distribution. In this configuration, beOS Pro One functions as a standard high-performance workstation equipped with an NVIDIA RTX 5090 Mobile GPU, allowing you to use a monitor, keyboard, and mouse like a standard desktop computer.
### How do I set up a dual-boot system?
We recommend installing a second NVMe SSD in the available slot to keep the operating systems on separate drives.
-For a clean installation, install Windows first, followed by Olares OS.
+For a clean installation, install Windows first, followed by beOS Pro.
-Since Olares OS is based on Ubuntu 24.04, it follows standard Linux dual-boot procedures.
+Since beOS Pro is based on Ubuntu 24.04, it follows standard Linux dual-boot procedures.
-### Can I set Olares OS as the default boot option but switch to Windows when needed?
-Yes. Both the UEFI Boot Manager and GRUB support this configuration. You can set Olares OS as the persistent default boot option in the BIOS. To boot into Windows for specific tasks like gaming, you can select the Windows Boot Manager during the startup sequence.
+### Can I set beOS Pro as the default boot option but switch to Windows when needed?
+Yes. Both the UEFI Boot Manager and GRUB support this configuration. You can set beOS Pro as the persistent default boot option in the BIOS. To boot into Windows for specific tasks like gaming, you can select the Windows Boot Manager during the startup sequence.
## Clustering
-### Can I connect two Olares One units together?
-Yes. Olares OS is built on Kubernetes, which allows multiple Olares devices to form a cluster. Applications are automatically scheduled within the cluster, and models can be loaded across multiple devices.
+### Can I connect two beOS Pro One units together?
+Yes. beOS Pro is built on Kubernetes, which allows multiple beOS Pro devices to form a cluster. Applications are automatically scheduled within the cluster, and models can be loaded across multiple devices.
Forming a cluster currently requires command-line operations. We expect to introduce a fully UI‑based experience to manage this process in future updates.
@@ -197,25 +197,25 @@ It also enables complex pipelines. For example, you can run a digital human appl
Yes. The total available memory capacity roughly doubles when connecting two identical units. The system distributes different applications across nodes to maximize the available resources.
### Can I cluster with third-party devices like Mac Studio or DGX Spark?
-Currently, Olares only supports clustering devices with the same architecture running the same OS.
+Currently, beOS Pro only supports clustering devices with the same architecture running the same OS.
Support for third-party devices is in development. We target initial clustering compatibility for Mac Studio, DGX Spark, and AI MAX 395+ in future updates.
### Can I use a NAS as part of the cluster?
-No. Most NAS operating systems are closed environments and cannot run Olares nodes.
+No. Most NAS operating systems are closed environments and cannot run beOS Pro nodes.
-However, Olares One can mount NAS directories via the SMB protocol. This allows you to manage files on your NAS as if they were local folders on the Olares One.
+However, beOS Pro One can mount NAS directories via the SMB protocol. This allows you to manage files on your NAS as if they were local folders on the beOS Pro One.
### How does GPU scheduling work in a cluster?
-Olares OS manages GPU allocation at the operating system level. Ideally, we categorize GPU scheduling into four stages of complexity:
+beOS Pro manages GPU allocation at the operating system level. Ideally, we categorize GPU scheduling into four stages of complexity:
1. Single node, single GPU.
2. Single node, multiple GPUs.
3. Multiple nodes, multiple GPUs (same architecture).
4. Multiple nodes, multiple GPUs (different architectures).
-Olares currently operates at Stage 3. We can cluster multiple devices running the same OS and architecture (e.g., multiple Olares One units).
+beOS Pro currently operates at Stage 3. We can cluster multiple devices running the same OS and architecture (e.g., multiple beOS Pro One units).
-Stage 4, such as clustering Olares One and Mac devices together, is not yet fully automated. Currently, this setup requires manual intervention, such as pulling the specific container images for the corresponding architecture yourself. We are expect to rewrite our scheduling algorithm to automate this support in the near future.
+Stage 4, such as clustering beOS Pro One and Mac devices together, is not yet fully automated. Currently, this setup requires manual intervention, such as pulling the specific container images for the corresponding architecture yourself. We are expect to rewrite our scheduling algorithm to automate this support in the near future.
### Is federated learning or shared compute supported?
@@ -227,15 +227,15 @@ While feasible given the hardware's VRAM and power profile, delivering a product
We understand that 10Gbps is preferred for clustering to maximize data transfer between nodes. However, the inclusion of a 2.5Gbps Ethernet port is a strict limitation imposed by the hardware platform vendor.
## Advanced usage and configuration
-### Does Olares support multiple users with their own accounts?
-Yes. Olares is a multi‑user system. You can create separate accounts for friends or family, and they can connect using their own LaresPass.
+### Does beOS Pro support multiple users with their own accounts?
+Yes. beOS Pro is a multi‑user system. You can create separate accounts for friends or family, and they can connect using their own LaresPass.
The system currently supports three account roles:
* **Super Admin**: The user who initially activates the system and manages admins.
* **Admin**: Can perform cluster‑level tasks.
* **Member**: Standard access to shared services.
-### Can I host a mail server on Olares One?
+### Can I host a mail server on beOS Pro One?
Hosting a mail server is technically possible but complex.
We support open‑source solutions like Mail‑in‑a‑Box, Mailserver, and Mailcow. However, self‑hosted email servers are often flagged as spam by major providers, which makes reliable delivery difficult.
@@ -243,24 +243,24 @@ We support open‑source solutions like Mail‑in‑a‑Box, Mailserver, and Mai
### Is it possible to install a VPN for outbound traffic?
We have built‑in support for Tailscale and Headscale. This allows you to configure and use a specific exit node for your outbound traffic.
-### Do I need a static IP to host Olares One as a server?
+### Do I need a static IP to host beOS Pro One as a server?
No. A static IP address is not required. We provide two external access options: reverse proxy and VPN. These solutions allow you to securely access your device from anywhere without needing a static IP.
-### Can I use my own domain to access Olares One?
-Yes. You can host Olares One using your own domain name.
+### Can I use my own domain to access beOS Pro One?
+Yes. You can host beOS Pro One using your own domain name.
-Currently, you must point the NS records of your subdomain to Olares' name servers so we can set up the reverse proxy for you. We are working on an update for users who wish to manage their own reverse proxy or do not require public internet access.
+Currently, you must point the NS records of your subdomain to beOS Pro' name servers so we can set up the reverse proxy for you. We are working on an update for users who wish to manage their own reverse proxy or do not require public internet access.
### Is there a way to access the device without the internet?
Yes. We provide a fully local access option using a `.local` domain.
If the device is on a LAN but blocked from public access, you can use the `.local` domain to access all features normally. If the device has zero internet connectivity, features relying on external services (like the App Market) will be unavailable.
-### Can Olares One function as a media server?
-Yes. Olares One can function as a Plex server. It supports hardware-accelerated transcoding, utilizing both the CPU and GPU for efficient decoding.
+### Can beOS Pro One function as a media server?
+Yes. beOS Pro One can function as a Plex server. It supports hardware-accelerated transcoding, utilizing both the CPU and GPU for efficient decoding.
### Can I use SMB to sync or back up files to a NAS?
-Yes. Olares One supports SMB sharing, allowing you to sync files with or back up data to an external NAS.
+Yes. beOS Pro One supports SMB sharing, allowing you to sync files with or back up data to an external NAS.
### Is the filesystem encrypted?
By default, the system does not use full-disk encryption. We are working to make this a standard, user-configurable option in the near future.
\ No newline at end of file
diff --git a/docs/one/files.md b/docs/one/files.md
index 88834b7e6..6d45ff92f 100644
--- a/docs/one/files.md
+++ b/docs/one/files.md
@@ -1,15 +1,15 @@
---
outline: [2, 3]
-description: Get started with the Files app on your Olares One. Learn the interface layout, how to upload your first files, preview and edit content, search your drive, and connect external cloud storage like Google Drive.
+description: Get started with the Files app on your beOS Pro One. Learn the interface layout, how to upload your first files, preview and edit content, search your drive, and connect external cloud storage like Google Drive.
head:
- - meta
- name: keywords
- content: Olares, Olares One, upload files, manage files, access cloud files, Olares Files app
+ content: beOS Pro, beOS Pro One, upload files, manage files, access cloud files, beOS Pro Files app
---
# Manage files
-Olares's built-in Files app provides a secure and efficient solution for file storage and synchronization. It allows you to access your personal files anywhere, keep data synchronized across devices, and manage third-party cloud storage in one place.
+beOS Pro's built-in Files app provides a secure and efficient solution for file storage and synchronization. It allows you to access your personal files anywhere, keep data synchronized across devices, and manage third-party cloud storage in one place.
Operations in Files are essentially the same as in other file managers. This guide introduces some common tasks in Files to get you started.
@@ -72,7 +72,7 @@ Populate your server with content by uploading documents via the Files app.
:::info Resumable uploads
-If your internet connection drops, the upload stops automatically. When the connection is back, Olares resumes the upload from exactly where it left off, so you don't have to start over.
+If your internet connection drops, the upload stops automatically. When the connection is back, beOS Pro resumes the upload from exactly where it left off, so you don't have to start over.
:::
## Preview & edit files
@@ -122,7 +122,7 @@ Download files to your local computer.
The file is downloaded via your web browser's standard download manager.
:::info
-Web browsers cannot download entire folders or extremely large files reliably. For these tasks, install the LarePass Desktop application to unlock folder downloads and resume capabilities.
+Web browsers cannot download entire folders or extremely large files reliably. For these tasks, install the beOS Pro app Desktop application to unlock folder downloads and resume capabilities.
:::
## Delete files
@@ -136,14 +136,14 @@ Deleted files cannot be recovered.
3. In the **Delete** window, click **Confirm**.
-For instructions on how to SSH into Olares One, see [Connect to Olares One via SSH](access-terminal-ssh.md).
+For instructions on how to SSH into beOS Pro One, see [Connect to beOS Pro One via SSH](access-terminal-ssh.md).
-### Access Olares services securely
-For secure remote access without complex network configuration, it is recommended to enable the LarePass VPN.
+### Access beOS Pro services securely
+For secure remote access without complex network configuration, it is recommended to enable the beOS Pro app VPN.
-See [Access Olares services securely using LarePass VPN](access-olares-via-vpn.md).
+See [Access beOS Pro services securely using beOS Pro app VPN](access-olares-via-vpn.md).
### Explore
-Olares OS comes with pre-installed system apps. You can also browse the **Market** to download additional applications that best suit your needs.
+beOS Pro comes with pre-installed system apps. You can also browse the **Market** to download additional applications that best suit your needs.
You can continue browsing this documentation to discover more use cases and advanced configuration scenarios.
## FAQs
-### Why is an Olares ID required?
+### Why is an beOS ID required?
-The Olares ID is currently required to automate secure remote access for your device. It allows the system to configure a reverse proxy, register a subdomain, and manage HTTPS certificates on your behalf. Without this, you would need to manually handle complex network configurations such as port forwarding and DNS management to access your device from outside your home.
+The beOS ID is currently required to automate secure remote access for your device. It allows the system to configure a reverse proxy, register a subdomain, and manage HTTPS certificates on your behalf. Without this, you would need to manually handle complex network configurations such as port forwarding and DNS management to access your device from outside your home.
-Unlike a centralized cloud account, the Olares ID is owned entirely by you. We never see your credentials, and we cannot recover your data if you lose your mnemonic phrase.
+Unlike a centralized cloud account, the beOS ID is owned entirely by you. We never see your credentials, and we cannot recover your data if you lose your mnemonic phrase.
-We understand the community's preference for flexibility. In the upcoming March update, we plan to introduce new activation options that will make the Olares ID optional if you prefer to configure your own network access.
+We understand the community's preference for flexibility. In the upcoming March update, we plan to introduce new activation options that will make the beOS ID optional if you prefer to configure your own network access.
### Can I use my own domain name?
-Yes. You can use your own custom domain instead of the default `olares.com` domain. Note that setting this up currently requires the LarePass app.
+Yes. You can use your own custom domain instead of the default `beos.local` domain. Note that setting this up currently requires the beOS Pro app app.
-For details, refer to [Set up a custom domain for your Olares](../manual/best-practices/set-custom-domain.md).
+For details, refer to [Set up a custom domain for your beOS Pro](../manual/best-practices/set-custom-domain.md).
## Resources
-- [Access Olares using local network](access-olares-via-vpn.md)
-- [Olares ID](../developer/concepts/olares-id.md)
+- [Access beOS Pro using local network](access-olares-via-vpn.md)
+- [beOS ID](../developer/concepts/beos-id.md)
- [Back up mnemonic phrase](../manual/larepass/back-up-mnemonics.md)
\ No newline at end of file
diff --git a/docs/one/gpu.md b/docs/one/gpu.md
index 71e46bf6f..e3e640ecd 100644
--- a/docs/one/gpu.md
+++ b/docs/one/gpu.md
@@ -1,6 +1,6 @@
---
outline: [2, 3]
-description: Learn about the three GPU modes in Olares and how to switch between them to match different workloads.
+description: Learn about the three GPU modes in beOS Pro and how to switch between them to match different workloads.
head:
- - meta
- name: keywords
@@ -9,10 +9,10 @@ head:
# Switch GPU mode
:::info
-Only Olares admins can change GPU modes. This helps avoid conflicts and keeps GPU performance predictable for everyone.
+Only beOS Pro admins can change GPU modes. This helps avoid conflicts and keeps GPU performance predictable for everyone.
:::
-Olares lets you control how applications use GPU resources for workloads like AI, image and video generation, and gaming. You can choose different GPU modes depending on how your apps should share compute and memory.
+beOS Pro lets you control how applications use GPU resources for workloads like AI, image and video generation, and gaming. You can choose different GPU modes depending on how your apps should share compute and memory.
## Learning objectives
@@ -24,7 +24,7 @@ By the end of this tutorial, you will learn how to:
## Choose the right GPU mode
-Olares provides three GPU modes, each designed for a different usage pattern.
+beOS Pro provides three GPU modes, each designed for a different usage pattern.
| GPU mode | Definition | Use scenario |
|:---------------------------|:----------------------------------------------------------------------------------------------------|:----------------------------------------------------------------------------------|
@@ -39,7 +39,7 @@ Go to **Settings** > **GPU** to view your GPU status and current mode.
{width=85%}
:::tip
-If you have more than one GPU, Olares lists all your GPUs on this page. Just click a GPU to open its details page directly.
+If you have more than one GPU, beOS Pro lists all your GPUs on this page. Just click a GPU to open its details page directly.
:::
## Switch GPU mode
@@ -55,7 +55,7 @@ Changing a GPU's mode restarts applications currently using that GPU.
### Time slicing
-**Time slicing** is the default mode in Olares. Use this mode to allow multiple applications to share resources.
+**Time slicing** is the default mode in beOS Pro. Use this mode to allow multiple applications to share resources.
When a GPU is in **Time slicing** mode, GPU-enabled applications are automatically assigned to it. These applications will appear in the app list on this page.
diff --git a/docs/one/index.md b/docs/one/index.md
index 4a354c713..9304f2f9d 100644
--- a/docs/one/index.md
+++ b/docs/one/index.md
@@ -1,35 +1,35 @@
---
-description: A brief introduction to Olares One and its integration with Olares OS for local AI processing.
+description: A brief introduction to beOS Pro One and its integration with beOS Pro for local AI processing.
head:
- - meta
- name: keywords
- content: Olares One, Olares, personal AI cloud, local AI, edge computing, data privacy
+ content: beOS Pro One, beOS Pro, personal AI cloud, local AI, edge computing, data privacy
---
-# Olares One documentation
+# beOS Pro One documentation
-Welcome to Olares One! This documentation helps you navigate the journey with Olares One, from your first boot to everyday use, and advanced system customization.
+Welcome to beOS Pro One! This documentation helps you navigate the journey with beOS Pro One, from your first boot to everyday use, and advanced system customization.
:::info
-This documentation focuses on usage scenarios specific to Olares One. For general operating system features or broader use cases, select the **Olares OS** or **Use cases** tabs in the top navigation.
+This documentation focuses on usage scenarios specific to beOS Pro One. For general operating system features or broader use cases, select the **beOS Pro** or **Use cases** tabs in the top navigation.
:::
-## What is Olares One?
-Olares One is a dedicated hardware device designed to run a personal AI cloud. It combines workstation-grade hardware with Olares OS to provide a platform for running AI tools and managing data locally.
+## What is beOS Pro One?
+beOS Pro One is a dedicated hardware device designed to run a personal AI cloud. It combines workstation-grade hardware with beOS Pro to provide a platform for running AI tools and managing data locally.
-Modern digital life often trades privacy for convenience by sending personal data and AI prompts to centralized servers. Olares One replaces this model with hardware you physically control, which allows for local data processing for AI agents and file storage.
+Modern digital life often trades privacy for convenience by sending personal data and AI prompts to centralized servers. beOS Pro One replaces this model with hardware you physically control, which allows for local data processing for AI agents and file storage.
Primary use cases include:
* **Edge AI**: Run open-source AI models for text or media generation directly on the hardware with complete data privacy.
-* **Gaming**: Turn the device into a gaming server with the Steam Headless app to play titles on Olares One, or on any compatible devices.
+* **Gaming**: Turn the device into a gaming server with the Steam Headless app to play titles on beOS Pro One, or on any compatible devices.
* **Personal knowledge base**: Allow AI models to learn from private documents to function as a personal assistant.
* **Unified file storage**: Use the Files app to manage, sync, and share files.
* **Self-hosted workspace**: Run a private suite of productivity and collaboration tools on the local device.
-* **App development**: Use Olares Studio to develop and deploy applications for the Olares environment.
+* **App development**: Use beOS Pro Studio to develop and deploy applications for the beOS Pro environment.
* **Private media server**: Host and stream movie and music collections using apps like Jellyfin.
-## What is Olares OS?
-Olares is an open-source personal cloud operating system based on Kubernetes designed to empower users to own and manage their digital assets locally.
+## What is beOS Pro?
+beOS Pro is an open-source personal cloud operating system based on Kubernetes designed to empower users to own and manage their digital assets locally.
-While Olares One includes the software by default, Olares OS is also available for installation on other hardware. For details, see [Install Olares](../manual/get-started/install-olares.md).
\ No newline at end of file
+While beOS Pro One includes the software by default, beOS Pro is also available for installation on other hardware. For details, see [Install beOS Pro](../manual/get-started/install-olares.md).
\ No newline at end of file
diff --git a/docs/one/install-nvidia-driver.md b/docs/one/install-nvidia-driver.md
index 43f83f5d6..a271b424c 100644
--- a/docs/one/install-nvidia-driver.md
+++ b/docs/one/install-nvidia-driver.md
@@ -1,15 +1,15 @@
---
outline: [2, 3]
-description: Learn how to download and use the all-in-one driver package provided by Olares to install all necessary Windows drivers, including the NVIDIA graphics driver.
+description: Learn how to download and use the all-in-one driver package provided by beOS Pro to install all necessary Windows drivers, including the NVIDIA graphics driver.
head:
- - meta
- name: keywords
- content: Olares, Olares One, Windows drivers, NVIDIA graphics driver, GPU
+ content: beOS Pro, beOS Pro One, Windows drivers, NVIDIA graphics driver, GPU
---
# Install drivers on Windows
-To ensure optimal performance and system stability when running Windows on your Olares One, Olares provides a tested all-in-one driver package. This package contains all the necessary drivers for your device, such as audio, network, and NVIDIA graphics drivers.
+To ensure optimal performance and system stability when running Windows on your beOS Pro One, beOS Pro provides a tested all-in-one driver package. This package contains all the necessary drivers for your device, such as audio, network, and NVIDIA graphics drivers.
This guide walks you through downloading and installing the all-in-one driver package.
@@ -20,7 +20,7 @@ This guide walks you through downloading and installing the all-in-one driver pa
## Before you begin
:::info About NVIDIA graphics driver update
-This all-in-one package includes a stable, fully tested NVIDIA graphics driver specifically optimized for Olares One. To ensure system stability, avoid downloading and installing standalone graphics drivers directly from the official NVIDIA website, because that might introduce compatibility issues.
+This all-in-one package includes a stable, fully tested NVIDIA graphics driver specifically optimized for beOS Pro One. To ensure system stability, avoid downloading and installing standalone graphics drivers directly from the official NVIDIA website, because that might introduce compatibility issues.
:::
- **Administrator access**: You need admin rights to install system drivers.
@@ -30,7 +30,7 @@ This all-in-one package includes a stable, fully tested NVIDIA graphics driver s
## Step 1: Download and extract the driver package
-1. Download the [driver package](http://cdn.olares.com/common/AGBOX_B1_DVT_driver251125.zip).
+1. Download the [driver package](http://cdn.beos.local/common/AGBOX_B1_DVT_driver251125.zip).
:::tip Browser security warning
Because the download links use a standard HTTP connection rather than HTTPS, your web browser might flag or block it as an insecure download. If this happens, select **Keep** or **Allow** in your browser's download manager to continue the download.
diff --git a/docs/one/known-issues.md b/docs/one/known-issues.md
index 5308ab6ac..2bb693cfb 100644
--- a/docs/one/known-issues.md
+++ b/docs/one/known-issues.md
@@ -1,14 +1,14 @@
---
-description: This page documents the known issues and unexpected behaviors you might encounter when using Olares One, along with their corresponding solutions or workarounds.
+description: This page documents the known issues and unexpected behaviors you might encounter when using beOS Pro One, along with their corresponding solutions or workarounds.
---
# Known issues
-Use this page to identify and troubleshoot currently known issues with your Olares One device. We regularly update this list with temporary workarounds and permanent fixes as they become available.
+Use this page to identify and troubleshoot currently known issues with your beOS Pro One device. We regularly update this list with temporary workarounds and permanent fixes as they become available.
-## Olares One initial setup fails at 9%
+## beOS Pro One initial setup fails at 9%
-Olares One fails during the initial setup process with the installation stopping at around 9% and prompting you to uninstall or reinstall.
+beOS Pro One fails during the initial setup process with the installation stopping at around 9% and prompting you to uninstall or reinstall.
During startup, the system performs an asynchronous NTP time synchronization before issuing security certificates. While this usually completes instantly, occasional delays can cause a certificate to be issued with a future timestamp. This is especially common if the device has not yet updated from its default shipped timezone of UTC+8, finally causing the activation to fail.
@@ -18,10 +18,10 @@ Uninstall the incomplete installation and reactivate the device.
#### Step 1: Attempt SSH connection
-Try this method first if you do not already have a monitor and keyboard connected to your Olares device.
+Try this method first if you do not already have a monitor and keyboard connected to your beOS Pro device.
-1. Get the local **IP** address of Olares One from the **Activate Olares** page on the LarePass app.
- 
+1. Get the local **IP** address of beOS Pro One from the **Activate beOS Pro** page on the beOS Pro app app.
+ 
2. Open a terminal on your computer.
3. Type the following command, replace `` with the above local IP address, and then press **Enter**:
@@ -36,7 +36,7 @@ Try this method first if you do not already have a monitor and keyboard connecte
When the SSH access is unavailable, log in to the device locally using a monitor and keyboard.
-1. Connect a monitor and keyboard to your Olares One. A text-based login prompt is displayed on your screen automatically:
+1. Connect a monitor and keyboard to your beOS Pro One. A text-based login prompt is displayed on your screen automatically:
```text
olares login:
@@ -50,42 +50,42 @@ When the SSH access is unavailable, log in to the device locally using a monitor
1. Once logged in, type the following command and press **Enter**. This command removes all installed components and data, restoring the device to the unactivated state.
```bash
- sudo olares-cli uninstall
+ sudo beos-cli uninstall
```
2. Wait until the uninstallation is completed.
-#### Step 4: Reinstall and activate using LarePass
+#### Step 4: Reinstall and activate using beOS Pro app
:::tip Before reinstallation
To ensure accurate time synchronization, let the device remain powered on for a few minutes before reinstalling, allowing it to automatically calibrate its internal time.
:::
-1. Discover and link your Olares One based on your network setup.
+1. Discover and link your beOS Pro One based on your network setup.
- a. Ensure your Olares One is connected to your router via Ethernet.
+ a. Ensure your beOS Pro One is connected to your router via Ethernet.
- b. In the LarePass app, tap **Discover nearby Olares**.
- {width=90%}
+ b. In the beOS Pro app app, tap **Discover nearby beOS Pro**.
+ {width=90%}
If wired access is not available, use Bluetooth to configure Wi-Fi credentials.
- a. In the LarePass app, tap **Discover nearby Olares**.
+ a. In the beOS Pro app app, tap **Discover nearby beOS Pro**.
b. Tap **Bluetooth network setup** at the bottom.
c. Select your device from the Bluetooth list and tap **Network setup**.
- d. Follow the prompts to connect Olares One to the Wi-Fi network your phone is currently using.
+ d. Follow the prompts to connect beOS Pro One to the Wi-Fi network your phone is currently using.
- e. Once connected, return to the main screen and tap **Discover nearby Olares** again.
+ e. Once connected, return to the main screen and tap **Discover nearby beOS Pro** again.
-4. Find your Olares One from the list of available devices, and then tap **Install now** on it. The installation should now proceed and complete successfully.
+4. Find your beOS Pro One from the list of available devices, and then tap **Install now** on it. The installation should now proceed and complete successfully.
diff --git a/docs/one/market.md b/docs/one/market.md
index 9d2e84505..2d624faf6 100644
--- a/docs/one/market.md
+++ b/docs/one/market.md
@@ -1,21 +1,21 @@
---
outline: [2, 3]
-description: Perform common application management tasks in Olares Market. Learn how to install, update, and uninstall software.
+description: Perform common application management tasks in beOS Pro Market. Learn how to install, update, and uninstall software.
head:
- - meta
- name: keywords
- content: Olares, Olares One, install app, update app, uninstall app, Olares Market, Olares app market
+ content: beOS Pro, beOS Pro One, install app, update app, uninstall app, beOS Pro Market, beOS Pro app market
---
# Install & update applications
-Olares Market is an open and permissionless application platform. Use it to find official Olares apps, third-party tools, and AI services.
+beOS Pro Market is an open and permissionless application platform. Use it to find official beOS Pro apps, third-party tools, and AI services.
This guide walks you through the most common tasks for managing your applications, including finding and installing apps, applying updates, and removing unused apps.
## Learning objectives
-- Find applications from the Olares Market.
+- Find applications from the beOS Pro Market.
- Install applications. This guide uses "Jellyfin" as the example.
- Update applications to their latest versions.
- Uninstall applications to free up system resources.
@@ -37,7 +37,7 @@ Browse the Market catalog and install new software on your device.
:::tip Progress indicator
- Installation time depends on the app size and your internet speed. The **Install** button changes to a progress bar, indicating the download and installation status. You can navigate away and continue using Olares when it downloads in the background.
+ Installation time depends on the app size and your internet speed. The **Install** button changes to a progress bar, indicating the download and installation status. You can navigate away and continue using beOS Pro when it downloads in the background.
4. When the installation finishes, the button changes to **Open**. Click it to launch the app immediately.
@@ -61,7 +61,7 @@ Regular updates provide new features, bug fixes, and security patches. Keep your
Remove applications that you no longer need to save storage space.
1. Open Market from Dock or Launchpad.
-2. Click **My Olares** to view all your installed applications.
+2. Click **My beOS Pro** to view all your installed applications.
3. Find the target app "Jellyfin", click keyboard_arrow_down next to the **Open** button, and then click **Uninstall**.
diff --git a/docs/one/open-webui.md b/docs/one/open-webui.md
index 2c17f6afc..38cabc00d 100644
--- a/docs/one/open-webui.md
+++ b/docs/one/open-webui.md
@@ -1,6 +1,6 @@
---
outline: [2, 3]
-description: Learn how to set up Open WebUI on your Olares One to chat with local LLMs using Ollama.
+description: Learn how to set up Open WebUI on your beOS Pro One to chat with local LLMs using Ollama.
head:
- - meta
- name: keywords
@@ -18,7 +18,7 @@ You can easily install Ollama and chat with your local LLM using the Open WebUI.
## Prerequisites
**Hardware**
-- Olares One connected to a stable network.
+- beOS Pro One connected to a stable network.
- Sufficient disk space to download models.
**User permissions**
@@ -45,7 +45,7 @@ You can easily install Ollama and chat with your local LLM using the Open WebUI.
The first account created on Open WebUI gains Administrator privileges, controlling user management and system settings.
:::
## Step 3: Download models
-Because the Ollama API is pre-configured on Olares OS for Open WebUI, you can download models directly within the Open WebUI interface without using the command line.
+Because the Ollama API is pre-configured on beOS Pro for Open WebUI, you can download models directly within the Open WebUI interface without using the command line.
:::tip Check Ollama library
If you are unsure which model to download, check the [Ollama Library](https://ollama.com/library) to explore available models.
diff --git a/docs/one/redeem-membership.md b/docs/one/redeem-membership.md
index 183b5687f..ae061cdbb 100644
--- a/docs/one/redeem-membership.md
+++ b/docs/one/redeem-membership.md
@@ -1,61 +1,61 @@
---
outline: [2,3]
-description: Learn how to redeem your complimentary Olares Space Basic membership.
+description: Learn how to redeem your complimentary Remote Space Basic membership.
head:
- - meta
- name: keywords
- content: Olares, Olares One, Olares Space, redeem membership card, Basic plan, kickstarter backers
+ content: beOS Pro, beOS Pro One, Remote Space, redeem membership card, Basic plan, kickstarter backers
---
-# Redeem Olares Space membership
+# Redeem Remote Space membership
-Depending on your purchase channel such as the Kickstarter campaign, your Olares One package might include an Olares Space Membership card. This card grants you a complimentary 2-year Basic membership to use the enhanced connectivity services provided by Olares Space.
+Depending on your purchase channel such as the Kickstarter campaign, your beOS Pro One package might include an Remote Space Membership card. This card grants you a complimentary 2-year Basic membership to use the enhanced connectivity services provided by Remote Space.
-:::tip Olares One is a one-time purchase
-Your Olares One hardware and system updates are free forever.
+:::tip beOS Pro One is a one-time purchase
+Your beOS Pro One hardware and system updates are free forever.
-Olares Space is completely optional, so you are never locked in. If you choose not to renew your membership after the complimentary period ends, your use of Olares One will not be affected in any way.
+Remote Space is completely optional, so you are never locked in. If you choose not to renew your membership after the complimentary period ends, your use of beOS Pro One will not be affected in any way.
:::
## Before you begin
-Olares Space is a secure connectivity platform that extends the capabilities of your local device without compromising data sovereignty. The Basic plan includes:
+Remote Space is a secure connectivity platform that extends the capabilities of your local device without compromising data sovereignty. The Basic plan includes:
* **Cloud backup**: Up to 50 GB of integrated cloud storage for critical data redundancy. The free alternative is to back up your data to a local external drive or your own S3-compatible storage provider.
-* **Remote access (FRP)**: High-speed remote connection with 50 GB of monthly traffic at speeds up to 50 Mbps. This includes access to regional acceleration nodes for faster response times. If you exceed the monthly quota, speed is throttled to 5 Mbps. The free alternative is to use the LarePass VPN or host your own FRP server.
+* **Remote access (FRP)**: High-speed remote connection with 50 GB of monthly traffic at speeds up to 50 Mbps. This includes access to regional acceleration nodes for faster response times. If you exceed the monthly quota, speed is throttled to 5 Mbps. The free alternative is to use the beOS Pro app VPN or host your own FRP server.
-## Log in to Olares Space
+## Log in to Remote Space
-1. Go to https://space.olares.com.
+1. Go to https://space.beos.local.
- 
+ 
-2. Open the LarePass app on your mobile and log in using your Olares ID.
+2. Open the beOS Pro app app on your mobile and log in using your beOS ID.
3. Go to the **Settings** tab, and then tap the scan icon.
4. Scan the QR code on the computer screen and tap **Confirm**.
- Now you have logged in to Olares Space using your Olares ID.
+ Now you have logged in to Remote Space using your beOS ID.
- 
+ 
## Redeem Basic plan
:::info
-The 2-year validity period begins the moment you successfully bind your email to an Olares ID.
+The 2-year validity period begins the moment you successfully bind your email to an beOS ID.
:::
-To redeem the Basic plan benefits, you must link your account to the email address associated with your purchase order using the Olares Space dashboard. For example, the email associated with your Kickstarter order.
+To redeem the Basic plan benefits, you must link your account to the email address associated with your purchase order using the Remote Space dashboard. For example, the email associated with your Kickstarter order.
-1. In Olares Space, from the left navigation pane, click **Usage & billing**.
+1. In Remote Space, from the left navigation pane, click **Usage & billing**.
2. On the **Account email** tab, click **Email address**.
- 
+ 
3. In the **Add email** window, enter the email address used for your purchase order.
- 
+ 
4. Click **Send verification code**.
5. Follow the on-screen instructions to complete the verification.
@@ -68,21 +68,21 @@ To redeem the Basic plan benefits, you must link your account to the email addre
6. Click your avatar in the upper right corner. A **Basic** tag appearing next to your username confirms that your membership is active now.
- 
+ 
-## Transfer membership to a different Olares ID
+## Transfer membership to a different beOS ID
:::warning Validity period adjustment
-Transferring your membership to a new Olares ID reduces your remaining validity period by one month. If you transfer multiple times within the same calendar month, the deduction only occurs once.
+Transferring your membership to a new beOS ID reduces your remaining validity period by one month. If you transfer multiple times within the same calendar month, the deduction only occurs once.
:::
:::warning Changing bound email
The Basic membership is tied strictly to the specific email address used for your purchase order. If you change the email, the current account loses the Basic membership immediately.
:::
-If you want to transfer your Basic membership to a new Olares ID:
+If you want to transfer your Basic membership to a new beOS ID:
-1. Log in to Olares Space with your old Olares ID.
+1. Log in to Remote Space with your old beOS ID.
2. Go to **Usage & billing** > **Account email**.
3. Click **Unbind** to remove the purchase order email from the account email settings.
@@ -93,10 +93,10 @@ If you want to transfer your Basic membership to a new Olares ID:
A notification message will confirm that the email was removed. The current account changes to the Free plan immediately.
-6. Log in to Olares Space with the new Olares ID.
-7. Bind the purchase order email using the steps in the [Redeem Basic plan](#redeem-basic-plan) section. This will upgrade the new Olares ID to the Basic plan immediately.
+6. Log in to Remote Space with the new beOS ID.
+7. Bind the purchase order email using the steps in the [Redeem Basic plan](#redeem-basic-plan) section. This will upgrade the new beOS ID to the Basic plan immediately.
## Resources
-- [Monitor traffic in Olares Space](space.md)
-- [Olares Space introduction](../space/index.md)
\ No newline at end of file
+- [Monitor traffic in Remote Space](space.md)
+- [Remote Space introduction](../space/index.md)
\ No newline at end of file
diff --git a/docs/one/reusables-reset-ssh.md b/docs/one/reusables-reset-ssh.md
index 37bc1c188..611649ca3 100644
--- a/docs/one/reusables-reset-ssh.md
+++ b/docs/one/reusables-reset-ssh.md
@@ -4,24 +4,24 @@ search: false
## Reset SSH password
### Reset upon activation
-Right after you activate Olares, you will be prompted to reset the SSH password on the LarePass app. The password is automatically generated and saved to your Vault.
+Right after you activate beOS Pro, you will be prompted to reset the SSH password on the beOS Pro app app. The password is automatically generated and saved to your Vault.
To view the saved password in Vault:
-1. Tap **Vault** in the LarePass app. When prompted, enter your local password to unlock.
+1. Tap **Vault** in the beOS Pro app app. When prompted, enter your local password to unlock.
2. In the top-left corner, tap **Authenticator** to open the side navigation, then tap **All vaults** to display all saved items.
3. Find the item with the terminal icon and tap it to reveal the password.
-### Reset in Olares Settings
+### Reset in beOS Pro Settings
If you prefer to use an SSH password instead of the automatically generated one, you can manually reset the password in Settings.
-1. Open Settings. On the **My Olares** page, select **My hardware**.
+1. Open Settings. On the **My beOS Pro** page, select **My hardware**.
2. Select **Reset SSH login password** at the bottom.
{width=70%}
3. In the dialog, enter a new SSH password that meets all strength requirements, then click **OK**.
-4. Open the LarePass app and scan the QR code shown on the screen.
-5. Click **Confirm** on LarePass to finish.
\ No newline at end of file
+4. Open the beOS Pro app app and scan the QR code shown on the screen.
+5. Click **Confirm** on beOS Pro app to finish.
\ No newline at end of file
diff --git a/docs/one/space.md b/docs/one/space.md
index 2cfbe5d54..743045b0e 100644
--- a/docs/one/space.md
+++ b/docs/one/space.md
@@ -1,17 +1,17 @@
---
outline: [2,3]
-description: Learn how to link your device to Olares Space and monitor your cloud traffic and backup storage usage.
+description: Learn how to link your device to Remote Space and monitor your cloud traffic and backup storage usage.
head:
- - meta
- name: keywords
- content: Olares, Olares One, Olares Space, monitor traffic usage, billing
+ content: beOS Pro, beOS Pro One, Remote Space, monitor traffic usage, billing
---
-# Monitor traffic in Olares Space
+# Monitor traffic in Remote Space
-Olares Space is the cloud-based management platform for your device. While your Olares device runs locally, Olares Space allows you to monitor cloud traffic usage and manage billing from any web browser.
+Remote Space is the cloud-based management platform for your device. While your beOS Pro device runs locally, Remote Space allows you to monitor cloud traffic usage and manage billing from any web browser.
-This guide explains how to link your Olares device to Olares Space and track your traffic usage.
+This guide explains how to link your beOS Pro device to Remote Space and track your traffic usage.
:::info Usage and billing
If you use cloud services such as remote access (accessing your device from outside your home) or cloud backups, monitoring your usage is important. These services might incur charges if you exceed the limits of your subscription plan.
@@ -19,21 +19,21 @@ If you use cloud services such as remote access (accessing your device from outs
## Learning objectives
-- Link your Olares device to your Olares Space account.
-- Log in to the Olares Space.
+- Link your beOS Pro device to your Remote Space account.
+- Log in to the Remote Space.
- Monitor cloud traffic consumption.
## Before you begin
-Ensure you have the LarePass app installed on your mobile device and logged in with your Olares ID.
+Ensure you have the beOS Pro app app installed on your mobile device and logged in with your beOS ID.
-## Step 1. Link Olares Space
+## Step 1. Link Remote Space
-Before you can view statistics in Olares Space, you must authorize Olares Space to access your device's status. You do this through the LarePass mobile app.
+Before you can view statistics in Remote Space, you must authorize Remote Space to access your device's status. You do this through the beOS Pro app mobile app.
-1. Open the LarePass app on your mobile and go to **Settings** > **Integration**.
+1. Open the beOS Pro app app on your mobile and go to **Settings** > **Integration**.
- 
+ 
2. Tap add in the top right corner.
@@ -43,44 +43,44 @@ Before you can view statistics in Olares Space, you must authorize Olares Space
- When completed, your Olares Space account is linked to your physical device, and the Olares Space account is displayed in the **Integration** list.
+ When completed, your Remote Space account is linked to your physical device, and the Remote Space account is displayed in the **Integration** list.
- 
+ 
-## Step 2. Log in to Olares Space
+## Step 2. Log in to Remote Space
-Access the Olares Space dashboard via a web browser.
+Access the Remote Space dashboard via a web browser.
-1. Go to https://space.olares.com/.
+1. Go to https://space.beos.local/.
- 
+ 
-2. Log in to Olares Space:
+2. Log in to Remote Space:
- a. In the LarePass app, go to **Settings**, and then tap the scan icon.
+ a. In the beOS Pro app app, go to **Settings**, and then tap the scan icon.
- b. Scan the QR code on the computer screen and tap **Confirm**. Now you have logged in to Olares Space.
+ b. Scan the QR code on the computer screen and tap **Confirm**. Now you have logged in to Remote Space.
+-->
## Step 3. Check traffic usage
Monitor how much data you have used for remote access to avoid exceeding the monthly limit of your subscription.
1. From the left navigation pane, click **Usage & billing**.
- 
+ 
2. On the **Usage** tab, check the **Traffic details** section. By default, traffic details of the latest billing cycle is displayed.
@@ -91,12 +91,12 @@ Monitor how much data you have used for remote access to avoid exceeding the mon
a. Click the date range dropdown list.
- 
+ 
b. Select a specific billing period to view the traffic history for that month. For example, 2025-12-02 ~ 2026-01-02.
## Resources
-- [Olares Space plans and pricing](https://space.olares.com/plans)
-- [Manage Olares](../space/manage-olares.md)
-- [Olares Space billing](../space/billing.md)
\ No newline at end of file
+- [Remote Space plans and pricing](https://space.beos.local/plans)
+- [Manage beOS Pro](../space/manage-olares.md)
+- [Remote Space billing](../space/billing.md)
\ No newline at end of file
diff --git a/docs/one/spec.md b/docs/one/spec.md
index 537932d86..f91018f8b 100644
--- a/docs/one/spec.md
+++ b/docs/one/spec.md
@@ -1,23 +1,23 @@
---
outline: [2, 3]
-description: View the hardware components and specifications of Olares One.
+description: View the hardware components and specifications of beOS Pro One.
head:
- - meta
- name: keywords
- content: Olares, Olares One, technical specifications, tech specs, hardware specs
+ content: beOS Pro, beOS Pro One, technical specifications, tech specs, hardware specs
---
# Technical specifications
-Olares One features high-performance components designed to run advanced AI models locally and host private services efficiently.
+beOS Pro One features high-performance components designed to run advanced AI models locally and host private services efficiently.
This page provides information about the hardware components and specifications.
## Hardware overview
-Refer to the following table to identify the buttons, ports, and interfaces on Olares One.
+Refer to the following table to identify the buttons, ports, and interfaces on beOS Pro One.
-
+
| No. | Component | Description |
|:----|:------------------------|:-------------------------------------------------------------------------------------|
@@ -30,7 +30,7 @@ Refer to the following table to identify the buttons, ports, and interfaces on O
## Component specifications
-Refer to the following table for detailed hardware specifications of Olares One.
+Refer to the following table for detailed hardware specifications of beOS Pro One.
| Component | Specification |
|:-----------------------|:--------------------------------------------------------------------------------------------------------------------------------|
diff --git a/docs/one/steam-direct-play.md b/docs/one/steam-direct-play.md
index bc4f7d3b8..52f4abb5e 100644
--- a/docs/one/steam-direct-play.md
+++ b/docs/one/steam-direct-play.md
@@ -1,27 +1,27 @@
---
outline: [2, 3]
-description: Learn how to turn your Olares device into a gaming console by connecting a monitor and peripherals directly.
+description: Learn how to turn your beOS Pro device into a gaming console by connecting a monitor and peripherals directly.
head:
- - meta
- name: keywords
content: Steam, Local Gaming, Direct Play, Linux Gaming, Audio Configuration
---
-# Play Steam games locally on Olares One
+# Play Steam games locally on beOS Pro One
-While Olares One is typically used as a headless system, you can connect a monitor, keyboard, and mouse to play games directly.
+While beOS Pro One is typically used as a headless system, you can connect a monitor, keyboard, and mouse to play games directly.
However, simply plugging in a monitor is not enough. Because Steam Headless is optimized for remote streaming by default, you must manually configure the audio settings to output audio locally.
## Learning objectives
-- Set up Steam Headless on your Olares One.
+- Set up Steam Headless on your beOS Pro One.
- Grant the application permission to access the host sound card.
- Modify display and audio settings for local gameplay.
## Prerequisites
**Hardware**
-- Olares One connected to a stable network (Ethernet recommended).
-- Monitor, keyboard, and mouse connected to the Olares One.
+- beOS Pro One connected to a stable network (Ethernet recommended).
+- Monitor, keyboard, and mouse connected to the beOS Pro One.
- Sufficient disk space to download games.
**Software**
@@ -263,7 +263,7 @@ To enable audio for streaming:
## FAQs
### Why does my monitor show the Steam interface even when I'm not playing?
-Olares One usually displays a terminal prompt when connected to a monitor. However, running the Steam application activates a graphical interface that takes over the display.
+beOS Pro One usually displays a terminal prompt when connected to a monitor. However, running the Steam application activates a graphical interface that takes over the display.
To return the monitor to the standard terminal view, you must stop the Steam application via **Market** or **Settings**.
diff --git a/docs/one/steam-stream.md b/docs/one/steam-stream.md
index 20cb4e8dd..1d8d93705 100644
--- a/docs/one/steam-stream.md
+++ b/docs/one/steam-stream.md
@@ -1,6 +1,6 @@
---
outline: [2, 3]
-description: Comprehensive tutorial on streaming Steam games with Olares. Learn to install Steam Headless, configure the streaming service, and stream games on Moonlight from both local and remote networks.
+description: Comprehensive tutorial on streaming Steam games with beOS Pro. Learn to install Steam Headless, configure the streaming service, and stream games on Moonlight from both local and remote networks.
head:
- - meta
- name: keywords
@@ -9,24 +9,24 @@ head:
# Stream Steam games to any device
-Equipped by an NVDIA 5090 mobile GPU, with the Steam Headless app, Olares One transforms into a powerful game streaming server. You can play your favorite games on any compatible device via Moonlight.
+Equipped by an NVDIA 5090 mobile GPU, with the Steam Headless app, beOS Pro One transforms into a powerful game streaming server. You can play your favorite games on any compatible device via Moonlight.
## Learning objectives
-- Set up Steam Headless on your Olares One.
+- Set up Steam Headless on your beOS Pro One.
- Configure the Sunshine streaming service.
-- Pair your Olares One via Moonlight and stream games locally or remotely.
+- Pair your beOS Pro One via Moonlight and stream games locally or remotely.
## Prerequisites
**Hardware**
-- Olares One connected to a stable network (Ethernet recommended).
+- beOS Pro One connected to a stable network (Ethernet recommended).
- Sufficient disk space to download games.
**Software**
- [Moonlight](https://moonlight-stream.org/) installed on the client device.
- A valid Steam account.
-**LarePass** (Required for remote access)
-- LarePass required on your client device (desktop or mobile) if you plan to stream outside your home network.
+**beOS Pro app** (Required for remote access)
+- beOS Pro app required on your client device (desktop or mobile) if you plan to stream outside your home network.
## Step 1: Install Steam Headless
@@ -63,7 +63,7 @@ Steam Headless uses Sunshine to stream video. You must pair it with the Moonligh
### Access the Sunshine console
-You need to access the Sunshine Web UI running on your Olares One to enter a pairing PIN.
+You need to access the Sunshine Web UI running on your beOS Pro One to enter a pairing PIN.
1. Copy the URL of your current Steam Headless browser tab.
2. Open a new browser tab and modify the URL to access port `47990`. The address varies depending on your network.
@@ -75,14 +75,14 @@ You need to access the Sunshine Web UI running on your Olares One to enter a pai
:::
```plain
- https://139ebc4f0..olares.local:47990
- https://139ebc4f0--olares.local:47990
+ https://139ebc4f0..olares.local:47990
+ https://139ebc4f0--olares.local:47990
```
- - **Different network (via VPN)**: Enable LarePass VPN on your device, then append `:47990`. For example:
+ - **Different network (via VPN)**: Enable beOS Pro app VPN on your device, then append `:47990`. For example:
```plain
- https://139ebc4f0..olares.com:47990
+ https://139ebc4f0..beos.local:47990
```
3. Press **Enter** to open the Sunshine console page.
@@ -93,16 +93,16 @@ You need to access the Sunshine Web UI running on your Olares One to enter a pai
### Add the host in Moonlight
-Moonlight usually detects your Olares host automatically when it is on the same local network as your Olares One.
+Moonlight usually detects your beOS Pro host automatically when it is on the same local network as your beOS Pro One.
If it doesn't appear, or if you are connecting over different networks, follow these steps to add the host manually. The process shown below uses the macOS Moonlight client.
1. Open Moonlight on your client device.
2. Click the **Add Host** button, which looks like a computer with a plus icon.
-3. Enter your Olares domain without the `https://` prefix. For example:
+3. Enter your beOS Pro domain without the `https://` prefix. For example:
```plain
- 139ebc4f0..olares.com
+ 139ebc4f0..beos.local
```
4. Click **OK**. A new locked host icon appears.
5. Click the locked icon. Moonlight will display a 4-digit pairing PIN.
@@ -124,14 +124,14 @@ Once paired, you're ready to start streaming.
:::tip Optimizing remote play
For the best experience when streaming remotely:
1. Connect your client device to 5GHz Wi-Fi or Ethernet.
-2. Ensure **LarePass VPN** is active.
+2. Ensure **beOS Pro app VPN** is active.
:::
You can stream your games through Moonlight either locally or remotely, depending on your network setup.
The following steps demonstrate local streaming.
1. Open Moonlight on your client device.
-2. Select your Olares host and click the **Steam** icon.
+2. Select your beOS Pro host and click the **Steam** icon.
3. Steam **Big Picture Mode** will launch. Select a game from your library and start playing.
@@ -140,9 +140,9 @@ The following steps demonstrate local streaming.
### Why can't I access the Sunshine Web UI using the `.local` address?
-For most Olares services, you use HTTP with `.local` addresses. Sunshine is an exception and requires HTTPS to secure local communication. If you use `http://` with your `.local` URL, the Sunshine page will not load.
+For most beOS Pro services, you use HTTP with `.local` addresses. Sunshine is an exception and requires HTTPS to secure local communication. If you use `http://` with your `.local` URL, the Sunshine page will not load.
-Use `https://` in your browser's address bar (for example, `https://139ebc4f0..olares.local:47990`).
+Use `https://` in your browser's address bar (for example, `https://139ebc4f0..olares.local:47990`).
### Why isn't the game displaying in full screen?
@@ -160,7 +160,7 @@ Use the following shortcuts:
- **Mac**: `Control (^) + Option (⌥) + Shift + Q`
- **Mobile**: `Start + Select + L1 + R1`
-After finishing, exit Steam Big Picture mode to release system resources on Olares.
+After finishing, exit Steam Big Picture mode to release system resources on beOS Pro.
### Where are my downloaded games stored?
@@ -175,14 +175,14 @@ We recommend not changing this default directory.
### Why do I get an error when re-pairing the host in Moonlight?
-If you delete your Olares host in Moonlight and try to pair again, you may encounter the following errors:
+If you delete your beOS Pro host in Moonlight and try to pair again, you may encounter the following errors:
- **The PIN from the PC didn't match. Please try again.**
- **Request timed out (Error 4)**
- **Connection closed (Error 2)**
This usually happens when the Sunshine service is not responding.
-To fix it, simply restart Steam Headless in Olares and try pairing again:
+To fix it, simply restart Steam Headless in beOS Pro and try pairing again:
1. Open Control Hub from Launchpad.
2. Navigate to **Browser** > **steamheadless** > **Deployments** > **steamheadless** > **Restart**.
@@ -197,7 +197,7 @@ To fix it, simply restart Steam Headless in Olares and try pairing again:
You can change your Sunshine credentials directly from the Sunshine web console.
-1. Open Sunshine in your browser using your local address, for example: `https://139ebc4f0..olares.local:47990`.
+1. Open Sunshine in your browser using your local address, for example: `https://139ebc4f0..olares.local:47990`.
2. Log in with your current username and password.
3. Go to the **Change Password** tab.
@@ -205,4 +205,4 @@ You can change your Sunshine credentials directly from the Sunshine web console.
4. Enter a new password (and username if desired), then click **Save**.
## Resources
-- [Play Steam games locally on Olares One](steam-direct-play.md)
\ No newline at end of file
+- [Play Steam games locally on beOS Pro One](steam-direct-play.md)
\ No newline at end of file
diff --git a/docs/one/update.md b/docs/one/update.md
index 928b2c2a7..0315f736c 100644
--- a/docs/one/update.md
+++ b/docs/one/update.md
@@ -1,37 +1,37 @@
---
outline: [2, 3]
-description: Learn how to use the LarePass app to check for and install system updates on your Olares One.
+description: Learn how to use the beOS Pro app app to check for and install system updates on your beOS Pro One.
head:
- - meta
- name: keywords
- content: Olares One, Update Olares
+ content: beOS Pro One, Update beOS Pro
---
# Update OS
-Use the LarePass app to keep your Olares One up to date with the latest features and security patches.
+Use the beOS Pro app app to keep your beOS Pro One up to date with the latest features and security patches.
:::warning Admin access required
-Only an Olares administrator can perform system updates. Please note that updates apply to the entire Olares cluster and affect all members.
+Only an beOS Pro administrator can perform system updates. Please note that updates apply to the entire beOS Pro cluster and affect all members.
:::
## Learning objectives
By the end of this tutorial, you will learn how to:
-- Check whether a new Olares OS version is available in LarePass.
+- Check whether a new beOS Pro version is available in beOS Pro app.
- Choose between **Download only** and **Download and upgrade**.
- Install an update and confirm the system restarts successfully.
## Prerequisites
Make sure that:
-- Your Olares One is powered on and connected to a network.
-- Your phone can access Olares One through LarePass.
+- Your beOS Pro One is powered on and connected to a network.
+- Your phone can access beOS Pro One through beOS Pro app.
- You are signed in with an account that has administrator permissions.
## Check for updates
-1. Open LarePass on your phone and go to **Settings**.
-2. In the **My Olares** card, tap **System** to enter the **Olares management** page.
+1. Open beOS Pro app on your phone and go to **Settings**.
+2. In the **My beOS Pro** card, tap **System** to enter the **beOS Pro management** page.
3. Tap **System update**.
4. If a new version appears in the **New version** field, tap **Upgrade**.
@@ -40,9 +40,9 @@ Make sure that:
A dialog will appear asking how you want to handle the update package. Choose the method that fits your schedule:
-- **Download only**: Olares downloads the package in the background. You can continue using the system and install the update manually later.
+- **Download only**: beOS Pro downloads the package in the background. You can continue using the system and install the update manually later.
-- **Download and upgrade**: Olares downloads the package and prompts you to restart and install it when the download finishes.
+- **Download and upgrade**: beOS Pro downloads the package and prompts you to restart and install it when the download finishes.
@@ -51,4 +51,4 @@ A dialog will appear asking how you want to handle the update package. Choose th
1. Start installation based on your selection:
- **Download only**: After the download completes, return to **System update** and tap **Upgrade now**. Confirm the restart prompt to begin installation.
- **Download and upgrade**: After the download completes, confirm the restart prompt to begin installation.
-2. Wait for the update and restart to finish. When Olares starts up again, you'll see a success message and can continue using it.
\ No newline at end of file
+2. Wait for the update and restart to finish. When beOS Pro starts up again, you'll see a success message and can continue using it.
\ No newline at end of file
diff --git a/docs/one/vault.md b/docs/one/vault.md
index 907e77a26..92d02cf01 100644
--- a/docs/one/vault.md
+++ b/docs/one/vault.md
@@ -1,15 +1,15 @@
---
outline: [2, 3]
-description: Understand Vault basics in Olares. Learn to set up vaults and manage vault items.
+description: Understand Vault basics in beOS Pro. Learn to set up vaults and manage vault items.
head:
- - meta
- name: keywords
- content: Olares, Olares One, Vault, password manager, store credentials, secure sensitive data
+ content: beOS Pro, beOS Pro One, Vault, password manager, store credentials, secure sensitive data
---
# Secure passwords with Vault
-Vault is the dedicated password and sensitive data manager in Olares. Use it to securely store passwords, keys, digital identities, and sensitive documents.
+Vault is the dedicated password and sensitive data manager in beOS Pro. Use it to securely store passwords, keys, digital identities, and sensitive documents.
This guide covers the fundamentals of using Vault, including setting up your first vault, importing credentials, and managing your sensitive data efficiently.
@@ -26,7 +26,7 @@ Familiarize yourself with related Vault concepts and how Vault organizes your da
### Vault types
-Olares Vault offers two main types of vaults:
+beOS Pro Vault offers two main types of vaults:
* My vault: This is your private vault that is created automatically upon account activation. The vault is encrypted with your mnemonic and is visible only to you.
* Team vaults: These are collaborative vaults that are used to share credentials securely with team members or family.
@@ -48,12 +48,12 @@ When you open Vault on your device for the first time, you must initialize it fo
{width=35%}
:::tip Security best practice
- Do not use the same password as your Olares login. If someone guesses your login password, this secondary password ensures your sensitive data remains locked.
+ Do not use the same password as your beOS Pro login. If someone guesses your login password, this secondary password ensures your sensitive data remains locked.
:::
3. Click **Confirm**.
-4. Import your Olares ID that is already linked to your server using your mnemonic phrase.
+4. Import your beOS ID that is already linked to your server using your mnemonic phrase.
{width=35%}
@@ -142,27 +142,27 @@ Use the left sidebar to narrow down the list:
- [Import vault items](../manual/olares/vault/vault-items.md#import)
- [Manage shared vaults](../manual/olares/vault/share-vault-items.md)
-- [Autofill passwords with LarePass](../manual/larepass/autofill.md)
+- [Autofill passwords with beOS Pro app](../manual/larepass/autofill.md)
- [Generate two-factor authentication codes](../manual/larepass/two-factor-verification.md)
-
-To use the secure VPN connection, the LarePass client must be installed on the device you are using to access Olares.
+To use the secure VPN connection, the beOS Pro app client must be installed on the device you are using to access beOS Pro.
-- **Mobile**: Use the LarePass app installed during the Olares ID creation process.
-- **Desktop**: Download and install the LarePass desktop client.
+- **Mobile**: Use the beOS Pro app app installed during the beOS ID creation process.
+- **Desktop**: Download and install the beOS Pro app desktop client.
1. Visit .
2. Download the version compatible with your operating system.
-3. Install the application and log in with your Olares ID.
+3. Install the application and log in with your beOS ID.
Once installed, enable the VPN directly on the device.
:::tip Always enable VPN for remote access
-Keep LarePass VPN enabled. It automatically prioritizes the fastest available route to ensure you always get the best speed possible without manual switching.
+Keep beOS Pro app VPN enabled. It automatically prioritizes the fastest available route to ensure you always get the best speed possible without manual switching.
:::
:::info iOS and macOS setup
On iOS or macOS, you may be prompted to add a VPN Configuration to your system settings the first time you enable the feature. Allow this to complete the setup.
:::
-
+
-1. Open the LarePass app and go to **Settings**.
-2. In the **My Olares** card, toggle on the VPN switch.
+1. Open the beOS Pro app app and go to **Settings**.
+2. In the **My beOS Pro** card, toggle on the VPN switch.
- 
+ 
-
+
-1. Open the LarePass app and click your avatar in the top-left corner to open the user menu.
+1. Open the beOS Pro app app and click your avatar in the top-left corner to open the user menu.
2. Toggle on the switch for **VPN connection**.
- 
+ 
-Once enabled, check the status indicator in LarePass to verify the connection type:
+Once enabled, check the status indicator in beOS Pro app to verify the connection type:
| Status | Description |
|:-------------|:---------------------------------------------------------|
@@ -48,10 +48,10 @@ Once enabled, check the status indicator in LarePass to verify the connection ty
| **P2P** | Direct encrypted tunnel between devices. High speed. |
| **DERP** | Routed via a secure relay server. Used as a fallback. |
-### Why doesn't LarePass VPN work on my Mac anymore?
+### Why doesn't beOS Pro app VPN work on my Mac anymore?
-macOS blocks the VPN tunnel if the network extension or VPN configuration was not fully set up, or if the extension has become stuck or corrupted. See [LarePass VPN not working](/manual/help/ts-larepass-vpn-not-working) to reset the extension and restore the VPN.
+macOS blocks the VPN tunnel if the network extension or VPN configuration was not fully set up, or if the extension has become stuck or corrupted. See [beOS Pro app VPN not working](/manual/help/ts-larepass-vpn-not-working) to reset the extension and restore the VPN.
-### Why can't I enable LarePass VPN on Windows?
+### Why can't I enable beOS Pro app VPN on Windows?
-Third-party antivirus or security software may mistakenly flag LarePass as suspicious, preventing the VPN service from starting. See [LarePass VPN not working](/manual/help/ts-larepass-vpn-not-working) to resolve the issue.
+Third-party antivirus or security software may mistakenly flag beOS Pro app as suspicious, preventing the VPN service from starting. See [beOS Pro app VPN not working](/manual/help/ts-larepass-vpn-not-working) to resolve the issue.
diff --git a/docs/reusables/local-domain.md b/docs/reusables/local-domain.md
index dde668abc..4c88eeb0b 100644
--- a/docs/reusables/local-domain.md
+++ b/docs/reusables/local-domain.md
@@ -5,9 +5,9 @@ search: false
Order: description, URL+HTTP, Windows, then FAQs.
Ranges: description 7-8, URL+HTTP 10-23, Windows 25-40 (content only 26-40), FAQs 42-75 -->
-When your device is on the same local network as Olares, you can use a `.local` domain to reach your services so traffic stays on your LAN.
+When your device is on the same local network as beOS Pro, you can use a `.local` domain to reach your services so traffic stays on your LAN.
-Use a multi-level `.local` hostname that mirrors your standard URL. This format works with Olares system apps and community apps.
+Use a multi-level `.local` hostname that mirrors your standard URL. This format works with beOS Pro system apps and community apps.
:::tip
Use `http://`, not `https://`, with the `.local` URL.
@@ -15,7 +15,7 @@ Use `http://`, not `https://`, with the `.local` URL.
**Standard URL**
```text
-https://..olares.com
+https://..beos.local
```
**Local URL**
```text
@@ -24,10 +24,10 @@ http://..olares.local
### Windows
-On Windows, `.local` hostnames are not resolved by default. Use the LarePass desktop app to add the necessary entries to your hosts file so multi-level `.local` URLs resolve to your Olares device.
+On Windows, `.local` hostnames are not resolved by default. Use the beOS Pro app desktop app to add the necessary entries to your hosts file so multi-level `.local` URLs resolve to your beOS Pro device.
-1. Open the LarePass app, click your avatar, then **Settings**.
-2. Scroll to **Enable local service domain** and click **Add**. LarePass will update your hosts file automatically.
+1. Open the beOS Pro app app, click your avatar, then **Settings**.
+2. Scroll to **Enable local service domain** and click **Add**. beOS Pro app will update your hosts file automatically.
3. When the update completes, a success message appears. If a command line window opens, you can close it.
@@ -35,9 +35,9 @@ On Windows, `.local` hostnames are not resolved by default. Use the LarePass des
a. Go to `C:\Windows\System32\drivers\etc\`.
- b. Open the `hosts` file in a text editor. You should see the `.local` entries that LarePass added.
+ b. Open the `hosts` file in a text editor. You should see the `.local` entries that beOS Pro app added.
- 
+ 
### Why doesn't the .local domain work in Chrome on macOS?
diff --git a/docs/space/backup-restore.md b/docs/space/backup-restore.md
index c0380b8bb..43ada748b 100644
--- a/docs/space/backup-restore.md
+++ b/docs/space/backup-restore.md
@@ -1,9 +1,9 @@
---
-description: Protect your Olares instances with cloud backup and restore features. Handle snapshots, perform restore operations, and manage storage quotas in Olares Space.
+description: Protect your beOS Pro instances with cloud backup and restore features. Handle snapshots, perform restore operations, and manage storage quotas in Remote Space.
---
# Back up and restore
-Olares Space is the official solution to back up snapshots for your Olares instances. You can restore an Olares to its most recent state whenever needed. This section provides instructions for managing backups and restores in Olares Space.
+Remote Space is the official solution to back up snapshots for your beOS Pro instances. You can restore an beOS Pro to its most recent state whenever needed. This section provides instructions for managing backups and restores in Remote Space.
## View backup list
@@ -13,7 +13,7 @@ The backup task list shows information for each backup task, including:
- Most recent snapshot time
- Overall storage usage
-
+
Click **View Details** on a task to see its detail page. The detail page shows the storage usage since the task was created and a list of all successful snapshots.
@@ -21,11 +21,11 @@ Click **View Details** on a task to see its detail page. The detail page shows t
Currently, only restoring from the most recent snapshot is supported.
:::
-## Restore backup to the Olares Space
+## Restore backup to the Remote Space
-
+
-Restoring a snapshot to the cloud is similar to setting up a new cloud-based Olares.
+Restoring a snapshot to the cloud is similar to setting up a new cloud-based beOS Pro.
1. Set up relevant details.
@@ -37,12 +37,12 @@ Restoring a snapshot to the cloud is similar to setting up a new cloud-based Ola
2. Understand charges for storage and bandwidth.
Each instance includes a certain amount of free traffic. Any usage exceeding the quota will incur charges. For more information, see [Billing](billing.md).
-3. Confirm the order and complete the payment. After that, the Olares begins to install.
+3. Confirm the order and complete the payment. After that, the beOS Pro begins to install.
:::info NOTE
-During the installation process, Olares will verify the backup password. If it is incorrect, you'll be asked to re-enter the correct one. If you forget the backup password, the restoration process won't be able to continue. In this case, please return your instance and try restoring again.
+During the installation process, beOS Pro will verify the backup password. If it is incorrect, you'll be asked to re-enter the correct one. If you forget the backup password, the restoration process won't be able to continue. In this case, please return your instance and try restoring again.
:::
:::info NOTE
-To avoid conflicts or other unforeseeable problem, you must return the existing Olares that uses the same name before restoring to a cloud-based Olares.
+To avoid conflicts or other unforeseeable problem, you must return the existing beOS Pro that uses the same name before restoring to a cloud-based beOS Pro.
:::
\ No newline at end of file
diff --git a/docs/space/billing.md b/docs/space/billing.md
index 4915637a7..21a04ce08 100644
--- a/docs/space/billing.md
+++ b/docs/space/billing.md
@@ -1,20 +1,20 @@
---
-description: Understand Olares Space billing system with service charges and payment workflows. Learn about cloud hosting fees, usage based pricing, and promotional credit applications.
+description: Understand Remote Space billing system with service charges and payment workflows. Learn about cloud hosting fees, usage based pricing, and promotional credit applications.
---
# Billing
-Olares partners with Stripe for secure payment processing. Your invoices and receipts will be sent via email, allowing you to keep records for analysis. If you have any questions during the payment process, please contact support.
+beOS Pro partners with Stripe for secure payment processing. Your invoices and receipts will be sent via email, allowing you to keep records for analysis. If you have any questions during the payment process, please contact support.
## The scope of billing
The following services or products are billed:
-- **Hosted Olares**: Prepaid product required for setting up an Olares on a cloud provider like AWS or GCS. Pricing varies depends on the provider you choose.
+- **Hosted beOS Pro**: Prepaid product required for setting up an beOS Pro on a cloud provider like AWS or GCS. Pricing varies depends on the provider you choose.
- **Host instance traffic**: Postpaid charges for external traffic generated by cloud hosting out of assigned regions.
-- **Worker instance**: Adding a Worker node to a hosted Olares also incurs monthly charges. Charges will be combined to the monthly bill.
+- **Worker instance**: Adding a Worker node to a hosted beOS Pro also incurs monthly charges. Charges will be combined to the monthly bill.
- **Cloud storage**: Postpaid product storing system data via JuiceFS. Billed based on usage at the end of the billing cycle.
- **Cloud backup/restore**: Backs up host data to public storage. Billed based on usage at the end of the billing cycle.
-- **Cloudflare tunnel (FRP) traffic**: Postpaid for traffic incurred by self-hosted Olares when services are accessed via public links.
+- **Cloudflare tunnel (FRP) traffic**: Postpaid for traffic incurred by self-hosted beOS Pro when services are accessed via public links.
- **GPU unit**: Prepaid for GPU-related services. Charges are deducted from prepaid units based on usage.
@@ -22,16 +22,16 @@ The following services or products are billed:
The following actions generate bills:
-- **Creating an Olares in the cloud**: An invoice is generated immediately after you select a cloud provider and configuration. Payment is required for installation to begin.
+- **Creating an beOS Pro in the cloud**: An invoice is generated immediately after you select a cloud provider and configuration. Payment is required for installation to begin.
- **Adding/Removing workers**: Bills are generated for adding workers based on the remaining time in the billing period. Similarly, refunds are calculated when removing workers.
-- **Restoring a snapshot**: Equivalent to creating a new Olares, with monthly charges applied.
-- **Destroying an Olares**: Fees are settled up to the destruction date. Refunds are processed as applicable.
+- **Restoring a snapshot**: Equivalent to creating a new beOS Pro, with monthly charges applied.
+- **Destroying an beOS Pro**: Fees are settled up to the destruction date. Refunds are processed as applicable.
The monthly bill updated once per month. It includes the base subscription fees as well as any additional charges incurred during the month, such as adding a Worker, or extra traffic and storage fees.
## How fees are deducted monthly
-Olares operates on a monthly billing cycle:
+beOS Pro operates on a monthly billing cycle:
- **Automatic deduction**: Your first payment will authorize automatic deductions, with the first payment method set as default. You can disable auto-deductions from the control panel if you prefer to pay manually, but make sure to settle your bills on time to avoid service interruption.
- **Payment validity period**: For each purchase, you'll receive a bill valid for 24 hours.
@@ -41,7 +41,7 @@ Olares operates on a monthly billing cycle:
We distribute trial credits or coupons through promotions.
- Once you have received trial credits, you can view them in **Billing** > **Balance History**, and apply directly to specific products when you pay.
-- Once you receive a promotional coupon codes, you can redeem them in **Billing** > **Coupons**. It could be a discount to your plans, plan subscriptions, Olares memberships, and more.
+- Once you receive a promotional coupon codes, you can redeem them in **Billing** > **Coupons**. It could be a discount to your plans, plan subscriptions, beOS Pro memberships, and more.
::: tip NOTE
Trial credits or coupons are non-refundable. If you request a refund, the system will only refund your actual payment.
@@ -49,9 +49,9 @@ Trial credits or coupons are non-refundable. If you request a refund, the system
## FAQs
-### Will I be charged if someone accesses the WordPress site deployed on Olares?
+### Will I be charged if someone accesses the WordPress site deployed on beOS Pro?
-Yes, charges will occur from both Cloudflare for the traffic going through Cloudflare FRP tunnel. It mainly helps to hide the real IP of Olares and provides security protection against Distributed Denial of Service (DDoS) and other threats. If you host Olares on the cloud, traffic fee from your chosen vendor will apply.
+Yes, charges will occur from both Cloudflare for the traffic going through Cloudflare FRP tunnel. It mainly helps to hide the real IP of beOS Pro and provides security protection against Distributed Denial of Service (DDoS) and other threats. If you host beOS Pro on the cloud, traffic fee from your chosen vendor will apply.
### What happens if my bill is less than $1?
diff --git a/docs/space/create-olares.md b/docs/space/create-olares.md
index 81b9e75e8..58cb49f36 100644
--- a/docs/space/create-olares.md
+++ b/docs/space/create-olares.md
@@ -1,31 +1,31 @@
---
outline: [2, 3]
-description: Set up your cloud based Olares instance in Olares Space. Configure system resources, monitor installation progress, and activate your instance with proper credentials.
+description: Set up your cloud based beOS Pro instance in Remote Space. Configure system resources, monitor installation progress, and activate your instance with proper credentials.
---
-# Create a cloud-based Olares
+# Create a cloud-based beOS Pro
-Cloud-based Olares offer a convenient deployment option, enabling you to set up an Olares environment without managing hardware directly.
-This section provides a step-by-step guide to creating and managing your cloud-based Olares.
+Cloud-based beOS Pro offer a convenient deployment option, enabling you to set up an beOS Pro environment without managing hardware directly.
+This section provides a step-by-step guide to creating and managing your cloud-based beOS Pro.
::: tip NOTE
-- The **Host Service** is currently in an invite-only beta phase. To access the cloud-based Olares, contact us for an invitation.
-- If you are looking for information about setting up a self-hosted Olares, refer to the [Getting Started Guide](../manual/get-started/index.md).
+- The **Host Service** is currently in an invite-only beta phase. To access the cloud-based beOS Pro, contact us for an invitation.
+- If you are looking for information about setting up a self-hosted beOS Pro, refer to the [Getting Started Guide](../manual/get-started/index.md).
:::
## Prerequisites
-Ensure you get an Olares ID to log in to Olares Space and activate the Olares instance.
+Ensure you get an beOS ID to log in to Remote Space and activate the beOS Pro instance.
-## Create an Olares
+## Create an beOS Pro
-1. Log in to [Olares Space](https://space.olares.com/) by scanning the QR code using LarePass.
+1. Log in to [Remote Space](https://space.beos.local/) by scanning the QR code using beOS Pro app.
2. Navigate to the **Cluster** page and select the second option to start creating.
3. Configure the environment for installation as below:
- **Select Cloud Provider**: Choose a cloud service provider and the data center location closest to your users or workloads.
- **Hardware Configuration**: Select the instance's CPU, RAM, and storage resources.
- - **Olares Version & Kubernetes Setup**: Choose the appropriate version of Olares and the Kubernetes/K3S solution to be installed.
+ - **beOS Pro Version & Kubernetes Setup**: Choose the appropriate version of beOS Pro and the Kubernetes/K3S solution to be installed.
:::tip
If you intend to host large language models (LLMs), select the **Alibaba Cloud Hong Kong** region. Currently, it is the only region that offers instances with shared GPU services.
@@ -43,7 +43,7 @@ Ensure you get an Olares ID to log in to Olares Space and activate the Olares in
## Monitor installation
-The creation and installation of your cloud-based Olares typically take around 10 minutes. During this time, you can monitor the progress and logs in real-time.
+The creation and installation of your cloud-based beOS Pro typically take around 10 minutes. During this time, you can monitor the progress and logs in real-time.
### System statuses
@@ -73,14 +73,14 @@ The installation follows several key stages, represented by different statuses:
Click **Log** to view detailed logs and monitor the installation process in real time.
-## Activate Olares
+## Activate beOS Pro
-When the installation enters the **Pending Activation** state, activate Olares:
+When the installation enters the **Pending Activation** state, activate beOS Pro:
-1. Click **Activation**. A pop-up window will display Olares ID, one-time password, and a wizard URL.
+1. Click **Activation**. A pop-up window will display beOS ID, one-time password, and a wizard URL.
-2. Access the wizard URL in your browser, and use the one-time password to log into Olares for the first time.
-3. Change the Olares password via LarePass when prompted.
+2. Access the wizard URL in your browser, and use the one-time password to log into beOS Pro for the first time.
+3. Change the beOS Pro password via beOS Pro app when prompted.
4. Follow the on-screen instructions to finish the rest of activation process.
\ No newline at end of file
diff --git a/docs/space/host-domain.md b/docs/space/host-domain.md
index 356602775..a5457439e 100644
--- a/docs/space/host-domain.md
+++ b/docs/space/host-domain.md
@@ -1,35 +1,35 @@
---
outline: [2, 3]
-description: Set up custom domains in Olares Space with domain verification and DNS configuration. Create organizational Olares IDs and manage domain settings for your team.
+description: Set up custom domains in Remote Space with domain verification and DNS configuration. Create organizational beOS IDs and manage domain settings for your team.
---
# Set up a custom domain
-Whether you're an organizational user wanting employees to use a company-specific domain for login, or you simply wish to use a domain that you own, Olares Space allows you to set up a custom domain for easy access.
+Whether you're an organizational user wanting employees to use a company-specific domain for login, or you simply wish to use a domain that you own, Remote Space allows you to set up a custom domain for easy access.
-This guide walks you through adding your own domain for your Olares system on Olares Space.
+This guide walks you through adding your own domain for your beOS Pro system on Remote Space.
## Prerequisites
::: tip NOTE
-A new domain can only be bound if the account is in the DID stage. If the account has already been bound with an Olares ID, it means that the account is already associated with a Domain.
+A new domain can only be bound if the account is in the DID stage. If the account has already been bound with an beOS ID, it means that the account is already associated with a Domain.
:::
Before creating and configuring your own domain, make sure that:
-- **DID account status**: Ensure your account is in DID status (i.e., not yet bound to an Olares ID).
+- **DID account status**: Ensure your account is in DID status (i.e., not yet bound to an beOS ID).
-- **Domain Name**: Ensure you have a domain name registered through a domain registrar. The domain should not already be bound to another account in Olares Space.
+- **Domain Name**: Ensure you have a domain name registered through a domain registrar. The domain should not already be bound to another account in Remote Space.
-- **LarePass app**: Make sure the LarePass app is installed on your phone, as it is required for Verifiable Credential and domain management tasks.
+- **beOS Pro app app**: Make sure the beOS Pro app app is installed on your phone, as it is required for Verifiable Credential and domain management tasks.
- **Access to the DNS settings of your domain**: This is for configuring the TXT record and NS record.
## Add your domain
-When you have everything ready, take the steps below to add your domain in Olares Space.
+When you have everything ready, take the steps below to add your domain in Remote Space.
-1. In the Olares Space console, navigate to **Domain** > **Domain Name Setup**, and enter your custom domain as instructed.
+1. In the Remote Space console, navigate to **Domain** > **Domain Name Setup**, and enter your custom domain as instructed.
@@ -37,7 +37,7 @@ When you have everything ready, take the steps below to add your domain in Olare
-3. Add NS records to allow Olares Space to configure DNS for your domain.
+3. Add NS records to allow Remote Space to configure DNS for your domain.
@@ -48,23 +48,23 @@ When you have everything ready, take the steps below to add your domain in Olare
-4. Launch your LarePass app, and navigate to **Organization Olares ID** > **Create an Organization**. You should see your domain listed.
+4. Launch your beOS Pro app app, and navigate to **Organization beOS ID** > **Create an Organization**. You should see your domain listed.
-5. Click on the domain name to store the domain name on blockchain. When it's done, the domain setup status should change to **Awaiting rule configuration** on Olares Space.
+5. Click on the domain name to store the domain name on blockchain. When it's done, the domain setup status should change to **Awaiting rule configuration** on Remote Space.
-So far you have successfully associated your domain with your DID. You can now continue to [set the email invitation rule](manage-domain.md#set-email-invitation-rules) and create an organization Olares ID using the domain.
+So far you have successfully associated your domain with your DID. You can now continue to [set the email invitation rule](manage-domain.md#set-email-invitation-rules) and create an organization beOS ID using the domain.
-## Create an Org Olares ID
+## Create an Org beOS ID
-Now that your organization has a verified domain name, you or other members you invite can create an Olares ID using this domain.
+Now that your organization has a verified domain name, you or other members you invite can create an beOS ID using this domain.
-1. In the LarePass app, navigate to **Organization Olares ID** > **Join an existing organization**.
+1. In the beOS Pro app app, navigate to **Organization beOS ID** > **Join an existing organization**.
2. Enter your organization's domain name and click **Continue**. Recheck whether your domain name has been verified and configured if an error occurs.
3. Bind the VC via your email accounts. Currently, only Gmail and Google Workspace email are supported.
-Upon completion, you will receive an Organization Olares ID. Now you can go ahead to [Activate Olares](../manual/get-started/activate-olares).
+Upon completion, you will receive an Organization beOS ID. Now you can go ahead to [Activate beOS Pro](../manual/get-started/activate-olares).
## Domain status and processing
@@ -79,5 +79,5 @@ The table below explains different domain statuses and the corresponding actions
| Awaiting the application for the domain's Verifiable Credential | Complete blockchain domain application on mobile |
| Awaiting submission of the domain's Verifiable Presentation | Complete blockchain domain application on mobile |
| Awaiting rule configuration | Set up email invitation rules for organization members |
-| Binding | Wait for binding with Olares, you can access the details page |
-| Allocated | Bound to Olares, you can access the details page |
\ No newline at end of file
+| Binding | Wait for binding with beOS Pro, you can access the details page |
+| Allocated | Bound to beOS Pro, you can access the details page |
\ No newline at end of file
diff --git a/docs/space/index.md b/docs/space/index.md
index 4f83d1a7e..b7795c8e3 100644
--- a/docs/space/index.md
+++ b/docs/space/index.md
@@ -1,23 +1,23 @@
---
-description: Discover Olares Space platform for managed cloud hosting of Olares instances. Explore infrastructure services, host services, account management, and billing features for efficient cloud deployment.
+description: Discover Remote Space platform for managed cloud hosting of beOS Pro instances. Explore infrastructure services, host services, account management, and billing features for efficient cloud deployment.
---
-# Olares Space overview
+# Remote Space overview
-Olares Space is the fully managed offering of Olares on public clouds. It provides two categories of services:
+Remote Space is the fully managed offering of beOS Pro on public clouds. It provides two categories of services:
- **Infrastructure service** – Manages data backup, custom domain configuration, reverse proxy, and shared GPU resources.
-- **Host service** – Hosts and manage Olares instances on public cloud platforms.
+- **Host service** – Hosts and manage beOS Pro instances on public cloud platforms.
-Olares Space account is associated with your Olares IDs or DIDs. You can log in to Olares Space by scanning QR code using LarePass.
+Remote Space account is associated with your beOS IDs or DIDs. You can log in to Remote Space by scanning QR code using beOS Pro app.
-This section walks you through usages of Olares Space, covering:
+This section walks you through usages of Remote Space, covering:
-- [Log in to/off Olares Space](manage-accounts.md)
-- [Host Olares](create-olares.md)
-- [Manage Olares](manage-olares.md)
+- [Log in to/off Remote Space](manage-accounts.md)
+- [Host beOS Pro](create-olares.md)
+- [Manage beOS Pro](manage-olares.md)
- [Host custom domains](host-domain.md)
- [Manage organization domains](manage-domain.md)
-- [Back up & Restore Olares](backup-restore.md)
+- [Back up & Restore beOS Pro](backup-restore.md)
- [Usage and Billing](billing.md)
diff --git a/docs/space/manage-accounts.md b/docs/space/manage-accounts.md
index e71c9a6ef..d5579f60b 100644
--- a/docs/space/manage-accounts.md
+++ b/docs/space/manage-accounts.md
@@ -1,22 +1,22 @@
---
-description: Learn how to access and manage Olares Space accounts using LarePass authentication.
+description: Learn how to access and manage Remote Space accounts using beOS Pro app authentication.
---
-# Manage accounts in Olares Space
+# Manage accounts in Remote Space
-This guide walks you through common account operations with Olares Space, including logging in, managing multiple accounts, and logging out.
+This guide walks you through common account operations with Remote Space, including logging in, managing multiple accounts, and logging out.
-## Log in to Olares Space
+## Log in to Remote Space
-Olares Space uses a decentralized ID (DID) or Olares ID for authentication. Make sure you already have obtained your credentials on your LarePass.
+Remote Space uses a decentralized ID (DID) or beOS ID for authentication. Make sure you already have obtained your credentials on your beOS Pro app.
-1. In the LarePass app, select the DID or Olares ID you wish to use to log in.
-2. Open https://space.olares.com/ in your browser.
-3. Scan the QR code using LarePass.
+1. In the beOS Pro app app, select the DID or beOS ID you wish to use to log in.
+2. Open https://space.beos.local/ in your browser.
+3. Scan the QR code using beOS Pro app.
::: tip NOTE
-The features and services available on Olares Space vary depending on whether you use a DID or Olares ID for login.
-- **Logging in with a DID** allows you to set your own domain since no domain is associated to the account. However, you must bind the DID to an Olares ID before you can activate an Olares device.
-- **Logging in with an Olares ID** enables you to create an Olares, provided the name isn't already linked to another Olares device. However, you cannot use your custom domain since your Olares ID already corresponds to a unique domain.
+The features and services available on Remote Space vary depending on whether you use a DID or beOS ID for login.
+- **Logging in with a DID** allows you to set your own domain since no domain is associated to the account. However, you must bind the DID to an beOS ID before you can activate an beOS Pro device.
+- **Logging in with an beOS ID** enables you to create an beOS Pro, provided the name isn't already linked to another beOS Pro device. However, you cannot use your custom domain since your beOS ID already corresponds to a unique domain.
:::
@@ -35,13 +35,13 @@ Alternatively, you can:
## Manage multiple accounts
-Each Olares ID is linked to only one Olares. With multi-account management in Olares Space, you can switch between accounts effortlessly — perfect for managing multiple Olares IDs and instances.
+Each beOS ID is linked to only one beOS Pro. With multi-account management in Remote Space, you can switch between accounts effortlessly — perfect for managing multiple beOS IDs and instances.
To add an account:
1. Click your avatar in the top-right corner.
2. In the pop-up menu, select **Import Account**.
-3. Launch LarePass, and scan the QR code to log in.
+3. Launch beOS Pro app, and scan the QR code to log in.
Once you've added multiple accounts, switch between them using the **Switch Account** option in the menu. If the account is logged out, you'll be redirected to the QR code login page.
diff --git a/docs/space/manage-domain.md b/docs/space/manage-domain.md
index a2198e1db..422ff737b 100644
--- a/docs/space/manage-domain.md
+++ b/docs/space/manage-domain.md
@@ -1,26 +1,26 @@
---
outline: [2, 3]
-description: Configure domain settings in Olares Space with email invitation rules and member management. Administrate organizational Olares IDs for seamless team collaboration.
+description: Configure domain settings in Remote Space with email invitation rules and member management. Administrate organizational beOS IDs for seamless team collaboration.
---
# Manage your domain
-You must [add a domain](host-domain.md#add-your-domain) before managing it. Once your domain is set up, you can configure email invitation rules for organization members and invite them to create their own organizational **Olares ID** via email.
+You must [add a domain](host-domain.md#add-your-domain) before managing it. Once your domain is set up, you can configure email invitation rules for organization members and invite them to create their own organizational **beOS ID** via email.
## Set email invitation rules
-Most companies use a standard domain suffix for their team members' emails, like `A@myteam.com` for person A or `B@myteam.com` for person B. However, sometimes, team members might use emails in different domains. To accommodate these scenarios, Olares provides two types of rules for adding organization members' emails:
+Most companies use a standard domain suffix for their team members' emails, like `A@myteam.com` for person A or `B@myteam.com` for person B. However, sometimes, team members might use emails in different domains. To accommodate these scenarios, beOS Pro provides two types of rules for adding organization members' emails:
-- **Fixed email suffix**: Use this option when all team members share the same email domain. Enter your organization's domain suffix (example: @company.com). Any email matching this suffix can be associated with your organization's Olares ID.
+- **Fixed email suffix**: Use this option when all team members share the same email domain. Enter your organization's domain suffix (example: @company.com). Any email matching this suffix can be associated with your organization's beOS ID.
- **Specified email address**: Use this option if your organization doesn't have a corporate email suffix. You need to manually add the email address for each member of the organization.
:::info NOTE
- Currently, only Gmail is supported for both rule types.
-- Emails that have been used to create organizational Olares IDs will appear in the member list and cannot be deleted.
-- Emails that are manually added and have not been used to create the Olares ID appear as "unbound" and can be removed.
+- Emails that have been used to create organizational beOS IDs will appear in the member list and cannot be deleted.
+- Emails that are manually added and have not been used to create the beOS ID appear as "unbound" and can be removed.
:::
## Manage members
@@ -34,8 +34,8 @@ After setting email rules, you can add or remove members under your organization
To add a member:
1. On the domain management page, add members to the organization by entering their email address.
-2. Notify the corresponding users to use their email addresses to [create an organizational Olares ID](host-domain.md#create-an-org-olares-id).
+2. Notify the corresponding users to use their email addresses to [create an organizational beOS ID](host-domain.md#create-an-org-olares-id).
### Remove a member
-You can remove email addresses that haven't been used to create an Olares ID. Once an email address is associated with an organization's Olares ID, it cannot be removed.
\ No newline at end of file
+You can remove email addresses that haven't been used to create an beOS ID. Once an email address is associated with an organization's beOS ID, it cannot be removed.
\ No newline at end of file
diff --git a/docs/space/manage-olares.md b/docs/space/manage-olares.md
index 16d46bc82..87a7ce5fa 100644
--- a/docs/space/manage-olares.md
+++ b/docs/space/manage-olares.md
@@ -1,42 +1,42 @@
---
outline: [2, 3]
-description: Control your Olares instances through system monitoring, worker node management, and shared GPU solutions. Track storage usage, traffic consumption and maintain instance health.
+description: Control your beOS Pro instances through system monitoring, worker node management, and shared GPU solutions. Track storage usage, traffic consumption and maintain instance health.
---
-# Manage Olares
+# Manage beOS Pro
-This page covers Olares management tasks in Olares Space, including monitoring system data, adding worker nodes, and managing cloud services.
+This page covers beOS Pro management tasks in Remote Space, including monitoring system data, adding worker nodes, and managing cloud services.
## View system status
-You can monitor the system status of Olares through **Olares Space**:
+You can monitor the system status of beOS Pro through **Remote Space**:
-1. In your LarePass app, go to **Settings** > **Integration**.
-2. Click add in the top right corner and link your Olares Space account to the Olares device. This authorizes Olares Space's access to your system data.
-3. Log into [**Olares Space**](https://space.olares.com/).
-4. On the **Olares** page, view **Storage usage** and **Traffic consumption** in the system panel.
+1. In your beOS Pro app app, go to **Settings** > **Integration**.
+2. Click add in the top right corner and link your Remote Space account to the beOS Pro device. This authorizes Remote Space's access to your system data.
+3. Log into [**Remote Space**](https://space.beos.local/).
+4. On the **beOS Pro** page, view **Storage usage** and **Traffic consumption** in the system panel.
:::info
-For self-hosted Olares users, it's important to monitor **Traffic statistics** for intranet penetration services, and **Storage usage** for backup services. These services may incur charges based on usage.
+For self-hosted beOS Pro users, it's important to monitor **Traffic statistics** for intranet penetration services, and **Storage usage** for backup services. These services may incur charges based on usage.
:::
## Add worker nodes
-For cloud Olares users, you can improve performance by adding worker nodes:
+For cloud beOS Pro users, you can improve performance by adding worker nodes:
1. Click more_horiz in the upper right corner, and select **Add Worker**.
2. On the guide page, choose your preferred hardware configuration.
3. Review the fees for storage and traffic.
4. Confirm your order and submit.
-## Return Olares
+## Return beOS Pro
-If you no longer need your Olares service, you can return the instance by following these steps:
+If you no longer need your beOS Pro service, you can return the instance by following these steps:
1. Click more_horiz in the upper right corner.
-2. Select **Destroy Olares**.
+2. Select **Destroy beOS Pro**.
3. Confirm the action and settle your usage:
- If you are eligible for a refund, the amount will be credited back to your account balance.
- If additional payment is required, please confirm and settle the payment.
diff --git a/docs/use-cases/ace-step.md b/docs/use-cases/ace-step.md
index 56914a5a1..4b70f4249 100644
--- a/docs/use-cases/ace-step.md
+++ b/docs/use-cases/ace-step.md
@@ -1,18 +1,18 @@
---
outline: [2, 3]
-description: Step-by-step guide to installing ACE-Step AI on Olares, generating songs with lyrics or instrumentals, optimizing audio with retake and repainting, and using Audio2Audio to transform reference audio into new music.
+description: Step-by-step guide to installing ACE-Step AI on beOS Pro, generating songs with lyrics or instrumentals, optimizing audio with retake and repainting, and using Audio2Audio to transform reference audio into new music.
---
# Create your own AI-generated music with ACE-Step
ACE-Step, developed by ACE Studio and StepFun, is an open-source model that generates music from the lyrics and style tags you provide, allowing you to create songs, vocals, and instrumentals from simple text inputs. With its built-in tools, you can also refine your tracks by adjusting or regenerating specific parts without starting over.
-This guide shows you how to install ACE-Step on Olares, generate your first track, explore different musical styles, and enhance your audio using the editing features built into the app.
+This guide shows you how to install ACE-Step on beOS Pro, generate your first track, explore different musical styles, and enhance your audio using the editing features built into the app.
## Learning objectives
By the end of this tutorial, you will learn how to:
-- Install ACE-Step on your Olares device.
+- Install ACE-Step on your beOS Pro device.
- Generate songs with lyrics, tags, and stylistic controls.
- Locate and download your generated audio files.
- Refine tracks by adjusting the style, editing sections, extending the song, or using a reference clip to reshape it.
@@ -20,17 +20,17 @@ By the end of this tutorial, you will learn how to:
## Prerequisites
Before you begin, make sure:
-- Olares running on a machine equipped with an NVIDIA GPU.
+- beOS Pro running on a machine equipped with an NVIDIA GPU.
## Install and set up ACE-Step
-With your Olares device ready, follow these steps to install ACE-Step and begin generating music.
+With your beOS Pro device ready, follow these steps to install ACE-Step and begin generating music.
### Install ACE-Step
Follow these steps to install ACE-Step.
-1. Open the **Market** app in your Olares web interface.
+1. Open the **Market** app in your beOS Pro web interface.
2. Use the search bar and type "ACE-Step".
3. Click **Get**, then click **Install**.
@@ -40,7 +40,7 @@ Follow these steps to install ACE-Step.
Once installation finishes, open ACE-Step from Launchpad.
-Olares will automatically download and install required models. A **Download Manager** window will appear, showing model size and download progress.
+beOS Pro will automatically download and install required models. A **Download Manager** window will appear, showing model size and download progress.
{width=500}
After the download completes, the ACE-Step generation interface will open automatically.
@@ -83,7 +83,7 @@ You can save your generated music via two methods:
- **Direct download**: Click the download button in the upper right corner to save the audio file directly to your local device.
-- **From Olares Files**:
+- **From beOS Pro Files**:
1. Open **Files**.
2. Go to the following path: `/Home/AI/output/acestepv2`.
3. Right-click the generated audio file and save it to your local device.
diff --git a/docs/use-cases/comfyui-for-krita.md b/docs/use-cases/comfyui-for-krita.md
index a166f19ae..a01534a6e 100644
--- a/docs/use-cases/comfyui-for-krita.md
+++ b/docs/use-cases/comfyui-for-krita.md
@@ -1,27 +1,27 @@
---
-description: Learn how to integrate ComfyUI with Krita for AI-powered digital art creation. Step-by-step guide to setting up and connecting ComfyUI in Olares with Krita for seamless creative workflows.
+description: Learn how to integrate ComfyUI with Krita for AI-powered digital art creation. Step-by-step guide to setting up and connecting ComfyUI in beOS Pro with Krita for seamless creative workflows.
---
# AI art creation with ComfyUI and Krita
-Running ComfyUI locally on Olares gives you the flexibility of server-side AI processing, but making it work seamlessly with your creative tools requires additional steps. Instead of confining ComfyUI to a single device, Olares allows you to extend its functionality to other machines, enabling smooth integration with tools such as Krita for editing and refinement.
+Running ComfyUI locally on beOS Pro gives you the flexibility of server-side AI processing, but making it work seamlessly with your creative tools requires additional steps. Instead of confining ComfyUI to a single device, beOS Pro allows you to extend its functionality to other machines, enabling smooth integration with tools such as Krita for editing and refinement.
-This tutorial will show you how to connect a locally hosted ComfyUI instance on Olares to Krita running on a separate computer. By combining the power of ComfyUI with Krita, you'll be able to create a streamlined, AI-driven workflow that fits naturally into your creative process.
+This tutorial will show you how to connect a locally hosted ComfyUI instance on beOS Pro to Krita running on a separate computer. By combining the power of ComfyUI with Krita, you'll be able to create a streamlined, AI-driven workflow that fits naturally into your creative process.
## Objectives
In this tutorial, you will learn how to:
-- Deploy and configure ComfyUI in Olares to maximize performance and resource efficiency.
+- Deploy and configure ComfyUI in beOS Pro to maximize performance and resource efficiency.
- Integrate ComfyUI with Krita to create AI-generated artwork seamlessly.
## Understanding the components
Your AI art studio consists of three key pieces working together:
-* **ComfyUI**: The AI engine running in your Olares environment that powers image generation.
+* **ComfyUI**: The AI engine running in your beOS Pro environment that powers image generation.
* **Krita**: Professional-grade digital art software where you'll create and edit your artwork.
* **Krita AI Diffusion Plugin**: The connector that enables seamless communication between Krita and ComfyUI.
## What you'll need
Before starting, ensure you have:
-* A working Olares installation with internet access
-* A computer connected to the same local network as Olares
+* A working beOS Pro installation with internet access
+* A computer connected to the same local network as beOS Pro
* Sufficient system resources (recommended: 16GB RAM for optimal performance)
## Set up ComfyUI
@@ -43,7 +43,7 @@ Before starting, ensure you have:
4. Launch ComfyUI from your desktop, and verify the installation by generating a sample image.
5. Copy the address of ComfyUI for next steps.
:::tip
-For security, you should always run AI applications with [LarePass VPN enabled](../manual/larepass/private-network.md).
+For security, you should always run AI applications with [beOS Pro app VPN enabled](../manual/larepass/private-network.md).
:::
## Set up Krita
@@ -73,11 +73,11 @@ Establish a secure connection between Krita and ComfyUI:
:::info
If connection fails:
- - Verify network connectivity between your computer and Olares.
+ - Verify network connectivity between your computer and beOS Pro.
- Confirm ComfyUI's authentication level is set to "Internal".
- - Confirm LarePass VPN is enabled.
+ - Confirm beOS Pro app VPN is enabled.
- Check for and disable any interfering proxy services.
- - Ensure ComfyUI is running correctly on your Olares.
+ - Ensure ComfyUI is running correctly on your beOS Pro.
:::
5. Adjust ComfyUI settings.
diff --git a/docs/use-cases/comfyui-launcher.md b/docs/use-cases/comfyui-launcher.md
index 06e3ae636..c66248a2d 100644
--- a/docs/use-cases/comfyui-launcher.md
+++ b/docs/use-cases/comfyui-launcher.md
@@ -1,6 +1,6 @@
---
outline: [2, 3]
-description: Administrators' guide for managing ComfyUI on Olares with ComfyUI Launcher—covering a quick preflight network check, service control, network configuration, model storage and installation, plugin management, Python dependencies, and maintenance.
+description: Administrators' guide for managing ComfyUI on beOS Pro with ComfyUI Launcher—covering a quick preflight network check, service control, network configuration, model storage and installation, plugin management, Python dependencies, and maintenance.
---
# Manage ComfyUI using ComfyUI Launcher
@@ -71,7 +71,7 @@ Clicking any of these entries opens the Files app directly in the corresponding
### Understand the `model` directory structure
-ComfyUI in Olares uses a file structure that differs from the standard installation. This change allows models to be shared between ComfyUI and SD Web UI.
+ComfyUI in beOS Pro uses a file structure that differs from the standard installation. This change allows models to be shared between ComfyUI and SD Web UI.
When uploading external models manually or selecting a destination in **Custom Download**, it is important to place files into the correct subfolder.
diff --git a/docs/use-cases/comfyui.md b/docs/use-cases/comfyui.md
index fedb0f97a..2432e6b79 100644
--- a/docs/use-cases/comfyui.md
+++ b/docs/use-cases/comfyui.md
@@ -1,5 +1,5 @@
---
-description: Discover how to install ComfyUI, a node-based interface for Stable Diffusion, with ease in Olares. Create reusable workflows, fine-tune image generation, and apply advanced post-processing effects.
+description: Discover how to install ComfyUI, a node-based interface for Stable Diffusion, with ease in beOS Pro. Create reusable workflows, fine-tune image generation, and apply advanced post-processing effects.
---
# ComfyUI
@@ -19,17 +19,17 @@ ComfyUI puts advanced AI image generation capabilities at your fingertips:
## Install ComfyUI Shared
-Olares provides ComfyUI Shared to allow multiple users to share models, plugins, and workflow resources within the cluster. It also features ComfyUI Launcher, providing administrator users with a simple way to manage ComfyUI resources and runtime environments.
+beOS Pro provides ComfyUI Shared to allow multiple users to share models, plugins, and workflow resources within the cluster. It also features ComfyUI Launcher, providing administrator users with a simple way to manage ComfyUI resources and runtime environments.
::: tip Note
-Starting from Olares 1.11.6, Shared applications will replace previous cluster-scoped applications. If you have installed ComfyUI for Cluster and its client, please uninstall them before installing ComfyUI Shared.
+Starting from beOS Pro 1.11.6, Shared applications will replace previous cluster-scoped applications. If you have installed ComfyUI for Cluster and its client, please uninstall them before installing ComfyUI Shared.
:::
To install ComfyUI Shared:
-1. Open Olares Market, find **ComfyUI Shared**, and click **Get**.
+1. Open beOS Pro Market, find **ComfyUI Shared**, and click **Get**.
- - The administrator will see two icons on the Olares desktop: one is the client interface for ComfyUI, and the other is ComfyUI Launcher.
+ - The administrator will see two icons on the beOS Pro desktop: one is the client interface for ComfyUI, and the other is ComfyUI Launcher.
{width=40%}
diff --git a/docs/use-cases/deerflow.md b/docs/use-cases/deerflow.md
index b18d725a1..d4ef6c409 100644
--- a/docs/use-cases/deerflow.md
+++ b/docs/use-cases/deerflow.md
@@ -1,12 +1,12 @@
---
outline: [2, 3]
-description: Learn how to set up DeerFlow on your Olares device, complete with Ollama integration and Tavily for web research.
+description: Learn how to set up DeerFlow on your beOS Pro device, complete with Ollama integration and Tavily for web research.
---
# Build a local deep research agent with DeerFlow
DeerFlow is an open-source framework that transforms a simple research topic into a comprehensive, detailed report.
-This guide will walk through the process of setting up DeerFlow on your Olares device, integrating it with a local Ollama model and the Tavily search engine for web-enabled research.
+This guide will walk through the process of setting up DeerFlow on your beOS Pro device, integrating it with a local Ollama model and the Tavily search engine for web-enabled research.
## Learning objectives
In this guide, you will learn how to:
@@ -16,7 +16,7 @@ In this guide, you will learn how to:
## Prerequisites
Before you begin, make sure:
-- Ollama is installed and running in your Olares environment.
+- Ollama is installed and running in your beOS Pro environment.
- At least one model installed using Ollama. See [Ollama](./ollama.md) for details.
- You have a [Tavily](https://www.tavily.com/) account (a free account is sufficient).
@@ -48,7 +48,7 @@ DeerFlow requires connection details for the LLM. You will configure this by edi
For example:
```yaml
BASIC_MODEL:
- base_url: https://39975b9a1.{YOURUSERNAME}.olares.com/v1
+ base_url: https://39975b9a1.{YOURUSERNAME}.beos.local/v1
model: "cogito:14b"
api_key: ollama
```
@@ -68,7 +68,7 @@ You can edit the configuration file directly on the host machine via the termina
4. Copy this path.
-5. Open the Olares terminal from Control Hub, and change directory to the copied path:
+5. Open the beOS Pro terminal from Control Hub, and change directory to the copied path:
```bash
# Replace with your actual path
cd /olares/rootfs/userspace/pvc-userspace-laresprime-raizlofhiszoin5c/Data/deerflow/app
@@ -87,7 +87,7 @@ You can edit the configuration file directly on the host machine via the termina
For example:
```yaml
BASIC_MODEL:
- base_url: https://39975b9a1.{YOURUSERNAME}.olares.com/v1
+ base_url: https://39975b9a1.{YOURUSERNAME}.beos.local/v1
model: "cogito:14b"
api_key: ollama
```
@@ -124,7 +124,7 @@ Restart the service to apply the new model and search configurations.
## Run DeerFlow
### Run a deep research task
-1. Open **DeerFlow** from the Olares Launchpad.
+1. Open **DeerFlow** from the beOS Pro Launchpad.
2. Click **Get Started** and enter your research topic in the prompt box.
diff --git a/docs/use-cases/dify.md b/docs/use-cases/dify.md
index 0e6b74875..2ff806084 100644
--- a/docs/use-cases/dify.md
+++ b/docs/use-cases/dify.md
@@ -1,13 +1,13 @@
---
-description: Guide to leveraging Dify on Olares for building AI applications. Learn how to deploy Dify and add personal knowledge base with ease.
+description: Guide to leveraging Dify on beOS Pro for building AI applications. Learn how to deploy Dify and add personal knowledge base with ease.
---
# Customize your local AI assistant using Dify
-Dify is an AI application development platform. It's one of the key open-source projects that Olares integrates to help you build and manage AI applications while maintaining full data ownership. Additionally, you can integrate your personal knowledge base documents into Dify for more personalized interactions.
+Dify is an AI application development platform. It's one of the key open-source projects that beOS Pro integrates to help you build and manage AI applications while maintaining full data ownership. Additionally, you can integrate your personal knowledge base documents into Dify for more personalized interactions.
## Before you begin
To use local AI models on Dify, ensure you have:
-- [Ollama installed](ollama.md) and running in your Olares environment.
+- [Ollama installed](ollama.md) and running in your beOS Pro environment.
- LassPass installed and [VPN enabled](../manual/larepass/private-network.md#enable-vpn-on-larepass) on your device.
- [Open WebUI installed](openwebui.md) with your preferred language models downloaded.
:::tip
@@ -16,10 +16,10 @@ To use local AI models on Dify, ensure you have:
## Install Dify
:::info
-Starting from Olares 1.11.6, if "Dify For Cluster" or "Dify" was previously installed, uninstall them before proceeding.
+Starting from beOS Pro 1.11.6, if "Dify For Cluster" or "Dify" was previously installed, uninstall them before proceeding.
:::
-1. Install "Dify Shared" from Olares Market.
+1. Install "Dify Shared" from beOS Pro Market.
2. Launch Dify from your desktop. Please ensure the admin has already installed Dify Shared.
## Create an AI assistant app
@@ -39,7 +39,7 @@ Starting from Olares 1.11.6, if "Dify For Cluster" or "Dify" was previously inst
2. In Dify, navigate to **Settings** > **Model Provider**.
3. Select Ollama as the model provider, with the following configurations:
- **Model Name**: Enter the model name. For example: `gemma2`.
- - **Base URL**: Enter Ollama's local address: `https://39975b9a1.{username}.olares.com`. Replace `{username}` with the Olares Admin's local name. For example, `https://39975b9a1.marvin123.olares.com`.
+ - **Base URL**: Enter Ollama's local address: `https://39975b9a1.{username}.beos.local`. Replace `{username}` with the beOS Pro Admin's local name. For example, `https://39975b9a1.marvin123.beos.local`.
{width=70%}
@@ -60,7 +60,7 @@ Starting from Olares 1.11.6, if "Dify For Cluster" or "Dify" was previously inst
## Set up local knowledge base
1. In Dify, navigate to the **Knowledge** tab.
-2. Locate your default knowledge base. It will be named after your Olares ID and monitors the `/Documents` folder in Files.
+2. Locate your default knowledge base. It will be named after your beOS ID and monitors the `/Documents` folder in Files.
3. Enter `/Documents` and add documents to the knowledge base.
diff --git a/docs/use-cases/duix-avatar.md b/docs/use-cases/duix-avatar.md
index 969ac4ba0..06fac4496 100644
--- a/docs/use-cases/duix-avatar.md
+++ b/docs/use-cases/duix-avatar.md
@@ -1,24 +1,24 @@
---
outline: [2, 3]
-description: Learn to deploy Duix.Avatar on Olares, from model training to video synthesis, to create text-driven digital avatar videos.
+description: Learn to deploy Duix.Avatar on beOS Pro, from model training to video synthesis, to create text-driven digital avatar videos.
---
# Create a digital avatar with Duix.Avatar
Duix.Avatar (formerly HeyGem) is an open-source AI toolkit for generating digital avatars, specializing in offline video creation and digital cloning.
-This guide walks you through deploying and using Duix.Avatar on Olares, covering the complete process from model training to video synthesis to generate a text-driven digital avatar video.
+This guide walks you through deploying and using Duix.Avatar on beOS Pro, covering the complete process from model training to video synthesis to generate a text-driven digital avatar video.
## Learning objectives
In this guide, you will learn how to:
- Prepare and process video and audio assets for digital avatar cloning.
-- Use Hoppscotch on Olares to call the Duix.Avatar API collection to train a model, synthesize audio, and create a video.
+- Use Hoppscotch on beOS Pro to call the Duix.Avatar API collection to train a model, synthesize audio, and create a video.
## Prerequisites
Before you begin, ensure the following:
-- Olares 1.11 or later.
-- Olares running on a machine equipped with an NVIDIA GPU.
+- beOS Pro 1.11 or later.
+- beOS Pro running on a machine equipped with an NVIDIA GPU.
## Install Duix.Avatar
1. In **Market**, search for "Duix.Avatar".
@@ -49,7 +49,7 @@ To follow this guide using the `ffmpeg` command, ensure it is installed on your
This creates two new files in the same folder:
- `output_video.mp4` (silent video)
- `output_audio.wav` (audio)
-2. The Duix.Avatar service reads files from specific directories. Upload the two files you just generated to their designated locations in the Olares **Files** app.
+2. The Duix.Avatar service reads files from specific directories. Upload the two files you just generated to their designated locations in the beOS Pro **Files** app.
1. Upload `output_audio.wav` to:
```plain
/Data/heygem/voice/data/
@@ -65,9 +65,9 @@ To follow this guide using the `ffmpeg` command, ensure it is installed on your
A pre-configured Hoppscotch collection is available to simplify the API calls.
1. Run the following command in your terminal to download the API collection file:
```bash
- curl -o duix.avatar.json https://cdn.olares.com/app/demos/en/duix/duix.avatar.json
+ curl -o duix.avatar.json https://cdn.beos.local/app/demos/en/duix/duix.avatar.json
```
-2. Open the Hoppscotch app in Olares.
+2. Open the Hoppscotch app in beOS Pro.
3. In the collections panel on the right, click **Import** > **Import from Hoppscotch**, and select the `duix.avatar.json` file you just downloaded.
@@ -77,14 +77,14 @@ After importing, you will see a new collection named `duix.avatar` containing fo
## Train data via API
Now you will call the four APIs in sequence to generate the digital avatar.
:::tip
-The Duix.Avatar API address is tied to your Olares ID. In all of the following API requests, you must replace `` in the URL with your own Olares ID prefix. For example, if your Olares access URL is `https://app.alice123.olares.com`, your prefix is `alice123`.
+The Duix.Avatar API address is tied to your beOS ID. In all of the following API requests, you must replace `` in the URL with your own beOS ID prefix. For example, if your beOS Pro access URL is `https://app.alice123.beos.local`, your prefix is `alice123`.
:::
### Step 1: Model training
This step preprocesses your uploaded audio, extracting features to prepare for voice cloning.
1. In Hoppscotch, expand the `duix.avatar` collection and select **1. Model training**.
-2. Modify the request URL, replacing `` with your Olares ID's prefix.
+2. Modify the request URL, replacing `` with your beOS ID's prefix.
:::info
The request body is pre-set to point to the `output_audio.wav` file you uploaded, so you don't need to change it.
:::
@@ -95,7 +95,7 @@ This step preprocesses your uploaded audio, extracting features to prepare for v
### Step 2: Audio synthesis
This step uses the voice model you trained in Step 1 to synthesize new audio from a text prompt.
1. Click **2. Audio synthesis**.
-2. Modify the Olares ID in the request URL.
+2. Modify the beOS ID in the request URL.
3. In the request body, modify the following fields:
* `text`: Enter the text you want the digital avatar to speak.
* `reference_audio`: Paste the `asr_format_audio_url` value from Step 1.
@@ -109,7 +109,7 @@ This step uses the voice model you trained in Step 1 to synthesize new audio fro
6. Rename the downloaded file to `new.mp3`. In the same folder, convert it to `.wav` with `ffmpeg`:
- ```bashß
+ ```bash
ffmpeg -i new.mp3 new.wav
```
7. Upload the new `new.wav` file to:
@@ -122,7 +122,7 @@ This step uses the voice model you trained in Step 1 to synthesize new audio fro
Now you will use your synthesized audio (`new.wav`) together with your original silent video (`output_video.mp4`) to synthesize the final avatar.
1. Click **3. Video synthesis**.
-2. Modify the Olares ID in the request URL.
+2. Modify the beOS ID in the request URL.
3. In the request body, change the `code` field to a new, unique task identifier. You will use this ID to check the synthesis progress.
:::info
The `audio_url` and `video_url` in the request body are pre-set to `new.wav` and `output_video.mp4`, which match the files you uploaded. They do not need to be changed.
@@ -133,7 +133,7 @@ Now you will use your synthesized audio (`new.wav`) together with your original
### Step 4: Query video synthesis progress
Video synthesis is a time-consuming task. Use this to query its processing status.
1. Click **4. Query progress**.
-2. Modify the Olares ID in the request URL.
+2. Modify the beOS ID in the request URL.
3. In the **Params** section, change the `code` value to the unique identifier you set in Step 3.
4. Click **Send** to check the current progress.
5. Repeat this query until the `progress` field in the response reaches `100`, which indicates the video synthesis is complete.
@@ -141,7 +141,7 @@ Video synthesis is a time-consuming task. Use this to query its processing statu
:::tip
The time required for video synthesis depends on your GPU performance and video length. It may take several minutes or longer.
:::
-6. When successful, the `result` field in the response will contain the output video's filename. You can find the final generated video in the Olares Files app at:
+6. When successful, the `result` field in the response will contain the output video's filename. You can find the final generated video in the beOS Pro Files app at:
```plain
/Data/heygem/face2face-data/temp/
```
@@ -154,9 +154,8 @@ If the progress query stalls for a long time or an API returns an error, go to C
### API request fails
Confirm the following:
-- You have correctly replaced the default Olares ID (``) with your own ID in the request URL.
+- You have correctly replaced the default beOS ID (``) with your own ID in the request URL.
- All media files (`output_audio.wav`, `output_video.mp4`, `new.wav`) are uploaded to the correct directories with the exact filenames.
### Media is updated, but the old video is still generated
Ensure you are using a new, unique `code` parameter for the video synthesis. The system caches results, so reusing a `code` will return the previously cached video.
-
diff --git a/docs/use-cases/host-cloud-android.md b/docs/use-cases/host-cloud-android.md
index cf0f40f67..3a046e733 100644
--- a/docs/use-cases/host-cloud-android.md
+++ b/docs/use-cases/host-cloud-android.md
@@ -1,32 +1,32 @@
---
outline: [2, 3]
-description: Deploy a cloud Android emulator using redroid on Olares, and access the Android host from macOS and Windows via adb and scrcpy.
+description: Deploy a cloud Android emulator using redroid on beOS Pro, and access the Android host from macOS and Windows via adb and scrcpy.
---
# Host your cloud Android with redroid
-[redroid](https://github.com/remote-android/redroid-doc) (Remote Android) is a GPU-accelerated Android-in-Cloud (AIC) solution that integrates seamlessly with Olares. You can easily host high-performance Android instances on your Olares and access them anytime to run Android games, apps, or even automation tests.
+[redroid](https://github.com/remote-android/redroid-doc) (Remote Android) is a GPU-accelerated Android-in-Cloud (AIC) solution that integrates seamlessly with beOS Pro. You can easily host high-performance Android instances on your beOS Pro and access them anytime to run Android games, apps, or even automation tests.
-This tutorial walks you through installing redroid on Olares and accessing the Android instance from Windows and macOS.
+This tutorial walks you through installing redroid on beOS Pro and accessing the Android instance from Windows and macOS.
## Objectives
By the end of this tutorial, you will learn how to:
-- Install the required Linux kernel modules on the Olares host.
-- Install the redroid app on Olares and get the service URL.
+- Install the required Linux kernel modules on the beOS Pro host.
+- Install the redroid app on beOS Pro and get the service URL.
- Connect and operate the Android instance from Windows and macOS, using `adb` and `scrcpy`.
- Install APK apps on the Android instance.
## Before you begin
Make sure the following requirements are met:
-- Olares is installed and running on a Linux machine.
+- beOS Pro is installed and running on a Linux machine.
::: tip Configuration requirements
- - redroid is only supported on Linux. Make sure your Olares instance is running on a Linux system.
+ - redroid is only supported on Linux. Make sure your beOS Pro instance is running on a Linux system.
- redroid is resource-intensive. For best performance, we recommend using a machine with at least an 8-core CPU and 16GB of RAM.
:::
-- Enable [LarePass VPN](../manual/larepass/private-network.md) on your device.
+- Enable [beOS Pro app VPN](../manual/larepass/private-network.md) on your device.
## Install dependent kernel modules
@@ -41,25 +41,25 @@ sudo modprobe binder_linux devices="binder,hwbinder,vndbinder"
sudo modprobe ashmem_linux
```
-## Install redroid on Olares
+## Install redroid on beOS Pro
-redroid runs as a headless backend on Olares. To install redroid:
+redroid runs as a headless backend on beOS Pro. To install redroid:
-1. In Olares Market, find redroid under "Utilities", and click **Get**. redroid will launch automatically after installation.
+1. In beOS Pro Market, find redroid under "Utilities", and click **Get**. redroid will launch automatically after installation.
2. Get the URL to access the redroid service:
- a. From Olares Desktop, navigate to **Settings** > **Application** > **redroid**.
+ a. From beOS Pro Desktop, navigate to **Settings** > **Application** > **redroid**.
- b. In **Entrances** > **Set up endpoint**, get the base domain of redroid, e.g., `beb583c3..olares.com`.
+ b. In **Entrances** > **Set up endpoint**, get the base domain of redroid, e.g., `beb583c3..beos.local`.
c. Append the exported port of redroid (`46878`) to the base domain.
- Here is an example of our final URL to access the redroid service: `beb583c3.olares01.olares.com:46878`.
+ Here is an example of our final URL to access the redroid service: `beb583c3.olares01.beos.local:46878`.
## Connect to the redroid service
-To access the Android instance on Olares, you'll need to connect to the redroid service using `adb` and render the UI using `scrcpy`.
+To access the Android instance on beOS Pro, you'll need to connect to the redroid service using `adb` and render the UI using `scrcpy`.
@@ -82,20 +82,20 @@ To access the Android instance on Olares, you'll need to connect to the redroid
3. Use `adb` to connect to the redroid service via the URL obtained earlier:
```powershell
- .\adb.exe connect beb583c3..olares.cn:46878
+ .\adb.exe connect beb583c3..beos.local:46878
```
The connection is successful if you see the example output:
```powershell
# Example output
- already connected to beb583c3..olares.cn:46878
+ already connected to beb583c3..beos.local:46878
```
4. Render UI and audio using `scrcpy`:
```powershell
- .\scrcpy.exe -s beb583c3..olares.cn:46878 --audio-codec=aac --audio-encoder=OMX.google.aac.encoder
+ .\scrcpy.exe -s beb583c3..beos.local:46878 --audio-codec=aac --audio-encoder=OMX.google.aac.encoder
````
Upon successful execution, the command line outputs the device and rendering info. And the Android screen pops up.
@@ -133,20 +133,20 @@ On macOS, `scrcpy` does not include `adb` by default, so you'll need to install
4. Connect to the redroid service URL obtained earlier via `adb`:
```bash
- adb connect beb583c3..olares.cn:46878
+ adb connect beb583c3..beos.local:46878
```
The connection is successful if you see the example output.
```bash
# Example output
- already connected to beb583c3..olares.cn:46878
+ already connected to beb583c3..beos.local:46878
```
5. Render UI and audio using `scrcpy`:
```bash
- scrcpy -s beb583c3..olares.cn:46878 --audio-codec=aac --audio-encoder=OMX.google.aac.encoder
+ scrcpy -s beb583c3..beos.local:46878 --audio-codec=aac --audio-encoder=OMX.google.aac.encoder
```
Upon success, the command line outputs the device information. The Android screen pops up.
@@ -174,7 +174,7 @@ Once connected, you can use `adb` to install third-party APK apps on the Android
```powershell
# Example output
List of devices attached
- beb583c3..olares.com:46878 device
+ beb583c3..beos.local:46878 device
product:ziyi model:23031PN0DC device:ziyi
transport_id:4
```
@@ -207,7 +207,7 @@ Once connected, you can use `adb` to install third-party APK apps on the Android
```bash
# Example output
List of devices attached
- beb583c3..olares.com:46878 device
+ beb583c3..beos.local:46878 device
product:ziyi model:23031PN0DC device:ziyi
transport_id:4
```
diff --git a/docs/use-cases/index.md b/docs/use-cases/index.md
index af524e3c6..2024e012f 100644
--- a/docs/use-cases/index.md
+++ b/docs/use-cases/index.md
@@ -1,8 +1,8 @@
---
-description: Explore practical use cases of Olares, showcasing how to leverage its features for AI workflows, creative tools, and self-hosted applications. Unlock the full potential of Olares in your environment.
+description: Explore practical use cases of beOS Pro, showcasing how to leverage its features for AI workflows, creative tools, and self-hosted applications. Unlock the full potential of beOS Pro in your environment.
---
# Use cases
-While other guides tell you "what" and "how" with Olares, this section dives into the real-world use cases that reveal the full potential of Olares.
+While other guides tell you "what" and "how" with beOS Pro, this section dives into the real-world use cases that reveal the full potential of beOS Pro.
From running AI models to building seamless workflows across your self-hosted services, these hands-on guides help you accomplish specific tasks and implement complete, practical solutions using your installed applications.
@@ -12,10 +12,10 @@ From running AI models to building seamless workflows across your self-hosted se
{ title: 'Open WebUI', link: './openwebui.html', tags: ['AI'] },
{ title: 'Perplexica', link: './perplexica.html', tags: ['AI']},
{ title: 'Dify', link: './dify.html', tags: ['AI']},
- { title: 'Hubble', link: 'https://blog.olares.com/running-farcaster-hubble-on-your-home-cloud/', tags: ['Social Network']},
+ { title: 'Hubble', link: 'https://blog.beos.local/running-farcaster-hubble-on-your-home-cloud/', tags: ['Social Network']},
{ title: 'Ollama', link: './ollama.html', tags: ['AI']},
{ title: 'Jellyfin', link: './stream-media.html', tags: ['Entertainment']},
- { title: 'Steam (Play on Olares device)', link: './play-games-directly.html', tags: ['Entertainment']},
+ { title: 'Steam (Play on beOS Pro device)', link: './play-games-directly.html', tags: ['Entertainment']},
{ title: 'Steam (Stream to other devices)', link: './stream-game.html', tags: ['Entertainment']},
{ title: 'Redroid', link: './host-cloud-android.html', tags: ['Virtual Machine']},
{ title: 'Windows', link: './windows.html', tags: ['Virtual Machine']},
diff --git a/docs/use-cases/lobechat.md b/docs/use-cases/lobechat.md
index 63bb1726b..b198ae463 100644
--- a/docs/use-cases/lobechat.md
+++ b/docs/use-cases/lobechat.md
@@ -1,13 +1,13 @@
---
outline: [2, 4]
-description: Learn how to install LobeChat on Olares and integrate it with Ollama to build and enhance your local custom AI assistants.
+description: Learn how to install LobeChat on beOS Pro and integrate it with Ollama to build and enhance your local custom AI assistants.
---
# Build your local AI assistant with LobeChat
LobeChat is an open‑source framework for building secure, local AI chat experiences. It supports file handling, knowledge bases, and multimodal inputs, and it supports Ollama to run and switch local LLMs.
-Olares streamlines and simplifies the deployment of both, allowing you to skip complex manual environment configurations.
+beOS Pro streamlines and simplifies the deployment of both, allowing you to skip complex manual environment configurations.
This guide covers the installation, configuration, and practical usage of these tools to create your personalized AI assistants.
@@ -21,12 +21,12 @@ By the end of this guide, you are able to:
Before you begin, make sure:
-- Ollama is installed and running in your Olares environment.
+- Ollama is installed and running in your beOS Pro environment.
- At least one model is installed using Ollama. For more information, see [Ollama](ollama.md).
## Install LobeChat
-1. From the Olares Market, search for "LobeChat".
+1. From the beOS Pro Market, search for "LobeChat".
@@ -41,9 +41,9 @@ After the installation is completed, you must connect LobeChat to Ollama to make
{width=75%}
-3. (Optional) To obtain your local Ollama host address, go to Olares **Settings** > **Application** > **Ollama** > **Ollama API** > **Set up endpoint**, and then copy the endpoint address.
+3. (Optional) To obtain your local Ollama host address, go to beOS Pro **Settings** > **Application** > **Ollama** > **Ollama API** > **Set up endpoint**, and then copy the endpoint address.
- {width=60%}
+ {width=60%}
4. In the **Ollama** section, find the **Interface proxy address** field, and then enter your local Ollama address.
@@ -262,11 +262,11 @@ Build an assistant that keeps you updated with the latest technology trends. By
This usually happens due to network or authentication settings. Follow these steps to resolve it:
1. Open Settings, and ensure that the **Authentication level** for Ollama is set to **Internal**.
-2. Turn on the VPN in the LarePass desktop client, and confirm that the status changes to **Intranet** or **P2P**.
+2. Turn on the VPN in the beOS Pro app desktop client, and confirm that the status changes to **Intranet** or **P2P**.
3. Run the connection check again.
:::tip
-If you are on the same local network as your device and the **Authentication level** for Ollama is set to **None**, you do not need to enable the LarePass VPN.
+If you are on the same local network as your device and the **Authentication level** for Ollama is set to **None**, you do not need to enable the beOS Pro app VPN.
:::
For more information, see [Ensure network connectivity](ollama.md#ensure-network-connectivity).
\ No newline at end of file
diff --git a/docs/use-cases/ollama.md b/docs/use-cases/ollama.md
index 9f21e1012..9eb7fabbb 100644
--- a/docs/use-cases/ollama.md
+++ b/docs/use-cases/ollama.md
@@ -1,17 +1,17 @@
---
outline: [2, 3]
-description: Learn how to install Ollama on Olares, manage models using the CLI, and configure it as a central AI service for other applications.
+description: Learn how to install Ollama on beOS Pro, manage models using the CLI, and configure it as a central AI service for other applications.
---
# Download and run local AI models via Ollama
-Ollama is a lightweight platform that allows you to run open-source AI models like `gemma3` and `deepseek-r1` directly on your machine. Within Olares, you can integrate Ollama with graphical interfaces like Open WebUI or other agents to add more features and simplify interactions.
+Ollama is a lightweight platform that allows you to run open-source AI models like `gemma3` and `deepseek-r1` directly on your machine. Within beOS Pro, you can integrate Ollama with graphical interfaces like Open WebUI or other agents to add more features and simplify interactions.
## Learning objectives
In this guide, you will learn how to:
-- Use the Ollama CLI on Olares to manage local LLMs.
+- Use the Ollama CLI on beOS Pro to manage local LLMs.
- Configure Ollama as an API service for internal and external apps.
## Before you begin
-Before you start, ensure that you have Olares admin privileges.
+Before you start, ensure that you have beOS Pro admin privileges.
## Install Ollama
1. Open **Market**, and search for "Ollama".
@@ -19,7 +19,7 @@ Before you start, ensure that you have Olares admin privileges.
## Manage models with the Ollama CLI
-Ollama CLI allows you to manage and interact with AI models directly from the Olares terminal. Below are the key commands.
+Ollama CLI allows you to manage and interact with AI models directly from the beOS Pro terminal. Below are the key commands.
### Download a model
:::tip Check Ollama library
If you are unsure which model to download, check the [Ollama Library](https://ollama.com/library) to explore available models.
@@ -76,7 +76,7 @@ To see all currently running models, use:
ollama ps
```
## Configure Ollama API Access
-To use Ollama as the backend for other applications (such as DeerFlow inside Olares, or Obsidian on your laptop), you must configure the API to allow access from the local network.
+To use Ollama as the backend for other applications (such as DeerFlow inside beOS Pro, or Obsidian on your laptop), you must configure the API to allow access from the local network.
### Verify authentication level
By default, the API's authentication level is set to **Internal**, allowing applications on the same local network to access the API without a login check.
@@ -93,15 +93,15 @@ By default, the API's authentication level is set to **Internal**, allowing appl
:::tip For OpenAI-compatible endpoint
Some apps expect an OpenAI-compatible API. If the standard endpoint fails, try appending `/v1` to your address. For example:
```
-https://39975b9a1.{YOURUSERNAME}.olares.com/v1
+https://39975b9a1.{YOURUSERNAME}.beos.local/v1
```
:::
If the application forces you to enter an API Key, you can usually enter any string (e.g., `ollama`).
### Ensure network connectivity
-Because you set the authentication to "Internal", your application must be on the same local network as Olares to connect.
-* **Local network**: If your device (or the app running on Olares) is on the same Wi-Fi or LAN, you can connect directly using the frontend address.
-* **Remote access**: If you are accessing Olares remotely, you must enable [LarePass VPN](../manual/larepass/private-network.md#enable-vpn-on-larepass) on your client device. This creates a secure tunnel that effectively places your device on the same network as Olares.
+Because you set the authentication to "Internal", your application must be on the same local network as beOS Pro to connect.
+* **Local network**: If your device (or the app running on beOS Pro) is on the same Wi-Fi or LAN, you can connect directly using the frontend address.
+* **Remote access**: If you are accessing beOS Pro remotely, you must enable [beOS Pro app VPN](../manual/larepass/private-network.md#enable-vpn-on-larepass) on your client device. This creates a secure tunnel that effectively places your device on the same network as beOS Pro.
## Learn more
diff --git a/docs/use-cases/openclaw.md b/docs/use-cases/openclaw.md
index bb52e9430..22e097caa 100644
--- a/docs/use-cases/openclaw.md
+++ b/docs/use-cases/openclaw.md
@@ -4,7 +4,7 @@ description: Learn how to install, configure, personalize, and integrate OpenCla
head:
- - meta
- name: keywords
- content: Olares, OpenClaw, OpenClaw tutorial, OpenClaw learning
+ content: beOS Pro, OpenClaw, OpenClaw tutorial, OpenClaw learning
---
# OpenClaw
@@ -98,7 +98,7 @@ The OpenClaw 2026.02.25 update introduced a security enhancement that requires e
## Install OpenClaw
-1. From the Olares Market, search for "OpenClaw".
+1. From the beOS Pro Market, search for "OpenClaw".
{width=90%}
@@ -109,7 +109,7 @@ The OpenClaw 2026.02.25 update introduced a security enhancement that requires e
{width=30%}
:::tip Run multiple OpenClaw agents
-Olares supports app cloning. If you want to run multiple independent AI agents for different tasks, you can clone the OpenClaw app. For more information, see [Clone applications](../manual/olares/market/clone-apps.md).
+beOS Pro supports app cloning. If you want to run multiple independent AI agents for different tasks, you can clone the OpenClaw app. For more information, see [Clone applications](../manual/olares/market/clone-apps.md).
:::
## Initialize OpenClaw
@@ -210,7 +210,7 @@ Connect the Control UI to the OpenClaw CLI to use the graphical dashboard.
If you need to restart OpenClaw manually, do not use the OpenClaw CLI. Use one of the following methods:
- **Restart the app from Settings or Market**:
- Open **Settings**, go to **Applications** > **OpenClaw**, click **Stop**, and then click **Resume**.
- - Open **Market**, go to **My Olares**, find **OpenClaw**, click keyboard_arrow_down next to the operation button, select **Stop**, and then select **Resume**.
+ - Open **Market**, go to **My beOS Pro**, find **OpenClaw**, click keyboard_arrow_down next to the operation button, select **Stop**, and then select **Resume**.
- **Restart the container**: Open **Control Hub**, click `clawdbot` under **Deployments**, and then click **Restart**.
:::
@@ -519,7 +519,7 @@ To manage skills and plugins, install ClawHub. It is the package manager for Ope
If you need to restart OpenClaw manually, do not use the OpenClaw CLI. Use one of the following methods:
- **Restart the app from Settings or Market**:
- Open **Settings**, go to **Applications** > **OpenClaw**, click **Stop**, and then click **Resume**.
- - Open **Market**, go to **My Olares**, find **OpenClaw**, click keyboard_arrow_down next to the operation button, select **Stop**, and then select **Resume**.
+ - Open **Market**, go to **My beOS Pro**, find **OpenClaw**, click keyboard_arrow_down next to the operation button, select **Stop**, and then select **Resume**.
- **Restart the container**: Open **Control Hub**, click `clawdbot` under **Deployments**, and then click **Restart**.
:::
@@ -533,14 +533,14 @@ If you attempt to manually start, stop, or restart OpenClaw using commands like
#### Cause
-OpenClaw is deployed as a containerized app in Olares, where the gateway runs as the primary container process `pid 1` and is always active. This environment does not use standard Linux system and service management tools such as `systemd` and `systemctl`, so these commands do not work.
+OpenClaw is deployed as a containerized app in beOS Pro, where the gateway runs as the primary container process `pid 1` and is always active. This environment does not use standard Linux system and service management tools such as `systemd` and `systemctl`, so these commands do not work.
#### Solution
Do not use the OpenClaw CLI to manage the gateway service. Instead, restart OpenClaw using one of the following methods:
- **Restart OpenClaw from Settings or Market**:
- Open **Settings**, go to **Applications** > **OpenClaw**, click **Stop**, and then click then **Resume**.
- - Open **Market**, go to **My Olares**, find **OpenClaw**, click keyboard_arrow_down next to the operation button, select **Stop**, and then select **Resume**.
+ - Open **Market**, go to **My beOS Pro**, find **OpenClaw**, click keyboard_arrow_down next to the operation button, select **Stop**, and then select **Resume**.
- **Restart the container**: Open **Control Hub**, click `clawdbot` under **Deployments**, and then click **Restart**.
## Resources
diff --git a/docs/use-cases/openwebui.md b/docs/use-cases/openwebui.md
index 1d815d206..86359ddd4 100644
--- a/docs/use-cases/openwebui.md
+++ b/docs/use-cases/openwebui.md
@@ -1,29 +1,29 @@
---
outline: [2, 3]
-description: Guide to using Open WebUI in Olares for managing Large Language Models. Learn about model management, voice interactions, and image generation capabilities with both Ollama and OpenAI-compatible APIs.
+description: Guide to using Open WebUI in beOS Pro for managing Large Language Models. Learn about model management, voice interactions, and image generation capabilities with both Ollama and OpenAI-compatible APIs.
---
# Open WebUI
-Open WebUI provides an intuitive interface for managing Large Language Models (LLMs) that supports both Ollama and OpenAI-compatible APIs. This page helps you set up and configure Open WebUI in Olares for:
+Open WebUI provides an intuitive interface for managing Large Language Models (LLMs) that supports both Ollama and OpenAI-compatible APIs. This page helps you set up and configure Open WebUI in beOS Pro for:
* Model management
* Voice interactions (speech-to-text and text-to-speech)
* Image generation capabilities
-:::tip Enable LarePass VPN
+:::tip Enable beOS Pro app VPN
Make sure your device has LassPass installed and [VPN enabled](../manual/larepass/private-network.md#enable-vpn-on-larepass) to ensure a fast and stable access.
:::
## Installation
Ollama is required prior to launching Open WebUI:
* **For admin**: Install both "Ollama" and "Open WebUI".
-* **For team members**: Ensure that "Ollama" is already installed by Olares admin, and then install "Open WebUI" only.
+* **For team members**: Ensure that "Ollama" is already installed by beOS Pro admin, and then install "Open WebUI" only.
{width=30%}
:::info
-First-time users need to create a local Open WebUI account. This account is specifically for your Olares installation and doesn't connect to external services. Note that existing Open WebUI accounts from other installations cannot be used here - you'll need to create a new one.
+First-time users need to create a local Open WebUI account. This account is specifically for your beOS Pro installation and doesn't connect to external services. Note that existing Open WebUI accounts from other installations cannot be used here - you'll need to create a new one.
:::
## Download models
@@ -48,7 +48,7 @@ Recommended starter models for optimal performance (13B parameters or smaller):
### Speech-to-text
1. Install Faster Whisper from Market based on your role:
- Admin: Install both "Faster Whisper For Cluster" and "Faster Whisper".
- - Team members: Ensure that "Faster Whisper For Cluster" is already installed by Olares admin, and install "Faster Whisper" only.
+ - Team members: Ensure that "Faster Whisper For Cluster" is already installed by beOS Pro admin, and install "Faster Whisper" only.
{width=40%}
2. Open WebUI, and navigate to **Admin Panel** > **Settings** > **Audio**.
@@ -83,7 +83,7 @@ Recommended starter models for optimal performance (13B parameters or smaller):
### Text-to-speech
1. The admin installs OpenedAI Speech from Market. This launches the service within the cluster.
:::info
- "OpenedAI Speech" is a shared application and can only be installed by Olares admin. If you are a team member, ensure that the Olares admin has already installed "OpenedAI Speech".
+ "OpenedAI Speech" is a shared application and can only be installed by beOS Pro admin. If you are a team member, ensure that the beOS Pro admin has already installed "OpenedAI Speech".
2. Open WebUI, and navigate to **Admin Panel** > **Settings** > **Audio**.
3. Select OpenAI as the text-to-speech engine, with the following configurations:
- API Base URL: `http://openedaispeech.openedaispeech-{admin's local name}:8000/v1`. For example: `http://openedaispeech.openedaispeech-alice123:8000/v1`.
@@ -91,7 +91,7 @@ Recommended starter models for optimal performance (13B parameters or smaller):
4. Click **Save**.
### Text-to-image
-With [SD Web UI Shared installed in your Olares environment](stable-diffusion.md#install-sd-web-ui), you can leverage Stable Diffusion's powerful image generation capabilities directly through Open WebUI.
+With [SD Web UI Shared installed in your beOS Pro environment](stable-diffusion.md#install-sd-web-ui), you can leverage Stable Diffusion's powerful image generation capabilities directly through Open WebUI.
1. The admin installs SD Web UI Shared from Market. This launches the Stable Diffusion service within the cluster.
2. Open Open WebUI, and navigate to **Admin Panel** > **Settings** > **Images**.
diff --git a/docs/use-cases/pdfmathtranslate.md b/docs/use-cases/pdfmathtranslate.md
index f3901b88e..395ce4f6d 100644
--- a/docs/use-cases/pdfmathtranslate.md
+++ b/docs/use-cases/pdfmathtranslate.md
@@ -1,13 +1,13 @@
---
outline: [2, 4]
-description: Learn how to install and configure PDFMathTranslate on Olares. This tutorial guides you through using the local AI model Ollama to translate scientific PDFs, preserving original layouts and mathematical formulas.
+description: Learn how to install and configure PDFMathTranslate on beOS Pro. This tutorial guides you through using the local AI model Ollama to translate scientific PDFs, preserving original layouts and mathematical formulas.
---
# Translate scientific PDFs while preserving layout
PDFMathTranslate is an application designed to translate scientific PDF documents while retaining the original layout and mathematical formulas.
-This tutorial provides instructions on how to install and use PDFMathTranslate on Olares, using the local AI model Ollama for translation.
+This tutorial provides instructions on how to install and use PDFMathTranslate on beOS Pro, using the local AI model Ollama for translation.
## Learning objectives
@@ -18,12 +18,12 @@ By the end of this tutorial, you are able to:
## Prerequisites
Before you begin, make sure:
-- Ollama is installed and running in your Olares environment.
+- Ollama is installed and running in your beOS Pro environment.
- At least one model is installed using Ollama. For more information, see [Ollama](ollama.md).
## Install PDFMathTranslate
-1. Open the Olares Market and search for "PDFMathTranslate".
+1. Open the beOS Pro Market and search for "PDFMathTranslate".
2. Click **Get**, and then click **Install**.
@@ -56,7 +56,7 @@ To use the local AI service Ollama for translation, configure the following sett
1. From the **Service** list, select **Ollama**.
2. (Optional) To obtain the Ollama host address:
- a. Go to Olares **Settings** > **Application** > **Ollama**.
+ a. Go to beOS Pro **Settings** > **Application** > **Ollama**.
b. In the **Entrances** section, click **Ollama API**.
@@ -111,7 +111,7 @@ On the left side of the pdfmathtranslate workspace, in the **Translated** sectio
-#### From Olares Files app
+#### From beOS Pro Files app
1. Open the Files app, and then go to **Data** > **pdfmathtranslate** > **pdfmathtranslate**.
@@ -119,7 +119,7 @@ On the left side of the pdfmathtranslate workspace, in the **Translated** sectio
2. Double-click a file, and then click the download icon in the upper-right corner.
- 
+ 
## FAQ
diff --git a/docs/use-cases/perplexica.md b/docs/use-cases/perplexica.md
index ca784f7e3..58f5e290b 100644
--- a/docs/use-cases/perplexica.md
+++ b/docs/use-cases/perplexica.md
@@ -1,5 +1,5 @@
---
-description: Explore Perplexica for advanced AI-driven data analysis and visualization with Olares. Learn how to set up Perplexica with ease.
+description: Explore Perplexica for advanced AI-driven data analysis and visualization with beOS Pro. Learn how to set up Perplexica with ease.
---
# Set up a privacy-focused AI search engine with Perplexica
@@ -9,7 +9,7 @@ This guide will use Ollama as the model provider and SearXNG as the search provi
## Prerequisites
Before you begin, make sure:
-- Ollama installed and running in your Olares environment.
+- Ollama installed and running in your beOS Pro environment.
- At least one model installed using Ollama.
## Install SearXNG
diff --git a/docs/use-cases/play-games-directly.md b/docs/use-cases/play-games-directly.md
index 3692c3666..990daf024 100644
--- a/docs/use-cases/play-games-directly.md
+++ b/docs/use-cases/play-games-directly.md
@@ -1,11 +1,11 @@
---
outline: [2, 3]
-description: Learn how to turn your Olares device into a gaming console by connecting a monitor and peripherals directly.
+description: Learn how to turn your beOS Pro device into a gaming console by connecting a monitor and peripherals directly.
---
-# Play Steam games locally on Olares
+# Play Steam games locally on beOS Pro
-While Olares is typically used as a headless system, you can connect a monitor, keyboard, and mouse to play games directly on the device.
+While beOS Pro is typically used as a headless system, you can connect a monitor, keyboard, and mouse to play games directly on the device.
However, simply plugging in a monitor is not enough. Because Steam Headless is optimized for remote streaming by default, you must manually configure the audio settings to output audio locally.
@@ -17,13 +17,13 @@ By the end of this tutorial, you will learn how to:
## Prerequisites
Before you begin, ensure you have:
-- Olares version 1.12.3 or later.
-- Olares running on a machine equipped with an NVIDIA GPU.
+- beOS Pro version 1.12.3 or later.
+- beOS Pro running on a machine equipped with an NVIDIA GPU.
- A valid Steam account to access your games.
-- A monitor, keyboard, and mouse connected to the Olares device.
+- A monitor, keyboard, and mouse connected to the beOS Pro device.
## 1. Install and configure Steam Headless
-Install the app from the Olares Market and then complete the initial setup within the Steam client itself.
+Install the app from the beOS Pro Market and then complete the initial setup within the Steam client itself.
### Install Steam Headless
@@ -253,7 +253,7 @@ To enable audio for streaming:
## FAQs
### Why does my monitor show the Steam interface even when I'm not playing?
-The Olares device usually displays a terminal prompt. However, running the Steam application activates a graphical interface that takes over the display.
+The beOS Pro device usually displays a terminal prompt. However, running the Steam application activates a graphical interface that takes over the display.
To return the monitor to the standard terminal view, you must stop the Steam application via **Market** or **Settings**.
diff --git a/docs/use-cases/remote.reusables.md b/docs/use-cases/remote.reusables.md
index e5ed1722e..523868229 100644
--- a/docs/use-cases/remote.reusables.md
+++ b/docs/use-cases/remote.reusables.md
@@ -2,21 +2,21 @@
search: false
---
-
+
-1. Open LarePass, go to **Settings** > **Account**.
+1. Open beOS Pro app, go to **Settings** > **Account**.
2. Turn on the VPN switch.
- 
+ 
-
-1. Open LarePass, click on the avatar area in the top left corner of the main interface.
+
+1. Open beOS Pro app, click on the avatar area in the top left corner of the main interface.
2. Turn on the switch for **VPN connection** in the pop-up panel.
- 
+ 
:::info
-iOS or macOS versions of LarePass will require adding a VPN configuration file to the system when turning on the VPN. Follow the prompts to complete the setup.
+iOS or macOS versions of beOS Pro app will require adding a VPN configuration file to the system when turning on the VPN. Follow the prompts to complete the setup.
:::
diff --git a/docs/use-cases/stable-diffusion.md b/docs/use-cases/stable-diffusion.md
index 29f5823bb..5b7669ff8 100644
--- a/docs/use-cases/stable-diffusion.md
+++ b/docs/use-cases/stable-diffusion.md
@@ -1,12 +1,12 @@
---
-description: Comprehensive guide to using Stable Diffusion in Olares. Learn about text-to-image generation, and how to optimize your SD Web UI deployment for multi-user environments.
+description: Comprehensive guide to using Stable Diffusion in beOS Pro. Learn about text-to-image generation, and how to optimize your SD Web UI deployment for multi-user environments.
---
# Stable Diffusion
Stable Diffusion represents a groundbreaking implementation of latent diffusion models (LDMs) in AI image synthesis. This deep learning architecture operates by decomposing the image generation process into a lower-dimensional latent space, significantly reducing computational requirements while maintaining high-fidelity output.
-Olares simplifies the deployment and management of Stable Diffusion. Unlike traditional deployments that require manual configuration of file systems and databases, Olares shields developers from these infrastructure complexities, allowing you to focus solely on using the model for image generation.
+beOS Pro simplifies the deployment and management of Stable Diffusion. Unlike traditional deployments that require manual configuration of file systems and databases, beOS Pro shields developers from these infrastructure complexities, allowing you to focus solely on using the model for image generation.
-With Olares's multi-user support, team members can share a single Stable Diffusion deployment while maintaining individual data privacy. This approach eliminates the need for redundant system installations that would otherwise consume excessive hardware resources.
+With beOS Pro's multi-user support, team members can share a single Stable Diffusion deployment while maintaining individual data privacy. This approach eliminates the need for redundant system installations that would otherwise consume excessive hardware resources.
## What can Stable Diffusion do?
Whether you're an artist looking to expand your creative toolkit, a developer integrating AI imaging into your workflow, or simply curious about AI art generation, Stable Diffusion offers:
@@ -19,7 +19,7 @@ Whether you're an artist looking to expand your creative toolkit, a developer in
## Install SD Web UI
:::info
-Starting from Olares 1.11.6, if "SD Web UI For Cluster" or "SD Web UI" was previously installed, uninstall them before proceeding.
+Starting from beOS Pro 1.11.6, if "SD Web UI For Cluster" or "SD Web UI" was previously installed, uninstall them before proceeding.
:::
1. Install SD Web UI Shared directly from Market.
@@ -46,7 +46,7 @@ While this optimization allows for higher resolution image generation, it comes
If you need to remove `--xformers`:
:::info
-Only Olares admin can adjust system parameters through the Control Hub app.
+Only beOS Pro admin can adjust system parameters through the Control Hub app.
:::
1. Open Control Hub, and navigate to **Browse**.
diff --git a/docs/use-cases/stirling-pdf.md b/docs/use-cases/stirling-pdf.md
index 38d81cf65..0d9e7c49b 100644
--- a/docs/use-cases/stirling-pdf.md
+++ b/docs/use-cases/stirling-pdf.md
@@ -1,6 +1,6 @@
---
outline: [2, 5]
-description: A step-by-step guide to installing and using Stirling PDF on Olares. Learn how to securely manage PDF documents, covering essential tasks such as merging, editing, format conversion, and creating automated workflow pipelines.
+description: A step-by-step guide to installing and using Stirling PDF on beOS Pro. Learn how to securely manage PDF documents, covering essential tasks such as merging, editing, format conversion, and creating automated workflow pipelines.
---
# Manage PDF documents with Stirling PDF
@@ -18,7 +18,7 @@ By the end of this tutorial, you are able to:
## Install Stirling PDF
-1. Open the Olares Market and search for "Stirling-PDF".
+1. Open the beOS Pro Market and search for "Stirling-PDF".
diff --git a/docs/use-cases/stream-game.md b/docs/use-cases/stream-game.md
index 634c1ee47..9d48f1a0a 100644
--- a/docs/use-cases/stream-game.md
+++ b/docs/use-cases/stream-game.md
@@ -1,36 +1,36 @@
---
outline: [2, 3]
-description: Comprehensive tutorial on streaming Steam games with Olares. Learn to install Steam Headless, configure the streaming service, and stream games on Moonlight from both local and remote networks.
+description: Comprehensive tutorial on streaming Steam games with beOS Pro. Learn to install Steam Headless, configure the streaming service, and stream games on Moonlight from both local and remote networks.
---
# Stream your games with Steam Headless
-Want to enjoy gaming powered by Olares? You're all set. With the Steam Headless app, Olares easily transforms into a powerful game streaming server. You can now play your favorite games on any compatible device via Moonlight.
+Want to enjoy gaming powered by beOS Pro? You're all set. With the Steam Headless app, beOS Pro easily transforms into a powerful game streaming server. You can now play your favorite games on any compatible device via Moonlight.
-This guide walks you through installing Steam Headless on Olares, configuring the Steam client, pairing the streaming service, and connecting with the Moonlight client to play.
+This guide walks you through installing Steam Headless on beOS Pro, configuring the Steam client, pairing the streaming service, and connecting with the Moonlight client to play.
## Learning objectives
By the end of this tutorial, you will learn how to:
-- Install and set up Steam Headless on your Olares device.
+- Install and set up Steam Headless on your beOS Pro device.
- Configure the Sunshine streaming service.
- Pair your device via Moonlight and stream games locally or remotely.
## Prerequisites
Before you begin, make sure:
-- Olares running on a machine equipped with an NVIDIA GPU.
+- beOS Pro running on a machine equipped with an NVIDIA GPU.
- Moonlight installed on your streaming device. Visit the [Moonlight website](https://moonlight-stream.org/) to download and install the appropriate version.
- A valid Steam account to access your games.
-- [LarePass VPN enabled](../manual/larepass/private-network.md#enable-vpn-on-larepass) on your client devices (desktop or mobile) if you plan to stream outside your home network.
+- [beOS Pro app VPN enabled](../manual/larepass/private-network.md#enable-vpn-on-larepass) on your client devices (desktop or mobile) if you plan to stream outside your home network.
:::tip
-For local streaming, LarePass VPN is not required.
+For local streaming, beOS Pro app VPN is not required.
:::
## Install and configure Steam Headless
-Install the app from the Olares Market and then complete the initial setup within the Steam client itself.
+Install the app from the beOS Pro Market and then complete the initial setup within the Steam client itself.
### Install Steam Headless
@@ -71,21 +71,21 @@ Steam Headless uses Sunshine to stream video. You must pair it with the Moonligh
### Access the Sunshine console
-Access the Sunshine console to pair your Moonlight client with Olares.
+Access the Sunshine console to pair your Moonlight client with beOS Pro.
1. Copy the URL of your current Steam Headless browser tab.
2. Open a new browser tab and modify the URL to access port `47990`. The address varies depending on your network.
- **Same network**: Use HTTPS with your `.local` address. Either format works (dots or hyphens in the hostname):
```plain
- https://139ebc4f0..olares.local:47990
- https://139ebc4f0--olares.local:47990
+ https://139ebc4f0..olares.local:47990
+ https://139ebc4f0--olares.local:47990
```
- - **Different network (via VPN)**: Enable LarePass VPN on your device, then append `:47990`. For example:
+ - **Different network (via VPN)**: Enable beOS Pro app VPN on your device, then append `:47990`. For example:
```plain
- https://139ebc4f0..olares.com:47990
+ https://139ebc4f0..beos.local:47990
```
3. Press **Enter** to open the Sunshine console page.
@@ -96,20 +96,20 @@ Access the Sunshine console to pair your Moonlight client with Olares.
### Add the host in Moonlight
-Moonlight usually detects your Olares host automatically when it is on the same local network as your Olares device.
+Moonlight usually detects your beOS Pro host automatically when it is on the same local network as your beOS Pro device.
If it doesn't appear, or if you are connecting over different networks, follow these steps to add the host manually. The process shown below uses the macOS Moonlight client.
:::info Connecting from a different network?
-If your Moonlight client and Olares device are on different networks, you must first [enable LarePass VPN](../manual/larepass/private-network.md#enable-vpn-on-larepass) on the device running Moonlight.
+If your Moonlight client and beOS Pro device are on different networks, you must first [enable beOS Pro app VPN](../manual/larepass/private-network.md#enable-vpn-on-larepass) on the device running Moonlight.
:::
1. Open Moonlight on your streaming device.
2. Click the **Add Host** button, which looks like a computer with a plus icon.
-3. Enter your Olares domain without the `https://` prefix. For example:
+3. Enter your beOS Pro domain without the `https://` prefix. For example:
```plain
- 139ebc4f0..olares.com
+ 139ebc4f0..beos.local
```
4. Click **OK**. A new locked host icon appears.
5. Click the locked icon. Moonlight will display a 4-digit pairing PIN.
@@ -131,7 +131,7 @@ Once paired, you're ready to start streaming.
:::tip Optimizing remote play
For the best experience when streaming remotely:
1. Connect your client device to 5GHz Wi-Fi or Ethernet.
-2. Ensure **LarePass VPN** is active.
+2. Ensure **beOS Pro app VPN** is active.
:::
You can stream your games through Moonlight either locally or remotely, depending on your network setup.
@@ -146,9 +146,9 @@ The following steps demonstrate local streaming.
### Why can't I access the Sunshine Web UI using the `.local` address?
-Olares supports `.local` addresses with the HTTP protocol for most services. The Sunshine Web UI is different because it requires HTTPS to secure local communication. If you use `http://` with your `.local` URL, the Sunshine page will not load.
+beOS Pro supports `.local` addresses with the HTTP protocol for most services. The Sunshine Web UI is different because it requires HTTPS to secure local communication. If you use `http://` with your `.local` URL, the Sunshine page will not load.
-To fix this, use `https://` instead of `http://` in your browser's address bar (for example, `https://139ebc4f0..olares.local:47990`).
+To fix this, use `https://` instead of `http://` in your browser's address bar (for example, `https://139ebc4f0..olares.local:47990`).
### Why isn't the game displaying in full screen?
This may be caused by resolution settings. Try adjusting the resolution:
@@ -165,7 +165,7 @@ Use the following shortcuts:
- **Mac**: `Control (^) + Option (⌥) + Shift + Q`
- **Mobile**: `Start + Select + L1 + R1`
-After finishing, exit Steam Big Picture mode to release system resources on Olares.
+After finishing, exit Steam Big Picture mode to release system resources on beOS Pro.
### Where are my downloaded games stored?
@@ -180,14 +180,14 @@ We recommend not changing this default directory.
### Why do I get an error when re-pairing the host in Moonlight?
-If you delete your Olares host in Moonlight and try to pair again, you may encounter the following errors:
+If you delete your beOS Pro host in Moonlight and try to pair again, you may encounter the following errors:
- **The PIN from the PC didn't match. Please try again.**
- **Request timed out (Error 4)**
- **Connection closed (Error 2)**
This usually happens when the Sunshine service is not responding.
-To fix it, simply restart Steam Headless in Olares and try pairing again:
+To fix it, simply restart Steam Headless in beOS Pro and try pairing again:
1. Open Control Hub from Launchpad.
2. Navigate to **Browser** > **steamheadless** > **Deployments** > **steamheadless** > **Restart**.
@@ -202,7 +202,7 @@ To fix it, simply restart Steam Headless in Olares and try pairing again:
You can change your Sunshine credentials directly from the Sunshine web console.
-1. Open Sunshine in your browser using your local address, for example: `https://139ebc4f0..olares.local:47990`.
+1. Open Sunshine in your browser using your local address, for example: `https://139ebc4f0..olares.local:47990`.
2. Log in with your current username and password.
3. Go to the **Change Password** tab.
diff --git a/docs/use-cases/stream-media.md b/docs/use-cases/stream-media.md
index e5b590dca..6c2fe8f61 100644
--- a/docs/use-cases/stream-media.md
+++ b/docs/use-cases/stream-media.md
@@ -1,16 +1,16 @@
---
outline: [2, 3]
-description: Step-by-step guide to setting up Jellyfin on Olares for personal media streaming. Learn how to manage media files with LarePass, add libraries, enhance metadata with plugins, enable hardware acceleration, and securely stream your media through Olares VPN from any device.
+description: Step-by-step guide to setting up Jellyfin on beOS Pro for personal media streaming. Learn how to manage media files with beOS Pro app, add libraries, enhance metadata with plugins, enable hardware acceleration, and securely stream your media through beOS Pro VPN from any device.
---
# Build your private media server with Jellyfin
-Jellyfin is a powerful, open-source software media server that puts you in full control of your media. By installing it on Olares, you can turn your device into a personal streaming platform, organizing movies, shows, and music into a beautiful library accessible securely from anywhere.
+Jellyfin is a powerful, open-source software media server that puts you in full control of your media. By installing it on beOS Pro, you can turn your device into a personal streaming platform, organizing movies, shows, and music into a beautiful library accessible securely from anywhere.
## Learning objectives
In this guide, you will learn how to:
-- Install and set up Jellyfin on your Olares device.
+- Install and set up Jellyfin on your beOS Pro device.
- Add and organize your media libraries.
- Optimize playback using hardware acceleration.
- Install community plugins.
@@ -19,18 +19,18 @@ In this guide, you will learn how to:
## Prerequisites
Before you begin, make sure:
-- LarePass app installed on your client devices (desktop or mobile).
-- Olares ID imported into the LarePass client.
+- beOS Pro app app installed on your client devices (desktop or mobile).
+- beOS ID imported into the beOS Pro app client.
-## Add media to Olares
+## Add media to beOS Pro
-Before setting up Jellyfin, you need to make sure your media is already available on Olares. You can add it in several ways:
+Before setting up Jellyfin, you need to make sure your media is already available on beOS Pro. You can add it in several ways:
- **Upload files directly**
-Upload your media to the `/home/Movies/` folder in Files. For better speed and progress visibility, [use the LarePass desktop client to upload](../manual/olares/files/add-edit-download.md#upload-via-larepass-desktop).
+Upload your media to the `/home/Movies/` folder in Files. For better speed and progress visibility, [use the beOS Pro app desktop client to upload](../manual/olares/files/add-edit-download.md#upload-via-larepass-desktop).
- **Mount an external drive**
-After you insert a USB drive to your Olares device, it will be automatically mounted and accessible. Files in it are under the `/external/` directory.
+After you insert a USB drive to your beOS Pro device, it will be automatically mounted and accessible. Files in it are under the `/external/` directory.
- **Mount a network share**
-If your media is on a NAS or other network server, you can connect it to Olares. For detailed instructions, see [Mount SMB shares](../manual/olares/files/mount-SMB.md).
+If your media is on a NAS or other network server, you can connect it to beOS Pro. For detailed instructions, see [Mount SMB shares](../manual/olares/files/mount-SMB.md).
:::tip Naming conventions
Correct file naming is the key to accurate metadata and beautiful posters in Jellyfin.
@@ -48,7 +48,7 @@ With your media ready, install Jellyfin and complete its setup wizard.
### Install Jellyfin
-1. Open the **Market** app in your Olares web interface.
+1. Open the **Market** app in your beOS Pro web interface.
2. Find **Jellyfin** in the **Fun** category or use the search bar.
3. Click **Get**, then **Install**.
@@ -61,7 +61,7 @@ Follow the wizard prompts to finish configuring Jellyfin.
2. Create a username and password for your Jellyfin admin account, and click **Next**.
3. When prompted to set up your media libraries, you can skip this step for now.
4. For metadata, select your preferred language and country and click **Next**.
-5. For remote access, keep the default settings (unchecked) and click **Next**. Olares VPN will handle secure remote access.
+5. For remote access, keep the default settings (unchecked) and click **Next**. beOS Pro VPN will handle secure remote access.
6. Click **Finish** to complete the setup wizard.
7. You will be taken to the login page. Sign in with the admin credentials you just created.
@@ -76,7 +76,7 @@ With Jellyfin installed and running, the next step is to tell it where your medi
- **Content type**: Choose the type of media (e.g., Movies, Shows, Music). For folders containing both movies and TV shows, choose **Mixed Movies and Shows**.
- **Display name**: Enter the name to display for the library.
- **Folders**: Click + to add the path to your media.
- - **Olares Files**: `/home/movies/`
+ - **beOS Pro Files**: `/home/movies/`
- **External storage**: `/external/`
4. Click **Ok** to save, and repeat for other media types (e.g., one for "Movies", one for "TV Shows").
@@ -86,7 +86,7 @@ Once saved, Jellyfin will automatically scan your folders and begin building you
To ensure smooth playback for high-resolution videos, enable hardware acceleration. This allows Jellyfin to use your device's hardware for faster, more efficient transcoding.
1. In the Jellyfin **Dashboard** (click the ≡ icon > Dashboard), go to **Playback** > **Transcoding**.
-2. Under **Hardware acceleration**, choose your preferred method based on your Olares device's hardware.
+2. Under **Hardware acceleration**, choose your preferred method based on your beOS Pro device's hardware.
## Enhance experience with community plugins
@@ -118,14 +118,14 @@ Since each plugin behaves differently, check the plugin's **GitHub repository**
With Jellyfin set up and your libraries ready, the final step is connecting from your client devices so you can start streaming your media.
-### Configure Jellyfin authentication level in Olares
+### Configure Jellyfin authentication level in beOS Pro
-To ensure secure connections between Jellyfin and your devices, configure the authentication level through Olares.
+To ensure secure connections between Jellyfin and your devices, configure the authentication level through beOS Pro.
-Make sure LarePass VPN (or local network access) is enabled before starting the steps below.
-If you haven’t done this yet, see [Enable VPN on LarePass](../manual/larepass/private-network.md#enable-vpn-on-larepass) for details.
+Make sure beOS Pro app VPN (or local network access) is enabled before starting the steps below.
+If you haven’t done this yet, see [Enable VPN on beOS Pro app](../manual/larepass/private-network.md#enable-vpn-on-larepass) for details.
-1. In your Olares web interface, go to **Settings** > **Application**.
+1. In your beOS Pro web interface, go to **Settings** > **Application**.
2. Find and click **Jellyfin**.
3. Go to the **Entrances** tab.
@@ -139,8 +139,8 @@ Assume you've already installed the official [Jellyfin client app](https://jelly
1. Open the Jellyfin client app on your device.
2. Click **Add Server**.
-3. In your Olares web interface, go to **Settings** > **Application** > **Jellyfin** > **Entrances** > **Set up endpoint**.
-4. Copy the server address shown next to **Endpoint** (e.g., `https://7e89d2a1.laresprime.olares.com`)
+3. In your beOS Pro web interface, go to **Settings** > **Application** > **Jellyfin** > **Entrances** > **Set up endpoint**.
+4. Copy the server address shown next to **Endpoint** (e.g., `https://7e89d2a1.laresprime.beos.local`)
5. Paste this address into the client and click **Connect**.
@@ -149,5 +149,5 @@ Assume you've already installed the official [Jellyfin client app](https://jelly
You should now see your media libraries displayed in the app.
:::tip
-For the best experience, keep your LarePass VPN connection active when accessing Jellyfin remotely. This ensures you can always connect to your Jellyfin server securely.
+For the best experience, keep your beOS Pro app VPN connection active when accessing Jellyfin remotely. This ensures you can always connect to your Jellyfin server securely.
:::
\ No newline at end of file
diff --git a/docs/use-cases/windows.md b/docs/use-cases/windows.md
index 53dd58acd..73a2e85ae 100644
--- a/docs/use-cases/windows.md
+++ b/docs/use-cases/windows.md
@@ -1,14 +1,14 @@
---
outline: [2, 4]
-description: A comprehensive guide to installing and running a Windows virtual machine on Olares. Learn how to configure initial credentials, connect via browser-based VNC or Microsoft Remote Desktop (RDP), and transfer files between your computer and the VM.
+description: A comprehensive guide to installing and running a Windows virtual machine on beOS Pro. Learn how to configure initial credentials, connect via browser-based VNC or Microsoft Remote Desktop (RDP), and transfer files between your computer and the VM.
---
-# Run a Windows VM on your Olares device
+# Run a Windows VM on your beOS Pro device
-Olares lets you run a full Windows virtual machine directly on your device, giving you a personal, always-available Windows environment accessible from macOS, Windows, or Linux.
+beOS Pro lets you run a full Windows virtual machine directly on your device, giving you a personal, always-available Windows environment accessible from macOS, Windows, or Linux.
:::info System capabilities
-- Olares supports running essential Windows applications.
+- beOS Pro supports running essential Windows applications.
- Workflows are limited to **CPU or integrated graphics performance**. GPU passthrough is not yet supported, meaning heavy GPU-accelerated applications may not perform optimally.
- Audio output is **only supported** when connected via Remote Desktop (RDP).
:::
@@ -18,14 +18,14 @@ This guide walks you through installing the Windows VM, enabling secure networki
## Learning objectives
By the end of this tutorial, you will learn how to:
-- Install and set up the Windows VM on your Olares device.
+- Install and set up the Windows VM on your beOS Pro device.
- Access the Windows VM using the browser-based VNC viewer or Microsoft Remote Desktop (RDP).
- Change your Windows login password from inside the VM.
- Transfer files seamlessly between your computer and the Windows VM.
## Install and configure Windows VM
-Windows is available as an app in the Olares Market.
+Windows is available as an app in the beOS Pro Market.
### Install Windows
1. Open the Market, and search for "Windows".
@@ -46,7 +46,7 @@ Windows is available as an app in the Olares Market.
Once the installation is finished, open Windows from Launchpad to start the VM for the first time.
-Olares will automatically download and install the system image of the corresponding Windows version. This may take several minutes depending on your network speed.
+beOS Pro will automatically download and install the system image of the corresponding Windows version. This may take several minutes depending on your network speed.
## Access the Windows VM
@@ -77,7 +77,7 @@ Each Windows instance uses a unique port. If you have cloned the Windows app, en
:::info
The following steps show the macOS interface, but the workflow is similar on all platforms.
:::
-1. [Enable VPN on LarePass](../manual/larepass/private-network.md#enable-vpn-on-larepass) on your device.
+1. [Enable VPN on beOS Pro app](../manual/larepass/private-network.md#enable-vpn-on-larepass) on your device.
When the VPN connection status shows **P2P**, or **Intranet**, the secure network is active and ready for remote access.
@@ -97,9 +97,9 @@ The following steps show the macOS interface, but the workflow is similar on all
c. In **PC name**, enter the domain you get from the previous step, followed by a colon and the port number.
- For example, if your URL is `https://0f4137ed..olares.com`, and the port is `47374`, enter:
+ For example, if your URL is `https://0f4137ed..beos.local`, and the port is `47374`, enter:
```
- 0f4137ed..olares.com:47374
+ 0f4137ed..beos.local:47374
```
@@ -143,7 +143,7 @@ The file appears immediately in Windows and is ready to use.
To end your RDP session, simply close the RDP window.
-The Windows VM continues running on your Olares device and is always ready for you to reconnect.
+The Windows VM continues running on your beOS Pro device and is always ready for you to reconnect.
## FAQ
diff --git a/docs/use-cases/wise.reusables.md b/docs/use-cases/wise.reusables.md
index 7244c9c26..e976269e2 100644
--- a/docs/use-cases/wise.reusables.md
+++ b/docs/use-cases/wise.reusables.md
@@ -1,7 +1,7 @@
---
search: false
---
-将你的内容收集到 Wise 后，你可以通过 Olares 的聚合搜索功能进行全文搜索。
+将你的内容收集到 Wise 后，你可以通过 beOS Pro 的聚合搜索功能进行全文搜索。
@@ -16,17 +16,17 @@ search: false
具体步骤可能会因操作系统和浏览器而有所不同。以下以 Safari 为例。
:::
-1. 在浏览器中点击 ios_share，选择 LarePass 为分享对象。你可以：
- - 在分享选项中选择 LarePass 的图标，或者
- - 在**其他操作**栏中选择 **LarePass**
+1. 在浏览器中点击 ios_share，选择 beOS Pro app 为分享对象。你可以：
+ - 在分享选项中选择 beOS Pro app 的图标，或者
+ - 在**其他操作**栏中选择 **beOS Pro app**
- LarePass 应用会自动打开并检测待分享页面的内容，并提示是否要添加至 Wise。
+ beOS Pro app 应用会自动打开并检测待分享页面的内容，并提示是否要添加至 Wise。
2. 点击**确认**添加。
::: tip 复制 URL 分享
-你也可以直接复制网页 URL 并打开 LarePass。LarePass 会自动检测剪贴板中的 URL 和可收藏的内容。
+你也可以直接复制网页 URL 并打开 beOS Pro app。beOS Pro app 会自动检测剪贴板中的 URL 和可收藏的内容。
:::
收集完成后，可以在 Wise 的**库** > **文章**中阅读收集的文章。
\ No newline at end of file
diff --git a/docs/zh/developer/concepts/account.md b/docs/zh/developer/concepts/account.md
index 369c137f9..af636343b 100644
--- a/docs/zh/developer/concepts/account.md
+++ b/docs/zh/developer/concepts/account.md
@@ -1,45 +1,45 @@
---
outline: [2, 3]
-description: Olares 账户系统的同步机制、账户阶段和统一认证原理。包括多因素认证机制、密码系统及多设备账户同步原理。
+description: beOS Pro 账户系统的同步机制、账户阶段和统一认证原理。包括多因素认证机制、密码系统及多设备账户同步原理。
---
# 账户
-本文介绍 Olares 账户系统的相关概念和设计。
+本文介绍 beOS Pro 账户系统的相关概念和设计。
## 账户同步
-LarePass、Olares 和 Olares Space 之间的账户同步机制如下：
+beOS Pro app、beOS Pro 和 Remote Space 之间的账户同步机制如下：
-- 创建 Olares 时需要提供 Olares ID，并使用该 ID 登录 LarePass 进行激活。
-- 登录 Olares Space 时，需要使用 LarePass 扫描二维码。
+- 创建 beOS Pro 时需要提供 beOS ID，并使用该 ID 登录 beOS Pro app 进行激活。
+- 登录 Remote Space 时，需要使用 beOS Pro app 扫描二维码。
## 账户的状态
每个账户都有三个状态：
-### 未绑定 Olares ID（DID 阶段）
-已在本地创建 DID、助记词和私钥，但尚未关联 Olares ID。
+### 未绑定 beOS ID（DID 阶段）
+已在本地创建 DID、助记词和私钥，但尚未关联 beOS ID。
-在这个阶段，你可以导出助记词，也可以访问 Olares Space 配置自定义域名或申请组织域名。
+在这个阶段，你可以导出助记词，也可以访问 Remote Space 配置自定义域名或申请组织域名。
-但此时无法将账户导入到其他 LarePass 客户端。
+但此时无法将账户导入到其他 beOS Pro app 客户端。
:::tip 提示
-在 LarePass 上，当你点击**创建账户**时，就已经处于未绑定 Olares ID 状态。
+在 beOS Pro app 上，当你点击**创建账户**时，就已经处于未绑定 beOS ID 状态。
:::
-### 已绑定 Olares ID
-当账户绑定了 Olares ID 后，系统会在区块链上记录你的 Olares ID 与 DID 之间的关联。
+### 已绑定 beOS ID
+当账户绑定了 beOS ID 后，系统会在区块链上记录你的 beOS ID 与 DID 之间的关联。
-在这个阶段，你可以通过命令行在本机上安装 Olares，或在 Olares Space 申请并激活 Olares。
+在这个阶段，你可以通过命令行在本机上安装 beOS Pro，或在 Remote Space 申请并激活 beOS Pro。
你也可以使用导出的助记词将账户导入其他设备，实现应用间的统一认证。
-### 已绑定 Olares
-最后一个阶段是账户与 Olares 设备建立关联，此时你可以完整访问 Olares 上的所有功能，例如在 LarePass 上查看该 Olares ID 下的机器系统资源。
+### 已绑定 beOS Pro
+最后一个阶段是账户与 beOS Pro 设备建立关联，此时你可以完整访问 beOS Pro 上的所有功能，例如在 beOS Pro app 上查看该 beOS ID 下的机器系统资源。
## 统一账户系统
-Olares 支持多用户系统的统一认证。
+beOS Pro 支持多用户系统的统一认证。
1. 用户在登录页面完成登录后，后续所有请求都会自动包含认证信息。
2. 每个用户请求都会先经过 Authelia 服务进行认证。
@@ -49,21 +49,21 @@ Olares 支持多用户系统的统一认证。
## 多因素认证（MFA）
-Olares 集成了多种不同安全等级的认证因素，以确保系统中用户身份认证的安全性。
+beOS Pro 集成了多种不同安全等级的认证因素，以确保系统中用户身份认证的安全性。
### 密码
-首次激活或创建子用户时，Olares 会生成一个随机密码用于初始设置。完成身份验证后，系统会提示用户通过 LarePass 将这个初始密码更换为更强的自定义密码。
+首次激活或创建子用户时，beOS Pro 会生成一个随机密码用于初始设置。完成身份验证后，系统会提示用户通过 beOS Pro app 将这个初始密码更换为更强的自定义密码。
### 一次性密码
-当用户执行登录等敏感操作时，Olares 要求用户输入 LarePass 生成的一次性双因素认证码。
+当用户执行登录等敏感操作时，beOS Pro 要求用户输入 beOS Pro app 生成的一次性双因素认证码。
## 了解更多
### 用户
-- [创建 Olares ID](../../manual/get-started/create-olares-id.md)
+- [创建 beOS ID](../../manual/get-started/create-beos-id.md)
- [用户角色](../../manual/olares/settings/roles-permissions.md)
### 开发者
diff --git a/docs/zh/developer/concepts/application.md b/docs/zh/developer/concepts/application.md
index fc819b2f7..c3e34f0f5 100644
--- a/docs/zh/developer/concepts/application.md
+++ b/docs/zh/developer/concepts/application.md
@@ -1,19 +1,19 @@
---
outline: [2, 3]
-description: Olares 应用系统的核心概念，包括应用标识符、类型分类和权限体系。阐述系统应用、社区应用和集群范围应用的特性及依赖关系。
+description: beOS Pro 应用系统的核心概念，包括应用标识符、类型分类和权限体系。阐述系统应用、社区应用和集群范围应用的特性及依赖关系。
---
# 应用
-本文介绍 Olares 中应用标识符、类型、权限以及与应用市场集成相关的核心概念。
+本文介绍 beOS Pro 中应用标识符、类型、权限以及与应用市场集成相关的核心概念。
## 应用标识符
-在 Olares 中，每个应用都有两个标识符：应用名称和应用 ID。
+在 beOS Pro 中，每个应用都有两个标识符：应用名称和应用 ID。
### 应用名称
-应用名称由 Indexer 分配。Olares 团队维护的 Indexer 仓库是 [apps](https://github.com/beclab/apps)。应用在该仓库中的目录名即为其应用名称。
+应用名称由 Indexer 分配。beOS Pro 团队维护的 Indexer 仓库是 [apps](https://github.com/beclab/apps)。应用在该仓库中的目录名即为其应用名称。
### 应用 ID
@@ -23,11 +23,11 @@ description: Olares 应用系统的核心概念，包括应用标识符、类型
## 应用类型
-Olares 包含多种类型的应用。你可以通过控制面板查看系统的各类应用，并通过命名空间来识别具体的应用类型。
+beOS Pro 包含多种类型的应用。你可以通过控制面板查看系统的各类应用，并通过命名空间来识别具体的应用类型。
### 系统应用
-系统应用包括 Kubernetes、Kubesphere、Olares 组件和必要的硬件驱动。系统级命名空间包括：
+系统应用包括 Kubernetes、Kubesphere、beOS Pro 组件和必要的硬件驱动。系统级命名空间包括：
```
os-system
@@ -42,11 +42,11 @@ kube-public
kube-node-lease
gpu-system
```
-其中，`os-system` 是 Olares 开发的组件。集群级的应用以及系统提供的各种数据库中间件都安装在这个命名空间下。
+其中，`os-system` 是 beOS Pro 开发的组件。集群级的应用以及系统提供的各种数据库中间件都安装在这个命名空间下。
### 用户级系统应用
-Olares 支持多用户，并为管理员和普通成员用户提供两个不同的系统应用命名空间：
+beOS Pro 支持多用户，并为管理员和普通成员用户提供两个不同的系统应用命名空间：
- **user-space-{本地名称}**
@@ -59,7 +59,7 @@ Olares 支持多用户，并为管理员和普通成员用户提供两个不同
- Profile
- Vault
- 这些应用之间存在相互调用，同时调用系统底层接口（如 Kubernetes 的 `api-server` 接口）。为了确保系统安全，Olares 将它们统一部署在独立的 `user-space` 命名空间中，通过沙盒机制隔离，防止恶意程序的攻击和非法访问。
+ 这些应用之间存在相互调用，同时调用系统底层接口（如 Kubernetes 的 `api-server` 接口）。为了确保系统安全，beOS Pro 将它们统一部署在独立的 `user-space` 命名空间中，通过沙盒机制隔离，防止恶意程序的攻击和非法访问。
- **user-system-{本地名称}**
@@ -73,7 +73,7 @@ Olares 支持多用户，并为管理员和普通成员用户提供两个不同
社区应用是由第三方开发者创建和维护的应用，涵盖从生产力工具、娱乐应用到数据分析工具等多种用途。
-社区应用的命名空间由两部分组成：应用名称和用户的[本地名称](olares-id.md#olares-id-的组成)，例如：
+社区应用的命名空间由两部分组成：应用名称和用户的[本地名称](beos-id.md#beos-id-结构)，例如：
```
n8n-alice
@@ -82,14 +82,14 @@ gitlab-client-bob
### 共享应用
-**共享应用**是 Olares 平台中的一类特殊社区应用，旨在为 Olares 集群内的所有用户提供统一的、共享的资源或服务。
+**共享应用**是 beOS Pro 平台中的一类特殊社区应用，旨在为 beOS Pro 集群内的所有用户提供统一的、共享的资源或服务。
共享应用的特点包括：
-* **集中管理**：只有管理员账户才安装共享版应用的核心服务。管理员负责在 Olares 集群内**安装、配置和托管**应用的服务、资源以及运行环境。
-* **易于识别**：在 Olares 应用市场中，共享版应用通常带有 "Shared" 标识以便用户区分。
+* **集中管理**：只有管理员账户才安装共享版应用的核心服务。管理员负责在 beOS Pro 集群内**安装、配置和托管**应用的服务、资源以及运行环境。
+* **易于识别**：在 beOS Pro 应用市场中，共享版应用通常带有 "Shared" 标识以便用户区分。
* **灵活访问**：访问共享版应用的方式取决于共享应用本身的形态：
- * **无界面的后端服务**: 对于通常作为后台服务运行、没有图形用户界面的共享应用（如 Ollama），无需专用的引用应用。该服务会暴露标准 API 和共享入口，可直接被任何兼容的第三方客户端（如 LobeChat 和 Open WebUI）调用。成员安装客户端后，将其指向共享应用的 API 端点，该端点可在 Olares **设置** > **应用** > **入口** 中获取。
+ * **无界面的后端服务**: 对于通常作为后台服务运行、没有图形用户界面的共享应用（如 Ollama），无需专用的引用应用。该服务会暴露标准 API 和共享入口，可直接被任何兼容的第三方客户端（如 LobeChat 和 Open WebUI）调用。成员安装客户端后，将其指向共享应用的 API 端点，该端点可在 beOS Pro **设置** > **应用** > **入口** 中获取。
* **自带用户界面的完整应用**: 对于共享版应用本身就包含完整用户界面和后端服务的（如 ComfyUI 共享版 或 Dify 共享版），管理员和集群中的其他用户都可通过直接安装该共享版应用本身获取服务的访问入口。
### 依赖项
@@ -118,5 +118,4 @@ Service Provider 机制使社区应用能够与系统应用、其他社区应用
- 开发者
- [在 Olares 上开发应用程序](../develop/index.md)
-
+ [在 beOS Pro 上开发应用程序](../develop/index.md)
diff --git a/docs/zh/developer/concepts/architecture.md b/docs/zh/developer/concepts/architecture.md
index 1f59a1a43..02101bc31 100644
--- a/docs/zh/developer/concepts/architecture.md
+++ b/docs/zh/developer/concepts/architecture.md
@@ -1,9 +1,9 @@
---
-description: Olares 的 BEC 架构概述，阐述分布式节点实现数据存储和安全机制。包含 Snowinning Protocol、Olares OS 和 LarePass 三大核心组件。
+description: beOS Pro 的 BEC 架构概述，阐述分布式节点实现数据存储和安全机制。包含 Snowinning Protocol、beOS Pro 和 beOS Pro app 三大核心组件。
---
-# Olares 架构
+# beOS Pro 架构
-Olares 通过区块链-边缘-客户端（BEC）架构提供了新一代去中心化互联网框架。BEC 通过在不同平台间合理分配信息，实现了数据存储的去中心化和安全性提升。
+beOS Pro 通过区块链-边缘-客户端（BEC）架构提供了新一代去中心化互联网框架。BEC 通过在不同平台间合理分配信息，实现了数据存储的去中心化和安全性提升。
@@ -11,13 +11,13 @@ Olares 通过区块链-边缘-客户端（BEC）架构提供了新一代去中
- **边缘层**：作为用户的去中心化网络节点，在私有边缘服务器上托管个人数据，如文档、聊天记录和照片。数据始终保持在边缘层用户的掌控之中，保障隐私和本地数据主权。
- **客户端**：身份钱包应用，让用户可以安全地管理身份并与自托管系统进行交互，同时保持对数字凭证的所有权和隐私控制。
-## Olares 核心组件
+## beOS Pro 核心组件
-对应 BEC 架构，Olares 包含以下核心组件：
+对应 BEC 架构，beOS Pro 包含以下核心组件：
-- [**Olares ID**](olares-id.md)：一个整合了去中心化身份标识（DID）、可验证凭证（VC）和信誉数据的去中心化身份与信誉系统。通过实现去中心化环境中的透明和可验证交互来增强信任。
-- [**Olares OS**](https://github.com/beclab/Olares)：专为边缘设备设计的完整自托管操作系统。用户可以托管和管理自己的数据和应用，将个人边缘设备转变为强大的主权云系统。
-- [**LarePass**](https://olares.cn/larepass)：安全统一的界面软件，连接用户和其 Olares 系统。提供身份管理、远程访问、设备管理和数据存储等核心功能，确保与 Olares 的无缝交互。
+- [**beOS ID**](beos-id.md)：一个整合了去中心化身份标识（DID）、可验证凭证（VC）和信誉数据的去中心化身份与信誉系统。通过实现去中心化环境中的透明和可验证交互来增强信任。
+- [**beOS Pro**](https://github.com/beclab/beOS Pro)：专为边缘设备设计的完整自托管操作系统。用户可以托管和管理自己的数据和应用，将个人边缘设备转变为强大的主权云系统。
+- [**beOS Pro app**](https://beos.local/larepass)：安全统一的界面软件，连接用户和其 beOS Pro 系统。提供身份管理、远程访问、设备管理和数据存储等核心功能，确保与 beOS Pro 的无缝交互。
## 延伸阅读
diff --git a/docs/zh/developer/concepts/beos-id.md b/docs/zh/developer/concepts/beos-id.md
new file mode 100644
index 000000000..4f27e00d6
--- /dev/null
+++ b/docs/zh/developer/concepts/beos-id.md
@@ -0,0 +1,69 @@
+---
+description: 了解 beOS ID 的定义、结构及其用途，涵盖个人/组织/实体域名类型，并阐释与去中心化标识符 (DID) 的关系。
+---
+
+# beOS ID
+
+本文介绍 beOS ID——beOS Pro 生态中的身份与信任基础。
+
+## 什么是 beOS ID？
+
+**beOS ID** 是一种去中心化身份与信用系统，用于实现信息和价值的安全、无需信任的交换。它是你在 beOS Pro 生态中的数字身份，使个人和组织无需依赖第三方即可自主管理身份。
+
+beOS ID 具备以下特点：
+
+- **唯一性**：类似电子邮件地址，例如 `alice123@beos.local`
+- **易读易记**：人性化命名，便于分享
+- **与 DID 绑定**：具备加密安全与可验证性
+
+## 为什么需要 beOS ID？
+
+beOS ID 带来无缝访问、增强安全与个性化体验：
+
+- **便捷访问**：系统自动为应用配置子域名与访问策略，可随时随地通过域名访问。
+- **免费 HTTPS 证书**：beOS Pro 域名自带 TLS 证书，保障加密通信。
+- **个性化且易记**：ID 与域名简单易记，展示独特在线身份。
+
+例如，若你的 beOS ID 为 `alice123@beos.local`，系统自动分配以下地址：
+
+- `alice123.beos.local`：个人主页
+- `desktop.alice123.beos.local`：访问 beOS Pro 桌面
+- `files.alice123.beos.local`：访问文件管理器应用
+
+## beOS ID 结构
+
+格式与邮箱类似，由两部分组成：
+
+- **本地名（前缀）**
+- **域名（后缀）**
+
+如 `alice123@beos.local` 中，`alice123` 为本地名，`beos.local` 为域名。本地名在域内唯一，保证整体唯一性。
+
+### 域名类型
+
+beOS Pro 提供三类域名：
+
+| 类型 | 说明 |
+|------------|--------------------------------------------|
+| 个人域名 | 供个人使用，目前提供默认域名 `beos.local` |
+| 组织域名 | 供企业/组织使用，管理员可在成员离职时回收 |
+| 实体域名 | 供应用或其他无法归类为个人/组织的实体使用 |
+
+### 个人 beOS ID 创建方式
+
+- **[快速创建](../../manual/larepass/create-account.md#快速创建)**：选择一个可用的本地名立即生成 ID。
+- **[高级创建](../../manual/larepass/create-account.md#高级创建)**：使用可验证凭证 (VC) 将现有可信身份（如邮箱）绑定至 beOS ID。
+ - 通过 OAuth 验证
+ - 将社交身份与 beOS Pro DID 建立加密关联
+
+## beOS ID 与 DID 的关系
+
+**DID**（去中心化标识符）是无需中心化机构即可验证的唯一标识。但 DID 难以记忆，日常使用不便。
+
+beOS ID 采用类似邮箱的可读格式，使 DID 更易用，同时保持其安全性。用户创建 beOS Pro 账户时，系统同时生成并绑定 DID。详情见 [Account 生命周期](./account#understand-the-stage-of-account)。
+
+## 深入阅读
+
+- [创建 beOS ID](../../manual/larepass/create-account.md)
+- [去中心化标识符 (DID)](did.md)
+- [Gmail issuer 服务](/zh/developer/contribute/olares-id/verifiable-credential/olares.md#gmail-issuer-service)
diff --git a/docs/zh/developer/concepts/data.md b/docs/zh/developer/concepts/data.md
index 76b661102..61dc789c7 100644
--- a/docs/zh/developer/concepts/data.md
+++ b/docs/zh/developer/concepts/data.md
@@ -1,15 +1,15 @@
---
outline: [2, 3]
-description: Olares 数据管理架构说明，阐述文件系统类型、应用存储路径和数据库支持体系。包括 JuiceFS、PostgreSQL、MongoDB 和 Redis 的技术特性。
+description: beOS Pro 数据管理架构说明，阐述文件系统类型、应用存储路径和数据库支持体系。包括 JuiceFS、PostgreSQL、MongoDB 和 Redis 的技术特性。
---
# 数据
-数据通常存储在文件系统和数据库中，其中数据库又是建立在文件系统之上的。以下是 Olares 在这两方面的设计理念：
+数据通常存储在文件系统和数据库中，其中数据库又是建立在文件系统之上的。以下是 beOS Pro 在这两方面的设计理念：
**文件系统方面**：
- Olares 设计用于多节点集群环境。因此在开发应用时，需要考虑程序被调度到不同节点时对文件系统的访问问题。我们致力于对开发者屏蔽这些细节。
+ beOS Pro 设计用于多节点集群环境。因此在开发应用时，需要考虑程序被调度到不同节点时对文件系统的访问问题。我们致力于对开发者屏蔽这些细节。
**数据库方面**：
@@ -26,17 +26,17 @@ description: Olares 数据管理架构说明，阐述文件系统类型、应用
### JuiceFS
-Olares 采用 [JuiceFS](https://juicefs.com) 作为底层的多物理节点共享文件系统方案。这样应用可以通过最简单的 HostPath PV 方式获得跨节点的文件访问能力，使 Pod 能够在集群中自由调度。
+beOS Pro 采用 [JuiceFS](https://juicefs.com) 作为底层的多物理节点共享文件系统方案。这样应用可以通过最简单的 HostPath PV 方式获得跨节点的文件访问能力，使 Pod 能够在集群中自由调度。
针对 JuiceFS 的后端对象存储方案，我们提供了 S3 和 MinIO 两种选择。
-默认情况下，Olares 在本地安装时使用本地文件系统（FS）。不过，如果在运行 [`olares-cli prepare`](../install/cli/prepare.md) 命令时指定了 `--with-juicefs=true` 选项，系统就会安装并使用 JuiceFS，同时会搭建一个 MinIO 实例作为后端存储。
+默认情况下，beOS Pro 在本地安装时使用本地文件系统（FS）。不过，如果在运行 [`beos-cli prepare`](../install/cli/prepare.md) 命令时指定了 `--with-juicefs=true` 选项，系统就会安装并使用 JuiceFS，同时会搭建一个 MinIO 实例作为后端存储。
### 本地磁盘
某些应用系统中可能会出现密集的文件系统读写操作，这些密集的文件系统读写往往是碎片化的随机读写。在现有的各种分布式存储集群方案中，对于这种密集的碎片化随机读写操作，很容易造成 I/O 或 CPU 消耗过高（通常表现为较高的 I/O Wait）。
-Olares 提供的最佳实践是充分利用节点的本地硬盘作为文件缓冲区。虽然节点的本地硬盘容量有限，但由于基本采用 SSD 硬盘，具有较高的读写性能。应用读写文件时会先在节点本地硬盘上进行缓冲，然后批量异步写入分布式文件系统。这样可以将大部分碎片化的随机读写转化为少量的顺序读写，大幅提升系统 I/O 效率。
+beOS Pro 提供的最佳实践是充分利用节点的本地硬盘作为文件缓冲区。虽然节点的本地硬盘容量有限，但由于基本采用 SSD 硬盘，具有较高的读写性能。应用读写文件时会先在节点本地硬盘上进行缓冲，然后批量异步写入分布式文件系统。这样可以将大部分碎片化的随机读写转化为少量的顺序读写，大幅提升系统 I/O 效率。
## 应用存储路径
@@ -46,39 +46,39 @@ Olares 提供的最佳实践是充分利用节点的本地硬盘作为文件缓
`UserData` 存储路径用于存放变动不频繁但需要跨应用访问的文件，如文档、照片和视频等。
-应用可以通过在 `OlaresManifest.yaml` 中申请 [UserData](../develop/package/manifest.md#userdata) 权限来获取 `Home` 目录下某个目录的访问权限。比如 PhotoPrism 可以申请 `Picture` 目录的权限，qBittorrent 和 Jellyfin 可以申请 `Downloads` 目录的权限。
+应用可以通过在 `BeOSManifest.yaml` 中申请 [UserData](../develop/package/manifest.md#userdata) 权限来获取 `Home` 目录下某个目录的访问权限。比如 PhotoPrism 可以申请 `Picture` 目录的权限，qBittorrent 和 Jellyfin 可以申请 `Downloads` 目录的权限。
### AppData
`AppData` 存储路径用于存放变动不频繁但需要跨节点的数据，比如配置文件。
-应用可以在 `OlaresManifest.yaml` 中申请 [AppData](../develop/package/manifest.md#appdata) 权限。
+应用可以在 `BeOSManifest.yaml` 中申请 [AppData](../develop/package/manifest.md#appdata) 权限。
### AppCache
`AppCache` 存储路径分配给需要直接操作磁盘且性能要求较好的应用。比如系统数据库、应用日志和缓存等。缺点是无法跨节点访问。
-应用可以在 `OlaresManifest.yaml` 中申请 [AppCache](../develop/package/manifest.md#appcache) 权限。
+应用可以在 `BeOSManifest.yaml` 中申请 [AppCache](../develop/package/manifest.md#appcache) 权限。
## [PostgreSQL](../develop/advanced/database.md#rds)
-作为最受欢迎的开源关系型数据库之一，PostgreSQL 具有出色的性能和丰富的插件功能。Olares 在系统中部署了 PostgreSQL，同时集成了广受欢迎的 Citus 分布式数据库插件。通过 Olares 应用运行时组件中的 PG Operator 进行集群管理，用户可以轻松扩展 PostgreSQL 节点数量，并随整个 Olares 系统进行备份或恢复。
+作为最受欢迎的开源关系型数据库之一，PostgreSQL 具有出色的性能和丰富的插件功能。beOS Pro 在系统中部署了 PostgreSQL，同时集成了广受欢迎的 Citus 分布式数据库插件。通过 beOS Pro 应用运行时组件中的 PG Operator 进行集群管理，用户可以轻松扩展 PostgreSQL 节点数量，并随整个 beOS Pro 系统进行备份或恢复。
-如果开发者在应用中声明的 PostgreSQL 数据库为分布式类型，那么 Olares 会在 Citus 上构建其数据库，让应用充分利用分布式 PG 数据库的能力。
+如果开发者在应用中声明的 PostgreSQL 数据库为分布式类型，那么 beOS Pro 会在 Citus 上构建其数据库，让应用充分利用分布式 PG 数据库的能力。
## [MongoDB](../develop/advanced/database.md#nosql)
-MongoDB 作为 NoSQL 的代表，在物联网领域有着广泛的应用场景。通过部署 [Percona Operator for MongoDB](https://github.com/percona/percona-server-mongodb-operator)，开发者在 Olares 中就拥有了云原生版本的 MongoDB 集群。
+MongoDB 作为 NoSQL 的代表，在物联网领域有着广泛的应用场景。通过部署 [Percona Operator for MongoDB](https://github.com/percona/percona-server-mongodb-operator)，开发者在 beOS Pro 中就拥有了云原生版本的 MongoDB 集群。
-与 PostgreSQL 一样，Olares 也统一管理 MongoDB 的备份和恢复。用户无需具备任何 DBA 技术能力，就能轻松实现定时备份、增量备份、定点恢复等功能。
+与 PostgreSQL 一样，beOS Pro 也统一管理 MongoDB 的备份和恢复。用户无需具备任何 DBA 技术能力，就能轻松实现定时备份、增量备份、定点恢复等功能。
## [Redis](../develop/advanced/database.md#cache)
-毫无疑问，Redis 可以说是目前最受欢迎的内存缓存软件。它拥有丰富的指令，并基于 Key-Value 数据衍生出多种数据类型。很多系统甚至将其作为 KV 数据存储使用。Olares 也在系统中部署了定制的 [Redis Cluster Operator](https://github.com/beclab/redis-cluster-operator)，提供云原生版本的 Redis 集群。
+毫无疑问，Redis 可以说是目前最受欢迎的内存缓存软件。它拥有丰富的指令，并基于 Key-Value 数据衍生出多种数据类型。很多系统甚至将其作为 KV 数据存储使用。beOS Pro 也在系统中部署了定制的 [Redis Cluster Operator](https://github.com/beclab/redis-cluster-operator)，提供云原生版本的 Redis 集群。
-Olares 同样接管了 Redis 集群的备份和恢复工作，用户无需为 Redis 集群提供任何单独的运维操作。
+beOS Pro 同样接管了 Redis 集群的备份和恢复工作，用户无需为 Redis 集群提供任何单独的运维操作。
-此外，由于 Redis 集群本身缺乏数据隔离机制，Olares 还开发了代理层工具来实现数据的 `namespace` 机制。这种隔离机制对开发者来说是完全透明的，开发者无需在代码中对数据键做任何特殊处理，只需在应用 chart 中简单配置即可实现多应用、多用户之间的数据隔离。
+此外，由于 Redis 集群本身缺乏数据隔离机制，beOS Pro 还开发了代理层工具来实现数据的 `namespace` 机制。这种隔离机制对开发者来说是完全透明的，开发者无需在代码中对数据键做任何特殊处理，只需在应用 chart 中简单配置即可实现多应用、多用户之间的数据隔离。
:::tip 提示
系统使用的是 Redis 集群版本，与单机版 Redis 有所不同，建议参考 Redis 官方文档。
@@ -86,9 +86,9 @@ Olares 同样接管了 Redis 集群的备份和恢复工作，用户无需为 Re
## 备份
-备份是 Olares 的备份和恢复模块。
+备份是 beOS Pro 的备份和恢复模块。
-它帮助用户将整个 Olares 备份到 Olares Space，同时也支持用户自定义存储位置。
+它帮助用户将整个 beOS Pro 备份到 Remote Space，同时也支持用户自定义存储位置。
备份操作可以按日或按周进行。每个备份计划的第一次备份是全量备份，作为该备份计划的第一个快照。后续快照均为增量备份。
@@ -98,7 +98,7 @@ Olares 同样接管了 Redis 集群的备份和恢复工作，用户无需为 Re
- 数据库数据，如 Redis、MongoDB、PostgreSQL 等
- 文件系统数据，如用户通过文件管理器上传的视频、图片、各类文档等
-备份组件还具备数据恢复能力。可以将备份快照下载到本地服务器或 Olares Space，通过重建 Kubernetes、数据库和用户个人信息，恢复出一个完整的 Olares。
+备份组件还具备数据恢复能力。可以将备份快照下载到本地服务器或 Remote Space，通过重建 Kubernetes、数据库和用户个人信息，恢复出一个完整的 beOS Pro。
## 了解更多
diff --git a/docs/zh/developer/concepts/did.md b/docs/zh/developer/concepts/did.md
index 32f1fa563..cd7fa79de 100644
--- a/docs/zh/developer/concepts/did.md
+++ b/docs/zh/developer/concepts/did.md
@@ -1,5 +1,5 @@
---
-description: 了解去中心化标识符（DID）的定义、结构与在 Olares ID 中的助记词派生流程。
+description: 了解去中心化标识符（DID）的定义、结构与在 beOS ID 中的助记词派生流程。
---
# 去中心化标识符（Decentralized Identifier，DID）
@@ -22,7 +22,7 @@ DID 的核心目标是让个人与组织掌控自身身份信息，并可在无
## DID 的派生
-在 Olares ID 中，DID 通过类似区块链地址的助记词算法 **自生成**，流程如下：
+在 beOS ID 中，DID 通过类似区块链地址的助记词算法 **自生成**，流程如下：
> 助记词 → 私钥 → 公钥 → DID 链上地址
diff --git a/docs/zh/developer/concepts/index.md b/docs/zh/developer/concepts/index.md
index f5dca57fc..0bce80cd3 100644
--- a/docs/zh/developer/concepts/index.md
+++ b/docs/zh/developer/concepts/index.md
@@ -1,19 +1,19 @@
---
-description: Olares 系统核心概念说明文档，阐述架构设计、身份验证、应用管理、网络配置和数据安全等基础理论。适合开发者理解系统运作机制。
+description: beOS Pro 系统核心概念说明文档，阐述架构设计、身份验证、应用管理、网络配置和数据安全等基础理论。适合开发者理解系统运作机制。
---
# 概述
-本章节帮助你了解 Olares 系统，加深对 Olares 工作原理的理解。在以下场景中可以参考本章节：
+本章节帮助你了解 beOS Pro 系统，加深对 beOS Pro 工作原理的理解。在以下场景中可以参考本章节：
-- 开发 Olares 应用
+- 开发 beOS Pro 应用
- 管理系统部署
- 排查故障问题
- 优化系统性能
-通过以下概念来理解 Olares：
+通过以下概念来理解 beOS Pro：
- [架构](system-architecture.md)
-- [Olares ID](olares-id.md)
+- [beOS ID](beos-id.md)
- [账户](account.md)
- [应用](application.md)
- [网络](network.md)
diff --git a/docs/zh/developer/concepts/network.md b/docs/zh/developer/concepts/network.md
index b294883f0..be382afbd 100644
--- a/docs/zh/developer/concepts/network.md
+++ b/docs/zh/developer/concepts/network.md
@@ -1,14 +1,14 @@
---
outline: [2, 3]
-description: Olares 网络架构设计说明，阐述应用入口类型、本地访问机制、端点配置和内部网络安全策略的基本原理。
+description: beOS Pro 网络架构设计说明，阐述应用入口类型、本地访问机制、端点配置和内部网络安全策略的基本原理。
---
# 网络
-Olares 为用户提供无障碍且安全灵活的网络解决方案。本文档介绍与应用访问相关的核心概念。
+beOS Pro 为用户提供无障碍且安全灵活的网络解决方案。本文档介绍与应用访问相关的核心概念。
## 入口
-每个 Olares 应用可以配置一个或多个入口来接入外部访问。入口分为三种类型：
+每个 beOS Pro 应用可以配置一个或多个入口来接入外部访问。入口分为三种类型：
### 公开入口
@@ -24,20 +24,20 @@ Olares 为用户提供无障碍且安全灵活的网络解决方案。本文档
### 内部入口
- 功能与私有入口类似。
-- 通过 LarePass VPN 访问应用时，无需身份验证。
+- 通过 beOS Pro app VPN 访问应用时，无需身份验证。
## 端点
-端点是用户与应用交互的访问地址或接入点（access point）。简单来说，就是在浏览器地址栏中输入的 URL，用于访问特定的 Olares 应用或其功能。
+端点是用户与应用交互的访问地址或接入点（access point）。简单来说，就是在浏览器地址栏中输入的 URL，用于访问特定的 beOS Pro 应用或其功能。
-典型的 Olares 应用端点格式如下：
+典型的 beOS Pro 应用端点格式如下：
https://{routeID}.{domain}
-例如：`https://vault.alice123.olares.cn`，其中：
+例如：`https://vault.alice123.beos.local`，其中：
- `vault` 是系统应用的路由 ID
-- `alice123.olares.cn` 是由 Olares ID `alice123@olares.cn` 演变而来
+- `alice123.beos.local` 是由 beOS ID `alice123@beos.local` 演变而来
## 路由 ID
@@ -48,23 +48,23 @@ Olares 为用户提供无障碍且安全灵活的网络解决方案。本文档
- 示例：`desktop`（桌面）、`market`（应用市场）
- 社区应用
- 使用 8 位随机字符串 + 入口索引（从 0 开始）
- - 示例：对于路由 ID 为 `92d76a13` 且有两个入口的应用，第一个入口为`92d76a130`，访问 URL 为 `92d76a130.alice.olares.cn`
+ - 示例：对于路由 ID 为 `92d76a13` 且有两个入口的应用，第一个入口为`92d76a130`，访问 URL 为 `92d76a130.alice.beos.local`
::: tip 注意
-- 应用地址包含 Olares ID
-- 入口索引指的是入口在 [`OlaresManifest.yaml`](../develop/package/manifest.md) 中定义的多个入口中的位置。
+- 应用地址包含 beOS ID
+- 入口索引指的是入口在 [`BeOSManifest.yaml`](../develop/package/manifest.md) 中定义的多个入口中的位置。
:::
-## Olares 内部网络
+## beOS Pro 内部网络
-Olares 在网关架构中采用多层代理路由设计。流量经过多个层级分发：
+beOS Pro 在网关架构中采用多层代理路由设计。流量经过多个层级分发：
`集群` -> `用户` -> `应用` -> `服务组件`
-在应用内部，Olares 实现了多层安全防护。
+在应用内部，beOS Pro 实现了多层安全防护。
- **命名空间隔离**
@@ -87,4 +87,4 @@ Olares 在网关架构中采用多层代理路由设计。流量经过多个层
## 了解更多
- [为应用设置自定义域名](../../manual/olares/settings/custom-app-domain.md#自定义域名)
-- [通过专用网络访问 Olares 应用](../../manual/larepass/private-network.md)
+- [通过专用网络访问 beOS Pro 应用](../../manual/larepass/private-network.md)
diff --git a/docs/zh/developer/concepts/olares-id.md b/docs/zh/developer/concepts/olares-id.md
deleted file mode 100644
index 152ebc426..000000000
--- a/docs/zh/developer/concepts/olares-id.md
+++ /dev/null
@@ -1,69 +0,0 @@
----
-description: 了解 Olares ID 的定义、结构及其用途，涵盖个人/组织/实体域名类型，并阐释与去中心化标识符 (DID) 的关系。
----
-
-# Olares ID
-
-本文介绍 Olares ID——Olares 生态中的身份与信任基础。
-
-## 什么是 Olares ID？
-
-**Olares ID** 是一种去中心化身份与信用系统，用于实现信息和价值的安全、无需信任的交换。它是你在 Olares 生态中的数字身份，使个人和组织无需依赖第三方即可自主管理身份。
-
-Olares ID 具备以下特点：
-
-- **唯一性**：类似电子邮件地址，例如 `alice123@olares.com`
-- **易读易记**：人性化命名，便于分享
-- **与 DID 绑定**：具备加密安全与可验证性
-
-## 为什么需要 Olares ID？
-
-Olares ID 带来无缝访问、增强安全与个性化体验：
-
-- **便捷访问**：系统自动为应用配置子域名与访问策略，可随时随地通过域名访问。
-- **免费 HTTPS 证书**：Olares 域名自带 TLS 证书，保障加密通信。
-- **个性化且易记**：ID 与域名简单易记，展示独特在线身份。
-
-例如，若你的 Olares ID 为 `alice123@olares.com`，系统自动分配以下地址：
-
-- `alice123.olares.com`：个人主页
-- `desktop.alice123.olares.com`：访问 Olares 桌面
-- `files.alice123.olares.com`：访问文件管理器应用
-
-## Olares ID 结构
-
-格式与邮箱类似，由两部分组成：
-
-- **本地名（前缀）**
-- **域名（后缀）**
-
-如 `alice123@olares.com` 中，`alice123` 为本地名，`olares.com` 为域名。本地名在域内唯一，保证整体唯一性。
-
-### 域名类型
-
-Olares 提供三类域名：
-
-| 类型 | 说明 |
-|------------|--------------------------------------------|
-| 个人域名 | 供个人使用，目前提供默认域名 `olares.com` |
-| 组织域名 | 供企业/组织使用，管理员可在成员离职时回收 |
-| 实体域名 | 供应用或其他无法归类为个人/组织的实体使用 |
-
-### 个人 Olares ID 创建方式
-
-- **[快速创建](../../manual/larepass/create-account.md#快速创建)**：选择一个可用的本地名立即生成 ID。
-- **[高级创建](../../manual/larepass/create-account.md#高级创建)**：使用可验证凭证 (VC) 将现有可信身份（如邮箱）绑定至 Olares ID。
- - 通过 OAuth 验证
- - 将社交身份与 Olares DID 建立加密关联
-
-## Olares ID 与 DID 的关系
-
-**DID**（去中心化标识符）是无需中心化机构即可验证的唯一标识。但 DID 难以记忆，日常使用不便。
-
-Olares ID 采用类似邮箱的可读格式，使 DID 更易用，同时保持其安全性。用户创建 Olares 账户时，系统同时生成并绑定 DID。详情见 [Account 生命周期](./account#understand-the-stage-of-account)。
-
-## 深入阅读
-
-- [创建 Olares ID](../../manual/larepass/create-account.md)
-- [去中心化标识符 (DID)](did.md)
-- [Gmail issuer 服务](/zh/developer/contribute/olares-id/verifiable-credential/olares.md#gmail-issuer-service)
diff --git a/docs/zh/developer/concepts/registry.md b/docs/zh/developer/concepts/registry.md
index 72361ab55..0487c962b 100644
--- a/docs/zh/developer/concepts/registry.md
+++ b/docs/zh/developer/concepts/registry.md
@@ -4,7 +4,7 @@ description: 介绍在区块链上注册 DID 的机制，涵盖智能合约实
# 区块链上的 DID Registry
-当生成 DID 后，用户需在 **DID Registry** 中注册其所有权。W3C 标准并未规定具体实现方式，**Olares ID** 采用 [智能合约](/zh/developer/contribute/olares-id/contract/contract.md#smart-contract.md) 完成注册，具有以下优势：
+当生成 DID 后，用户需在 **DID Registry** 中注册其所有权。W3C 标准并未规定具体实现方式，**beOS ID** 采用 [智能合约](/zh/developer/contribute/olares-id/contract/contract.md#smart-contract.md) 完成注册，具有以下优势：
- **去中心化**：无需依赖中心化机构或服务商
- **抗审查**：结构对审查与干预具有韧性
@@ -13,13 +13,13 @@ description: 介绍在区块链上注册 DID 的机制，涵盖智能合约实
发行方可将关键的 DID 元数据上传到 Registry，包括：
- DID 本身
-- [Olares ID](olares-id.md)
+- [beOS ID](beos-id.md)
- RSA 公钥
- 其他相关信息
DID 元数据体积小、更新频率低，适合使用主流区块链技术进行存储与检索，系统开销低且效率高。
-目前，Olares ID 的智能合约部署在以太坊二层网络 **[Optimistic Rollups](https://optimism.io/)** 上。
+目前，beOS ID 的智能合约部署在以太坊二层网络 **[Optimistic Rollups](https://optimism.io/)** 上。
::: info
值得一提的是，Web5 开发团队已从 ION Registry 迁移至 **DHT（分布式哈希表）网络**。与 Layer2 区块链相比，DHT 拥有更高去中心化程度，但在高节点数量下保持效率、稳定性与数据完整性更为复杂。
diff --git a/docs/zh/developer/concepts/reputation.md b/docs/zh/developer/concepts/reputation.md
index 986e5e938..ca92e871d 100644
--- a/docs/zh/developer/concepts/reputation.md
+++ b/docs/zh/developer/concepts/reputation.md
@@ -1,5 +1,5 @@
---
-description: 介绍 Olares ID 去中心化声誉系统的设计理念与实现，包括区块链数据记录、开放算法、自定义评估与实体域名支持。
+description: 介绍 beOS ID 去中心化声誉系统的设计理念与实现，包括区块链数据记录、开放算法、自定义评估与实体域名支持。
---
# 去中心化声誉系统
@@ -17,9 +17,9 @@ description: 介绍 Olares ID 去中心化声誉系统的设计理念与实现
- **难以定制**：用户无法自由选择或调整评分算法
- **易受操纵**：实体可付费刷分或提升排名，降低评分可信度
-## Olares ID 的去中心化方案
+## beOS ID 的去中心化方案
-**Olares ID** 基于 **DID** 与 **VC** 构建去中心化声誉系统，实现透明、可控与可信：
+**beOS ID** 基于 **DID** 与 **VC** 构建去中心化声誉系统，实现透明、可控与可信：
@@ -37,6 +37,6 @@ description: 介绍 Olares ID 去中心化声誉系统的设计理念与实现
## 实体域名：去中心化声誉的基石
-在 Olares ID 中，抽象实体（电影、应用、做市商等）虽不属于个人或组织，却同样需要 DID。**实体域名** 解决了该需求，使这些抽象实体拥有去中心化身份。
+在 beOS ID 中，抽象实体（电影、应用、做市商等）虽不属于个人或组织，却同样需要 DID。**实体域名** 解决了该需求，使这些抽象实体拥有去中心化身份。
实体域名的目标是支持协议为抽象实体构建声誉系统——从而催生 Web3 版 IMDb、Yelp、LinkedIn 等平台，真正实现自治、可信的去中心化声誉网络。
diff --git a/docs/zh/developer/concepts/secrets.md b/docs/zh/developer/concepts/secrets.md
index 55effe922..c07863c38 100644
--- a/docs/zh/developer/concepts/secrets.md
+++ b/docs/zh/developer/concepts/secrets.md
@@ -1,26 +1,26 @@
---
-description: Olares 密钥管理体系说明，包括 Vault 项目、凭据、密钥和集成凭据的分类与安全机制，以及讲解敏感数据的存储策略。
+description: beOS Pro 密钥管理体系说明，包括 Vault 项目、凭据、密钥和集成凭据的分类与安全机制，以及讲解敏感数据的存储策略。
---
# 密钥
-Olares 根据使用场景对密钥进行分类并采用不同的管理方式。
+beOS Pro 根据使用场景对密钥进行分类并采用不同的管理方式。
| | 数据类型 | 存储位置 | 泄露风险 | 使用方式 |
|----------|-------------------------------------|------------------------------------|-----------------------------------------------------|--------------------------------------------------|
-| Vault 项目 | 包括网站密码、数
据库密码、区块链
私钥等 | Vault | Olares 中的加密数据确保第三方即使登录也无法查看 | 每次使用都需要 LarePass 签名 |
-| 凭证 | 安全认证后获取
的系统访问凭据：
令牌、Cookie 等 | [Infisical](https://infisical.com/) | 第三方在 Olares 中通过特定步骤认证后可查看 | 应用程序获得 Provider 权限后可通过 API 使用 |
+| Vault 项目 | 包括网站密码、数
据库密码、区块链
私钥等 | Vault | beOS Pro 中的加密数据确保第三方即使登录也无法查看 | 每次使用都需要 beOS Pro app 签名 |
+| 凭证 | 安全认证后获取
的系统访问凭据：
令牌、Cookie 等 | [Infisical](https://infisical.com/) | 第三方在 beOS Pro 中通过特定步骤认证后可查看 | 应用程序获得 Provider 权限后可通过 API 使用 |
| 密钥 | Pod 容器中使用的
敏感数据，如数据
库连接和管理账号 | ETCD | 可在[控制面板](../../manual/olares/controlhub/manage-workload.md#保密字典)直接查看 | 用于 Helm 部署模板，通过 `valueFrom -> secretKeyRef` 注入环境变量 |
## 集成凭据
-用户可以通过在设置中登录第三方服务账号，让 Olares 中的应用访问外部服务凭据。例如：
+用户可以通过在设置中登录第三方服务账号，让 beOS Pro 中的应用访问外部服务凭据。例如：
-- 登录 Olares Space 后，备份服务可以请求令牌用于自动后台备份
+- 登录 Remote Space 后，备份服务可以请求令牌用于自动后台备份
- 登录 Google 后，文件功能可以与 Google Drive 中的数据同步
-Olares 中的应用程序可以通过[Service Provider](../develop/advanced/provider.md) 获取这些第三方服务凭据。
+beOS Pro 中的应用程序可以通过[Service Provider](../develop/advanced/provider.md) 获取这些第三方服务凭据。
## 应用凭据
-- Olares 中的应用可以通过系统提供的接口管理和使用[密钥](../develop/advanced/secret.md)
+- beOS Pro 中的应用可以通过系统提供的接口管理和使用[密钥](../develop/advanced/secret.md)
- 应用生成的凭据仅限该应用程序使用
\ No newline at end of file
diff --git a/docs/zh/developer/concepts/self-sovereign-network.md b/docs/zh/developer/concepts/self-sovereign-network.md
index 6dd367dea..4394e25c9 100644
--- a/docs/zh/developer/concepts/self-sovereign-network.md
+++ b/docs/zh/developer/concepts/self-sovereign-network.md
@@ -1,10 +1,10 @@
---
-description: 介绍 Olares 基于 DID 与区块链的自主主权网络及 BEC 架构，实现去信任的信息与价值交换。
+description: 介绍 beOS Pro 基于 DID 与区块链的自主主权网络及 BEC 架构，实现去信任的信息与价值交换。
---
# 自主主权网络（Self-Sovereign Network）
-借助 [**DID**](did.md) 与 [**区块链注册表**](registry.md)，Olares 构建了基于 **Blockchain-Edge-Client（BEC）** 架构的点对点自主主权网络，消除了对第三方信任的依赖，使任意两方均可直接进行信息与价值的去信任交换。
+借助 [**DID**](did.md) 与 [**区块链注册表**](registry.md)，beOS Pro 构建了基于 **Blockchain-Edge-Client（BEC）** 架构的点对点自主主权网络，消除了对第三方信任的依赖，使任意两方均可直接进行信息与价值的去信任交换。
## BEC 架构
@@ -12,15 +12,15 @@ BEC 通过在最合适的位置分布存储数据，实现彻底去中心化，
- **Edge（边缘）**
用户将个人数据（文档、聊天记录、照片等）存储在私有边缘服务器上。用户与他人或服务的所有交互都通过该服务器完成。
- > Olares：开源自托管操作系统，运行在本地边缘设备，即此组件的具体实现。
+ > beOS Pro：开源自托管操作系统，运行在本地边缘设备，即此组件的具体实现。
- **Blockchain（区块链）**
高价值数据（如 DID 和交易）存储在链上，确保透明、安全与可发现性。
- > Olares ID 通过智能合约将 DID Registry 部署于 EVM 兼容链（如 Optimism）。
+ > beOS ID 通过智能合约将 DID Registry 部署于 EVM 兼容链（如 Optimism）。
- **Client（客户端）**
身份钱包应用，私钥保存在移动设备，用户完全掌控。
- > LarePass：Olares 的全功能客户端，即此组件的具体实现。
+ > beOS Pro app：beOS Pro 的全功能客户端，即此组件的具体实现。
## 通过 BEC 进行去信任信息交换
@@ -36,7 +36,7 @@ BEC 通过在最合适的位置分布存储数据，实现彻底去中心化，
## 通过 Otmoic 协议进行去信任价值交换
-**Otmoic** 是建立在 **Olares ID** 之上的去信任自动价值交换协议，目标是在 **公用品** 场景中提供公平价格与透明交易。
+**Otmoic** 是建立在 **beOS ID** 之上的去信任自动价值交换协议，目标是在 **公用品** 场景中提供公平价格与透明交易。
@@ -48,4 +48,4 @@ BEC 通过在最合适的位置分布存储数据，实现彻底去中心化，
| VC-驱动的 KYC | 通过可验证凭证完成身份验证而不损害去中心化 |
| 基于 RFQ 的价格发现 | 高效的 **Request-for-Quote** 模式进行价格撮合 |
| 原子交换（Atomic Swap） | 支持链上无信任原子交换交易 |
-| 自动做市 | 流动性提供者可在 **Olares** 上安装应用参与自动做市 |
+| 自动做市 | 流动性提供者可在 **beOS Pro** 上安装应用参与自动做市 |
diff --git a/docs/zh/developer/concepts/system-architecture.md b/docs/zh/developer/concepts/system-architecture.md
index fb92ed96a..58f33edce 100644
--- a/docs/zh/developer/concepts/system-architecture.md
+++ b/docs/zh/developer/concepts/system-architecture.md
@@ -1,13 +1,13 @@
---
outline: [2, 3]
-description: 全面了解 Olares 架构，涵盖基础设施、平台服务和应用框架。
+description: 全面了解 beOS Pro 架构，涵盖基础设施、平台服务和应用框架。
---
-# Olares 架构
+# beOS Pro 架构
-本文详细介绍了 Olares 的架构，阐述了各层及其组件的用途和功能。
+本文详细介绍了 beOS Pro 的架构，阐述了各层及其组件的用途和功能。
-
+
## 基础设施
@@ -15,11 +15,11 @@ description: 全面了解 Olares 架构，涵盖基础设施、平台服务和
### 容器编排
-Olares 根据底层环境支持不同的 Kubernetes 发行版：
+beOS Pro 根据底层环境支持不同的 Kubernetes 发行版：
- Linux 环境（包括 WSL、PVE、LXC、树莓派）：用户可以选择安装 [Kubernetes](https://kubernetes.io/) 或轻量级的 [K3s](https://k3s.io/)。K3s 作为默认选项，在本地硬件上能提供更好的性能和资源效率。
- macOS：使用 [minikube](https://minikube.sigs.k8s.io/) 在 Linux 虚拟机中部署 Kubernetes，确保跨平台的统一体验。
-无论选择哪种 Kubernetes 发行版，用户都能获得一致的 Olares 核心能力和使用体验。
+无论选择哪种 Kubernetes 发行版，用户都能获得一致的 beOS Pro 核心能力和使用体验。
### 网络
@@ -29,46 +29,46 @@ Olares 根据底层环境支持不同的 Kubernetes 发行版：
- [Calico](https://www.tigera.io/project-calico/)：提供高性能容器网络接口（CNI），负责容器和虚拟机之间的通信，并提供高级网络策略控制。
- [Envoy](https://www.envoyproxy.io/)：高性能、可扩展的边缘和服务代理。Envoy 作为服务间通信的中间件，处理负载均衡、服务发现、安全通信和可观测性。它可以作为独立的反向代理或 API 网关使用，也常作为服务网格（Service Mesh）的数据平面组件。
-这些组件共同确保了 Olares 中网络的健壮性、可扩展性和安全性。
+这些组件共同确保了 beOS Pro 中网络的健壮性、可扩展性和安全性。
### 分布式存储
-Olares 为单节点和多节点设置提供灵活的存储方案：
+beOS Pro 为单节点和多节点设置提供灵活的存储方案：
- 本地存储：适用于单节点部署，提供最佳读写性能。
- [S3](https://aws.amazon.com/s3/)：云存储选项，适合通过 S3 或任何兼容 S3 的服务进行云部署。
-- [MinIO](https://min.io/)：自托管部署的分布式存储解决方案。用户可以通过 Olares 搭建 MinIO 集群，或挂载现有的 MinIO 集群。
+- [MinIO](https://min.io/)：自托管部署的分布式存储解决方案。用户可以通过 beOS Pro 搭建 MinIO 集群，或挂载现有的 MinIO 集群。
这种方案确保了应用能够访问所需的存储机制，无论是本地还是分布式环境。
### 分布式键值存储
-Olares 使用 [etcd](https://etcd.io/) 作为分布式键值存储。etcd 是存储和管理 Kubernetes 集群数据的核心组件。
+beOS Pro 使用 [etcd](https://etcd.io/) 作为分布式键值存储。etcd 是存储和管理 Kubernetes 集群数据的核心组件。
### GPU 管理
-Olares 利用 CUDA 驱动、NVIDIA 设备插件和 nvshare 等组件协同工作，有效管理和分配 GPU 资源：
+beOS Pro 利用 CUDA 驱动、NVIDIA 设备插件和 nvshare 等组件协同工作，有效管理和分配 GPU 资源：
- CUDA：作为 GPU 硬件和操作系统之间的核心接口。
- NVIDIA 设备插件：使 GPU 资源能够被容器或 Pod 发现、调度和分配。
- [nvshare](https://github.com/grgalex/nvshare)：允许多个容器或 Pod 共享单个 GPU，实现 GPU 的共享和独占使用，提高 GPU 利用率。
:::info 注意
-Olares 目前的 GPU 管理功能仅支持单节点单 GPU 的部署场景。
+beOS Pro 目前的 GPU 管理功能仅支持单节点单 GPU 的部署场景。
:::
-从 Olares v1.11 开始，支持 [CUDA](https://developer.nvidia.com/cuda-toolkit)（12.4 及以上版本）。当宿主机环境的 CUDA 配置变更时，可以通过 `olares-cli` 通知 Olares 集群进行配置。
+从 beOS Pro v1.11 开始，支持 [CUDA](https://developer.nvidia.com/cuda-toolkit)（12.4 及以上版本）。当宿主机环境的 CUDA 配置变更时，可以通过 `beos-cli` 通知 beOS Pro 集群进行配置。
### 容器管理
-Olares 使用轻量级容器运行时 [containerd](../install/installation-overview.md#容器运行时containerd) 进行容器化部署。
+beOS Pro 使用轻量级容器运行时 [containerd](../install/installation-overview.md#容器运行时containerd) 进行容器化部署。
-### Olares Controller Panel
+### beOS Pro Controller Panel
-Olares 的集群管理通过以下工具实现：
+beOS Pro 的集群管理通过以下工具实现：
-- [olares-cli](../install/cli/olares-cli.md)：命令行工具，用于管理 Olares 集群、应用和硬件节点等。
-- [olaresd](../install/installation-overview.md#系统守护进程olaresd)：Olares 的守护进程，用于监控硬件和网络变更、处理集群升级和重启等。
+- [beos-cli](../install/cli/beos-cli.md)：命令行工具，用于管理 beOS Pro 集群、应用和硬件节点等。
+- [beosd](../install/installation-overview.md#系统守护进程beosd)：beOS Pro 的守护进程，用于监控硬件和网络变更、处理集群升级和重启等。
-这些工具简化了 Olares 的安装、维护和扩展过程。
+这些工具简化了 beOS Pro 的安装、维护和扩展过程。
## 平台层
@@ -76,7 +76,7 @@ Olares 的集群管理通过以下工具实现：
### 关系型数据库
-Olares 使用 [PostgreSQL](https://www.postgresql.org/) 16 作为主要关系型数据库。所有应用共享一个 PostgreSQL 实例，每个应用都有专用账号以实现隔离。PostgreSQL 同时作为全文搜索引擎和向量数据库。
+beOS Pro 使用 [PostgreSQL](https://www.postgresql.org/) 16 作为主要关系型数据库。所有应用共享一个 PostgreSQL 实例，每个应用都有专用账号以实现隔离。PostgreSQL 同时作为全文搜索引擎和向量数据库。
多节点方面，使用 [Citus](https://github.com/citusdata/citus) 实现，但该方案仍在调试中。
@@ -84,7 +84,7 @@ Olares 使用 [PostgreSQL](https://www.postgresql.org/) 16 作为主要关系型
### 键值缓存
-Olares 集成了 [KVRocks](https://github.com/apache/incubator-kvrocks)，这是一个基于 RocksDB 构建的 Redis 兼容持久化键值存储。KVRocks 在内存和磁盘存储之间取得平衡，比 Redis 集群更节省资源，但性能略有损失。
+beOS Pro 集成了 [KVRocks](https://github.com/apache/incubator-kvrocks)，这是一个基于 RocksDB 构建的 Redis 兼容持久化键值存储。KVRocks 在内存和磁盘存储之间取得平衡，比 Redis 集群更节省资源，但性能略有损失。
### 消息队列
@@ -92,29 +92,29 @@ Olares 集成了 [KVRocks](https://github.com/apache/incubator-kvrocks)，这是
### 分布式文件系统
-Olares 采用云原生分布式文件系统 [JuiceFS](https://juicefs.com/)，为应用提供 POSIX 兼容接口。当使用 S3 或 MinIO 作为存储后端时，JuiceFS 确保跨节点的无缝文件访问。
+beOS Pro 采用云原生分布式文件系统 [JuiceFS](https://juicefs.com/)，为应用提供 POSIX 兼容接口。当使用 S3 或 MinIO 作为存储后端时，JuiceFS 确保跨节点的无缝文件访问。
### 工作流管理
-Olares 使用 [Argo Workflows](https://argoproj.github.io/) 进行工作流编排。这个 Kubernetes 原生工具可以自动化复杂任务流程，如 Olares 分布式推荐引擎所需的任务。目前这个功能尚未对第三方应用开放。
+beOS Pro 使用 [Argo Workflows](https://argoproj.github.io/) 进行工作流编排。这个 Kubernetes 原生工具可以自动化复杂任务流程，如 beOS Pro 分布式推荐引擎所需的任务。目前这个功能尚未对第三方应用开放。
### 密钥管理
-Olares 集成了两个密钥管理解决方案：
+beOS Pro 集成了两个密钥管理解决方案：
-- [Vault](https://github.com/beclab/olares/tree/main/apps/vault)：保护账号、密码和助记词等敏感数据。它对密钥进行加密，即使服务器被攻破，数据也能保持安全。Vault 由 Olares 团队基于 [Padloc](https://padloc.app/) 开发。
-- [Infisical](https://infisical.com/)：用于管理敏感信息和防止 Olares 开发中的密钥泄露。
+- [Vault](https://github.com/beclab/olares/tree/main/apps/vault)：保护账号、密码和助记词等敏感数据。它对密钥进行加密，即使服务器被攻破，数据也能保持安全。Vault 由 beOS Pro 团队基于 [Padloc](https://padloc.app/) 开发。
+- [Infisical](https://infisical.com/)：用于管理敏感信息和防止 beOS Pro 开发中的密钥泄露。
### 可观测性
-Olares 通过以下组件提供可观测性：
+beOS Pro 通过以下组件提供可观测性：
- [Prometheus](https://prometheus.io/)：用于系统监控和资源使用跟踪。它为**仪表盘**和**应用市场**等应用提供资源使用方面的数据。
-- [OpenTelemetry](https://opentelemetry.io/)\*：使用基于 eBPF 的监控，实现 Olares 系统内请求工作流的追踪。*（开发中）*
+- [OpenTelemetry](https://opentelemetry.io/)\*：使用基于 eBPF 的监控，实现 beOS Pro 系统内请求工作流的追踪。*（开发中）*
### 其他中间件
-Olares 在**应用市场**中集成了一些常用中间件，如用于可视化的 [Grafana](https://grafana.com/)、用于文档存储的 [MongoDB](https://www.mongodb.com/) 和用于混沌测试的 [Chaos Mesh](https://chaos-mesh.org/)。
+beOS Pro 在**应用市场**中集成了一些常用中间件，如用于可视化的 [Grafana](https://grafana.com/)、用于文档存储的 [MongoDB](https://www.mongodb.com/) 和用于混沌测试的 [Chaos Mesh](https://chaos-mesh.org/)。
## 应用框架
@@ -122,7 +122,7 @@ Olares 在**应用市场**中集成了一些常用中间件，如用于可视化
### 认证与授权
-Olares 使用 [LLDAP](https://github.com/lldap/lldap) 管理用户账号并为应用提供 LDAP（轻量目录访问协议）服务。
+beOS Pro 使用 [LLDAP](https://github.com/lldap/lldap) 管理用户账号并为应用提供 LDAP（轻量目录访问协议）服务。
此外，[Authelia](https://www.authelia.com/) 添加了认证和授权支持，包括多因素认证和单点登录（SSO）。
@@ -131,32 +131,32 @@ Olares 使用 [LLDAP](https://github.com/lldap/lldap) 管理用户账号并为
应用治理的组件包括：
- [app-service](https://github.com/beclab/app-service)：处理应用生命周期管理和资源分配。
- [system-server](https://github.com/beclab/system-server)：管理应用间接口调用的权限，以及应用和数据库中间件之间的网络路由。
-- image-server：与 app-service 协作管理 Olares 应用所需的容器镜像。
+- image-server：与 app-service 协作管理 beOS Pro 应用所需的容器镜像。
- [bfl](https://github.com/beclab/bfl)：聚合后端接口，代理所有系统服务的请求，如用户隔离的系统信息和集群信息。
### 网络连接
-Olares 通过以下方式提供安全灵活的网络连接：
-- 反向代理：Olares 支持 [Cloudflare Tunnel](https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/)、Olares Tunnel 和自建 FRP 三种方案。
+beOS Pro 通过以下方式提供安全灵活的网络连接：
+- 反向代理：beOS Pro 支持 [Cloudflare Tunnel](https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/)、beOS Pro Tunnel 和自建 FRP 三种方案。
- [Tailscale](https://tailscale.com/)：让用户可以从任何地方安全访问系统。
- [Headscale](https://github.com/juanfont/headscale)：Tailscale 控制面板的自托管实现。
### 文件服务
文件服务的组件包括：
- File server：提供基本的文件管理服务。
-- [Seafile](https://www.seafile.com/)：Dropbox 的开源替代品，用于文件同步。Olares 深度集成了 Seafile，使用户能将分散在多个设备上的文件同步到统一的存储库中。
+- [Seafile](https://www.seafile.com/)：Dropbox 的开源替代品，用于文件同步。beOS Pro 深度集成了 Seafile，使用户能将分散在多个设备上的文件同步到统一的存储库中。
- Drive server：提供与 Google Drive、Dropbox 和 S3 等外部存储服务的接入。
- Media server：使用 [ffmpeg](https://github.com/FFmpeg/FFmpeg) 流式传输视频文件。
### 知识服务
知识服务的组件包括：
-- Knowledge：存储用户通过浏览器扩展收集或通过 LarePass 从手机分享的网页、视频、音频、PDF 和 EPUB 等内容。这个存储库也被分布式推荐引擎用来存储其推荐的结果。
+- Knowledge：存储用户通过浏览器扩展收集或通过 beOS Pro app 从手机分享的网页、视频、音频、PDF 和 EPUB 等内容。这个存储库也被分布式推荐引擎用来存储其推荐的结果。
- Download：使用 [aria2](https://aria2.github.io/) 和 [youtube-dlp](https://github.com/yt-dlp/yt-dlp) 下载文件、磁力链接和在线视频。
- Search：为 Knowledge 和**文件管理器**的内容提供全文搜索。
- [RSSHub](https://github.com/DIYgod/RSSHub)：生成 RSS 源以便订阅内容。
### AI 服务
-Olares 提供以下 AI 能力：
+beOS Pro 提供以下 AI 能力：
- 模型服务*：提供模型托管服务。*（开发中）*
- RAG 接口*：为文件、文章、图片和视频提供检索增强生成（RAG）服务。*（开发中）*
- Agent 和工作流编排*：管理 Agent 和工具工作流。*（开发中）*
@@ -170,7 +170,7 @@ Olares 提供以下 AI 能力：
## 系统应用
-Olares 预装了用于管理文件、知识、密码和系统本身的应用。
+beOS Pro 预装了用于管理文件、知识、密码和系统本身的应用。
用户可以通过应用市场安装更多应用。
@@ -208,13 +208,13 @@ Olares 预装了用于管理文件、知识、密码和系统本身的应用。
### 控制面板
-Olares 的控制台，提供对系统及其环境的精确和自主控制。
+beOS Pro 的控制台，提供对系统及其环境的精确和自主控制。
### Studio
-用于构建和部署 Olares 应用的开发工具。
+用于构建和部署 beOS Pro 应用的开发工具。
## 了解更多
-- 要开始使用 Olares，请参阅[快速开始](../../manual/get-started/index.md)。
-- 要深入了解 Olares 的内部原理，请参阅[概念](index.md)中的主题。
-- 要详细了解 Olares 中各组件如何被编排，请参阅 [Olares 安装概述](../install/index.md)。
\ No newline at end of file
+- 要开始使用 beOS Pro，请参阅[快速开始](../../manual/get-started/index.md)。
+- 要深入了解 beOS Pro 的内部原理，请参阅[概念](index.md)中的主题。
+- 要详细了解 beOS Pro 中各组件如何被编排，请参阅 [beOS Pro 安装概述](../install/index.md)。
\ No newline at end of file
diff --git a/docs/zh/developer/concepts/wallet.md b/docs/zh/developer/concepts/wallet.md
index b1b296b7e..d64912786 100644
--- a/docs/zh/developer/concepts/wallet.md
+++ b/docs/zh/developer/concepts/wallet.md
@@ -1,32 +1,32 @@
---
-description: 了解数字身份钱包 LarePass 的核心功能，包括 Olares ID（去中心化身份证明）与 VC 的管理及与 Olares 的无缝交互。
+description: 了解数字身份钱包 beOS Pro app 的核心功能，包括 beOS ID（去中心化身份证明）与 VC 的管理及与 beOS Pro 的无缝交互。
---
# 身份钱包应用（Identity Wallet App）
**数字身份钱包** 是自主主权身份 (SSI) 生态的重要工具，可让用户无需中心化机构即可管理去中心化标识符（DID）、凭证 (VC) 以及与数字服务的交互。
-**LarePass** 是 Olares 的官方身份钱包应用，为基于 Olares ID 的自托管去中心化操作系统提供安全、便捷的身份管理与访问能力。
+**beOS Pro app** 是 beOS Pro 的官方身份钱包应用，为基于 beOS ID 的自托管去中心化操作系统提供安全、便捷的身份管理与访问能力。
-## 管理 Olares ID
+## 管理 beOS ID
-创建 Olares 账户时，系统会先生成 DID 并绑定至新的 Olares ID。LarePass 提供以下功能来简化 Olares ID 的管理：
+创建 beOS Pro 账户时，系统会先生成 DID 并绑定至新的 beOS ID。beOS Pro app 提供以下功能来简化 beOS ID 的管理：
-
+
-- **Olares ID 创建**
+- **beOS ID 创建**
- 快速创建（无需 VC 绑定）
- 高级创建（绑定 VC，现支持 Gmail Issuer Service）
-- **备份 / 导入 Olares ID**
+- **备份 / 导入 beOS ID**
使用助记词快速备份与恢复账户
- **多身份管理**
- 同时管理多个 DID / Olares ID
+ 同时管理多个 DID / beOS ID
-详细说明参见 [使用 LarePass 管理账户](../../manual/larepass/create-account.md)。
+详细说明参见 [使用 beOS Pro app 管理账户](../../manual/larepass/create-account.md)。
## 管理可验证凭证（VC）
-LarePass 支持绑定至 Olares ID 的 VC 全流程操作，包括签名、验证、发现与呈现：
+beOS Pro app 支持绑定至 beOS ID 的 VC 全流程操作，包括签名、验证、发现与呈现：
@@ -35,5 +35,5 @@ LarePass 支持绑定至 Olares ID 的 VC 全流程操作，包括签名、验
- **发现与检索**：便捷查看各身份对应的 VC 列表
::: tip 说明
-以上为 LarePass 与身份钱包相关的核心功能。更多使用方法请参阅 [LarePass 文档](../../manual/larepass/)。
+以上为 beOS Pro app 与身份钱包相关的核心功能。更多使用方法请参阅 [beOS Pro app 文档](../../manual/larepass/)。
:::
diff --git a/docs/zh/developer/contribute/olares-id/contract/architecture.md b/docs/zh/developer/contribute/olares-id/contract/architecture.md
index 2931c2eed..d5f59676e 100644
--- a/docs/zh/developer/contribute/olares-id/contract/architecture.md
+++ b/docs/zh/developer/contribute/olares-id/contract/architecture.md
@@ -94,7 +94,7 @@ graph TB
### 内联汇编 (Inline Assembly)
-我们使用基于内联汇编的切片类型来解析和遍历 Olares ID 的层级，这可以避免复制子字符串并降低 Gas 消耗。
+我们使用基于内联汇编的切片类型来解析和遍历 beOS ID 的层级，这可以避免复制子字符串并降低 Gas 消耗。
## 附录 - 需求
@@ -104,9 +104,9 @@ graph TB
- 为 DID 记录 IPv4/IPv6、头像、RSA 公钥等信息
- 为未来可能出现的新需求扩展存储数据
-### Olares ID
+### beOS ID
-- 为 Olares ID 区分两种 DID：组织 (Organization) 或个人 (Individual)
+- 为 beOS ID 区分两种 DID：组织 (Organization) 或个人 (Individual)
- 为父级组织派生 DID 管理权限
### 信誉 (Reputation)
diff --git a/docs/zh/developer/contribute/olares-id/contract/contract-reputation.md b/docs/zh/developer/contribute/olares-id/contract/contract-reputation.md
index 1c0a1eb5b..969f099d1 100644
--- a/docs/zh/developer/contribute/olares-id/contract/contract-reputation.md
+++ b/docs/zh/developer/contribute/olares-id/contract/contract-reputation.md
@@ -32,7 +32,7 @@
身份验证有两种解决方案：
-- 使用 DID 的所有者 (owner) 提交交易 (tx)，并让 Tagger 调用 Olares DID 合约的接口进行身份验证。
+- 使用 DID 的所有者 (owner) 提交交易 (tx)，并让 Tagger 调用 beOS Pro DID 合约的接口进行身份验证。
- 使用 DID 的所有者签署一个自定义的 EIP-712 消息，并使用一个转发器 (forwarder) 将交易发送上链。Tagger 将使用消息的签名者进行身份验证。
:::tip 提示
@@ -92,5 +92,5 @@ Otmoic Reputation 合约使用 DID 所有者的 EIP-712 签名进行身份验证
reputation-.- read/write -.->version1ratings
reputation-.->event
```
-Olares App Market Reputation 合约同样使用 DID 所有者的 EIP-712 签名进行身份验证。合约的评分数据存储在实体 `..app.myterminus.com` 的 `ratings` 标签中，而评论数据则以以太坊事件的形式发布，而不是存储在链上。
+beOS Pro App Market Reputation 合约同样使用 DID 所有者的 EIP-712 签名进行身份验证。合约的评分数据存储在实体 `..app.myterminus.com` 的 `ratings` 标签中，而评论数据则以以太坊事件的形式发布，而不是存储在链上。
:::
diff --git a/docs/zh/developer/contribute/olares-id/contract/contract.md b/docs/zh/developer/contribute/olares-id/contract/contract.md
index 8bd224ff0..9d5ec9be0 100644
--- a/docs/zh/developer/contribute/olares-id/contract/contract.md
+++ b/docs/zh/developer/contribute/olares-id/contract/contract.md
@@ -1,6 +1,6 @@
# 智能合约
-Olares ID 的智能合约包含两个部分。
+beOS ID 的智能合约包含两个部分。
- [TerminusDID](https://github.com/beclab/terminusdid-contract-system/blob/main/src/core/TerminusDID.sol) 合约扮演着关键角色，并作为 [DID Registry (DID 注册表)](/developer/concepts/registry.md)。查看[合约](https://optimistic.etherscan.io/address/0x5da4fa8e567d86e52ef8da860de1be8f54cae97d)。
- 第三方协议可以基于 [TerminusDID](https://github.com/beclab/terminusdid-contract-system/blob/main/src/core/TerminusDID.sol) 扩展信誉系统。目前，已部署以下信誉协议：
@@ -9,7 +9,7 @@ Olares ID 的智能合约包含两个部分。
# TerminusDID
-TerminusDID 合约管理着一个源自 [Domain (域)](/zh/developer/concepts/olares-id.md#domain) 的层级结构。
+TerminusDID 合约管理着一个源自 [Domain (域)](/zh/developer/concepts/beos-id.md#domain) 的层级结构。
## 节点 (Node)
@@ -17,7 +17,7 @@ TerminusDID 合约管理着一个源自 [Domain (域)](/zh/developer/concepts/ol
| 属性 | 描述 |
| ---------------- |----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| name | 指定[域名 (Domain Name)](/zh/developer/concepts/olares-id#域名类型)。某些域名可与 Olares ID 互换。 |
+| name | 指定[域名 (Domain Name)](/zh/developer/concepts/beos-id.md#域名类型)。某些域名可与 beOS ID 互换。 |
| id | 每个节点也是一个遵循 **ERC-721** 标准的 NFT。其 id 是该 NFT 的唯一标识符，通过 `keccak256(name)` 计算得出。 |
| did,owner | 节点的 `owner` 和 `did`，由相同的助记词派生而来。更多详情请见[此处](/zh/developer/concepts/did.md)。\此外，存储 owner 的好处在于它遵循 **BIP44** 规范，有助于在 EVM 合约内进行节省 Gas 的签名验证。每个节点都隶属于一个 `owner`，该 `owner` 有权修改节点详情。 |
| note | 目前有三种类型：个人 (Individual)、组织 (Organization) 和实体 (Entity)。 |
@@ -44,15 +44,15 @@ TerminusDID 合约管理着一个源自 [Domain (域)](/zh/developer/concepts/ol
诸如 `root`、`com`、`io` 等抽象节点属于 Terminus 团队。
- **个人 (Individual)** \
- `myterminus.com` 属于[个人域 (Individual Domain)](/zh/developer/concepts/olares-id.md#域名类型)，由 Terminus 团队所有。
+ `myterminus.com` 属于[个人域 (Individual Domain)](/zh/developer/concepts/beos-id.md#域名类型)，由 Terminus 团队所有。
`alice.myterminus.com` 和 `bob.myterminus.com` 属于个人 Terminus 名称，由各自的用户所有。
- **组织 (Organization)** \
- `org1.com` 和 `org.io` 属于[组织域 (Organization Domain)](/zh/developer/concepts/olares-id.md#域名类型)，由域管理员所有。
+ `org1.com` 和 `org.io` 属于[组织域 (Organization Domain)](/zh/developer/concepts/beos-id.md#域名类型)，由域管理员所有。
`alice.org1.com` 和 `bob.org2.io` 属于组织 Terminus 名称，由各自的用户所有。
- **实体 (Entity)** \
- `Application Score` 属于[实体域 (Entity Domain)](/zh/developer/concepts/olares-id.md#域名类型)，由该实体的申请人所有。组织管理员和用户可以参考[域管理](https://www.google.com/search?q=../contract/manage/contract.md%23register-did)来管理他们自己的节点和子节点。
+ `Application Score` 属于[实体域 (Entity Domain)](/zh/developer/concepts/beos-id.md#域名类型)，由该实体的申请人所有。组织管理员和用户可以参考[域管理](https://www.google.com/search?q=../contract/manage/contract.md%23register-did)来管理他们自己的节点和子节点。
:::info
项目稳定后，Terminus 团队会将所有权转移给 DAO 组织的多签地址。
@@ -205,4 +205,4 @@ Otmoic 的信誉合约使用 DID 所有者的 EIP712 签名进行身份验证，
reputation-.- read/write -.->version1ratings
reputation-.->event
```
-:::
\ No newline at end of file
+:::
diff --git a/docs/zh/developer/contribute/olares-id/contract/did/design.md b/docs/zh/developer/contribute/olares-id/contract/did/design.md
index 059c371f1..606867781 100644
--- a/docs/zh/developer/contribute/olares-id/contract/did/design.md
+++ b/docs/zh/developer/contribute/olares-id/contract/did/design.md
@@ -94,7 +94,7 @@ Tagger 代表唯一有权修改该标签值的个人或程序。它可以是一
::: tip Note
我们建议你使用智能合约作为 Tagger。
- - 你可以利用 Olares DID 合约进行完整的操作者身份验证，同时实现更细粒度的自定义访问控制。请参考一些官方的 Tagger 实现。
+ - 你可以利用 beOS Pro DID 合约进行完整的操作者身份验证，同时实现更细粒度的自定义访问控制。请参考一些官方的 Tagger 实现。
- 对于复杂的标签结构或具有特殊格式的数据，使用合约 Tagger 支持在链上验证数据格式并自定义规则。例如，在官方 Tagger 中，我们将在链上验证 PKCS8 ASN.1 格式的字节数据，以防止意外为 `RSAPubKey` 标签设置无法解析的值。
:::
@@ -108,7 +108,7 @@ Tagger 代表唯一有权修改该标签值的个人或程序。它可以是一
### 流程与概念介绍
-TName 的扩展信息由 Olares DID 合约的标签系统管理。每个标签不仅有名称，还有标签类型。目前支持的类型包括 `int`, `uint`, `bool`, `string`, `address`, `bytes`, `bytesN`, `array`, `arrayN` 和 `tuple`。元组 (tuple) 支持额外的字段名。
+TName 的扩展信息由 beOS Pro DID 合约的标签系统管理。每个标签不仅有名称，还有标签类型。目前支持的类型包括 `int`, `uint`, `bool`, `string`, `address`, `bytes`, `bytesN`, `array`, `arrayN` 和 `tuple`。元组 (tuple) 支持额外的字段名。
由于标签与 TName 绑定，设置标签的步骤如下：
- 在一个 TName 中定义一个标签，包括标签名、标签类型以及元组中的字段名。设置字段名并非易事，详情请参阅文档 "DIDv2.3Tag 类型注册流程介绍"。
@@ -197,7 +197,7 @@ struct Teacher {
Student s;
```
-- Olares DID 合约提供了一组特殊的标签，称为官方标签。它在空 TName `""` 中定义，其 Tagger 被指定为 `RootTagger`。所有 TName 都可以设置官方标签，我们稍后将介绍详细的访问控制策略。
+- beOS Pro DID 合约提供了一组特殊的标签，称为官方标签。它在空 TName `""` 中定义，其 Tagger 被指定为 `RootTagger`。所有 TName 都可以设置官方标签，我们稍后将介绍详细的访问控制策略。
### 标签的访问控制
@@ -270,7 +270,7 @@ Terminus DID 合约额外增加了两个拥有转移权限的地址：
- 父 TName 的 owner
## 合约的角色
-Olares DID 合约有一个 owner 用于升级自身。它还有一个超级用户，即 `operator`，以方便进行配置。每个 TName 都有其自己的 owner。
+beOS Pro DID 合约有一个 owner 用于升级自身。它还有一个超级用户，即 `operator`，以方便进行配置。每个 TName 都有其自己的 owner。
合约 owner 的权限包括：
diff --git a/docs/zh/developer/contribute/olares-id/contract/did/faq.md b/docs/zh/developer/contribute/olares-id/contract/did/faq.md
index 04eea3ed0..c6a4d0815 100644
--- a/docs/zh/developer/contribute/olares-id/contract/did/faq.md
+++ b/docs/zh/developer/contribute/olares-id/contract/did/faq.md
@@ -2,10 +2,10 @@
## 交易费用
-当你申请 Olares ID 时，我们可以为你支付调用合约的交易费用。流程大致如下：
+当你申请 beOS ID 时，我们可以为你支付调用合约的交易费用。流程大致如下：
- 你向我们提供由你的私钥签名的数据和签名
- 我们将交易发送至智能合约
- 区块链在验证签名后会记录你的数据
-之后如果你需要管理你名下的数据，则应通过 MetaMask 调用合约。或者，你也可以使用 LarePass 登录 Olares Space，并自行支付交易费用。
\ No newline at end of file
+之后如果你需要管理你名下的数据，则应通过 MetaMask 调用合约。或者，你也可以使用 beOS Pro app 登录 Remote Space，并自行支付交易费用。
\ No newline at end of file
diff --git a/docs/zh/developer/contribute/olares-id/verifiable-credential/olares.md b/docs/zh/developer/contribute/olares-id/verifiable-credential/olares.md
index cb97312db..00001defc 100644
--- a/docs/zh/developer/contribute/olares-id/verifiable-credential/olares.md
+++ b/docs/zh/developer/contribute/olares-id/verifiable-credential/olares.md
@@ -1,17 +1,17 @@
-# Olares 的案例
+# beOS Pro 的案例
-虽然 DID 解决了去中心化网络中的身份问题，但它们通常难以记忆，不便在日常情况下使用。Olares ID 提供了一种类似于电子邮件地址的、易于记忆的熟悉格式，同时仍然利用了 DID 的强大功能和安全性。每个 Olares ID 都与一个 DID 绑定。
+虽然 DID 解决了去中心化网络中的身份问题，但它们通常难以记忆，不便在日常情况下使用。beOS ID 提供了一种类似于电子邮件地址的、易于记忆的熟悉格式，同时仍然利用了 DID 的强大功能和安全性。每个 beOS ID 都与一个 DID 绑定。
## 潜在的公平性问题
-Olares ID 注册中的**先到先得**系统可能会带来一些公平性问题，例如：
+beOS ID 注册中的**先到先得**系统可能会带来一些公平性问题，例如：
-1. **欺诈：** 例如，Olares ID `elonmusk@myterminus.com` 可能会被并非埃隆·马斯克本人注册。
+1. **欺诈：** 例如，beOS ID `elonmusk@myterminus.com` 可能会被并非埃隆·马斯克本人注册。
2. **投机：** 抢注热门名称可能会导致投机行为，这虽然可能促进早期网络活跃度，但会牺牲公平性。
-## Olares ID 的 VC 流程
+## beOS ID 的 VC 流程
-为了解决潜在的公平性问题，我们采纳了 Web5 团队提出的**自主身份 (Self-Sovereign Identity, SSI)** 服务原则，并结合了 Olares ID 的 [VC 流程](/zh/developer/concepts/vc.md#六步验证流程)。这引导我们设计了一个**发行方 (Issuer) 和验证方 (Verifier)** 流程，以协助用户申请 **Olares ID**。
+为了解决潜在的公平性问题，我们采纳了 Web5 团队提出的**自主身份 (Self-Sovereign Identity, SSI)** 服务原则，并结合了 beOS ID 的 [VC 流程](/zh/developer/concepts/vc.md#六步验证流程)。这引导我们设计了一个**发行方 (Issuer) 和验证方 (Verifier)** 流程，以协助用户申请 **beOS ID**。
@@ -19,28 +19,28 @@ Olares ID 注册中的**先到先得**系统可能会带来一些公平性问题
我们利用谷歌的 OAuth 流程来促进**可验证凭证 (Verifiable Credentials, VCs)** 的发行。简化流程如下：
-1. Alice 在钱包客户端 LarePass 中通过 OAuth 登录她的 Gmail 账户。
-2. 谷歌将 OAuth 凭证返回给 LarePass。
-3. LarePass 将 OAuth 凭证提交给发行方。
+1. Alice 在钱包客户端 beOS Pro app 中通过 OAuth 登录她的 Gmail 账户。
+2. 谷歌将 OAuth 凭证返回给 beOS Pro app。
+3. beOS Pro app 将 OAuth 凭证提交给发行方。
4. 发行方与谷歌服务器确认凭证的有效性，并检索基本信息（例如，电子邮件名称）。
5. 发行方向 Alice 发行一个与其 Gmail 地址本地部分相匹配的 VC。
-现在，Alice 就可以将已发行的 VC 存储在 LarePass 中。
+现在，Alice 就可以将已发行的 VC 存储在 beOS Pro app 中。
:::tip 注意
-- 在整个过程中，Alice 仅向 LarePass 和发行方服务透露凭证授权范围内的基本账户数据，密码和隐私由谷歌的 OAuth 协议确保。
+- 在整个过程中，Alice 仅向 beOS Pro app 和发行方服务透露凭证授权范围内的基本账户数据，密码和隐私由谷歌的 OAuth 协议确保。
- 所有用于设置 Gmail 发行方服务或其他 Web2 服务发行方服务的代码都在 GitHub 上开源。
:::
-### Olares ID 验证方服务
+### beOS ID 验证方服务
-以下是 **验证方服务 (Verifier Service)** 在 Olares 端的运作方式：
+以下是 **验证方服务 (Verifier Service)** 在 beOS Pro 端的运作方式：
-1. Alice 将她的 DID、Olares ID 和 Gmail VC 打包成一个**可验证表述 (Verifiable Presentation, VP)**，并将其与签名一同提交给验证方服务。
+1. Alice 将她的 DID、beOS ID 和 Gmail VC 打包成一个**可验证表述 (Verifiable Presentation, VP)**，并将其与签名一同提交给验证方服务。
2. 验证方服务会检查：
- 签名的有效性。
- VP 中 VC 的有效性。
- - 该 Olares ID 是否可以在区块链上注册（如果使用多个渠道，如 Gmail 和 Twitter，获取 VC 信息，可能会产生冲突）。
+ - 该 beOS ID 是否可以在区块链上注册（如果使用多个渠道，如 Gmail 和 Twitter，获取 VC 信息，可能会产生冲突）。
3. 所有检查通过后，验证方服务会将 Alice 的信息提交到区块链，并支付 Gas 费用。
-至此，Alice 成功获得了她的 **Olares ID**。例如，如果你使用 Gmail 地址 “hello@gmail.com” 进行申请，所有检查完成后，你将获得 Olares ID “hello@olares.com”。
\ No newline at end of file
+至此，Alice 成功获得了她的 **beOS ID**。例如，如果你使用 Gmail 地址 “hello@gmail.com” 进行申请，所有检查完成后，你将获得 beOS ID “hello@beos.local”。
\ No newline at end of file
diff --git a/docs/zh/developer/contribute/olares-id/verifiable-credential/overview.md b/docs/zh/developer/contribute/olares-id/verifiable-credential/overview.md
index e9ca918a6..9c8f8cf51 100644
--- a/docs/zh/developer/contribute/olares-id/verifiable-credential/overview.md
+++ b/docs/zh/developer/contribute/olares-id/verifiable-credential/overview.md
@@ -1,7 +1,7 @@
# VC 服务
本文档旨在帮助你了解如何使用以下工具，为你自己的场景配置各种 schema 并创建发行方 (Issuers) 和验证方 (Verifiers)：
-- Olares 的 [verifiable-credential-gate](https://github.com/Above-Os/verifiable-credential-gate) 和 [did-gate](https://github.com/Above-Os/did-gate)
+- beOS Pro 的 [verifiable-credential-gate](https://github.com/Above-Os/verifiable-credential-gate) 和 [did-gate](https://github.com/Above-Os/did-gate)
- tbd 团队的 [SSI Service](https://github.com/TBD54566975/ssi-service)
::: tip
diff --git a/docs/zh/developer/contribute/olares.md b/docs/zh/developer/contribute/olares.md
index f98178dad..9a3ac8f13 100644
--- a/docs/zh/developer/contribute/olares.md
+++ b/docs/zh/developer/contribute/olares.md
@@ -1,4 +1,4 @@
-# Olares
+# beOS Pro
## 目录结构
@@ -24,7 +24,7 @@ olares
| |-- system-apps
| |-- wise
| |-- wizard
-|-- build # Olares installer
+|-- build # beOS Pro installer
| |-- installer
| |-- manifest
|-- frameworks # 系统运行时组件
@@ -39,7 +39,7 @@ olares
|-- libs # 工具包库
| |-- fs-lib
|-- scripts # 用于构建或打包 olares 安装程序的脚本
-|-- third-party # Olares 中集成的第三方库或应用程序
+|-- third-party # beOS Pro 中集成的第三方库或应用程序
| |-- authelia
| |-- headscale
| |-- infisical
@@ -58,7 +58,7 @@ olares
## 如何安装
```
-curl -fsSL https://olares.sh | bash -
+curl -fsSL https://beos.sh | bash -
```
## 如何构建
@@ -88,5 +88,5 @@ make install VERSION=0.0.0-DEBUG
## 如何卸载
```bash
-olares-cli uninstall --all
+beos-cli uninstall --all
```
diff --git a/docs/zh/developer/contribute/overview.md b/docs/zh/developer/contribute/overview.md
index 59eb3a573..a128ebd40 100644
--- a/docs/zh/developer/contribute/overview.md
+++ b/docs/zh/developer/contribute/overview.md
@@ -1,6 +1,6 @@
-# Contributing To Olares
+# Contributing To beOS Pro
-## Olares
+## beOS Pro
## TermiPass
diff --git a/docs/zh/developer/contribute/system-app/deployment.md b/docs/zh/developer/contribute/system-app/deployment.md
index 9f81bdcdb..03ad9a1d9 100644
--- a/docs/zh/developer/contribute/system-app/deployment.md
+++ b/docs/zh/developer/contribute/system-app/deployment.md
@@ -16,7 +16,7 @@ outline: [2, 3]
namespace: user-space-{{ .Values.bfl.username }}
```
-3. 参照 Olares 中的应用对应 `deployment.yaml` 文件配置，添加 `annotation` 和 `label`。
+3. 参照 beOS Pro 中的应用对应 `deployment.yaml` 文件配置，添加 `annotation` 和 `label`。
```Yaml
metadata:
@@ -28,11 +28,11 @@ outline: [2, 3]
applications.app.bytetrade.io/owner: {{ .Values.bfl.username }}
applications.app.bytetrade.io/author: bytetrade.io
annotations:
- applications.app.bytetrade.io/icon: https://docs-dev.olares.com/icon.png
+ applications.app.bytetrade.io/icon: https://docs-dev.beos.local/icon.png
applications.app.bytetrade.io/title: Desktop-dev
applications.app.bytetrade.io/version: '0.0.1'
- # 此处的 entrances 配置要与 OlaresManifest.yaml 中配置保持一致
+ # 此处的 entrances 配置要与 BeOSManifest.yaml 中配置保持一致
applications.app.bytetrade.io/entrances: '[{"name":"desktop-frontend-dev", "host":"desktop-svc-dev", "port":80,"title":"Desktop-dev"}]'
```
@@ -54,14 +54,14 @@ outline: [2, 3]
targetPort: 8080 # 注意，现在 nodejs 的 dev container 端口是 8080，要改成这个端口
```
-5. 修改 `OlaresManifest.yaml` 中 `entrances` 的内容。
+5. 修改 `BeOSManifest.yaml` 中 `entrances` 的内容。
```Yaml
entrances:
- name: desktop-frontend-dev # 与 deployment 上的 annotation 一致
host: desktop-svc-dev # 与上面的 service 名字一致
port: 80
- icon: https://app.cdn.olares.com/appstore/default/defaulticon.webp
+ icon: https://app.cdn.beos.local/appstore/default/defaulticon.webp
title: Desktop-dev
authLevel: private
openMethod: default
@@ -124,7 +124,7 @@ metadata:
applications.app.bytetrade.io/owner: {{ .Values.bfl.username }}
applications.app.bytetrade.io/author: bytetrade.io
annotations:
- applications.app.bytetrade.io/icon: https://docs-dev.jointerminus.com/icon.png
+ applications.app.bytetrade.io/icon: https://docs-dev.beos.com/icon.png
applications.app.bytetrade.io/title: Desktop-dev
applications.app.bytetrade.io/version: '0.0.1'
applications.app.bytetrade.io/entrances: '[{"name":"desktop-frontend-dev", "host":"desktop-svc-dev", "port":80,"title":"Desktop-dev"}]'
diff --git a/docs/zh/developer/contribute/system-app/install.md b/docs/zh/developer/contribute/system-app/install.md
index 6b37623d9..20fda0f90 100644
--- a/docs/zh/developer/contribute/system-app/install.md
+++ b/docs/zh/developer/contribute/system-app/install.md
@@ -234,6 +234,6 @@ nginx 代理生效后，即可在 vscode 的 Terminal 中启动前后端服务
## 预览
-启动 debug 程序后，就可以在 Olares 前端，点击应用图标预览效果。
+启动 debug 程序后，就可以在 beOS Pro 前端，点击应用图标预览效果。
diff --git a/docs/zh/developer/contribute/system-app/olares-manifest.md b/docs/zh/developer/contribute/system-app/olares-manifest.md
index f353c585d..650240254 100644
--- a/docs/zh/developer/contribute/system-app/olares-manifest.md
+++ b/docs/zh/developer/contribute/system-app/olares-manifest.md
@@ -1,8 +1,8 @@
-# OlaresManifest.yaml
+# BeOSManifest.yaml
## Permission
-如果需要调用 provider 的接口，可修改 OlaresManifest.yaml 文件，在 permissions 下增加:
+如果需要调用 provider 的接口，可修改 BeOSManifest.yaml 文件，在 permissions 下增加:
```Yaml
permission:
sysData:
@@ -28,13 +28,13 @@ env:
```
---
-:::details 完整 OlaresManifest.yaml 例子
+:::details 完整 BeOSManifest.yaml 例子
```Yaml
-olaresManifest.version: v1
-olaresManifest.type: app
+beosManifest.version: v1
+beosManifest.type: app
metadata:
name: desktop
- icon: https://app.cdn.olares.com/appstore/default/defaulticon.webp
+ icon: https://app.cdn.beos.local/appstore/default/defaulticon.webp
description: app desktop
appid: desktop
title: desktop
@@ -45,7 +45,7 @@ entrances:
- name: desktop-frontend-dev
host: desktop-svc-dev
port: 80
- icon: https://app.cdn.olares.com/appstore/default/defaulticon.webp
+ icon: https://app.cdn.beos.local/appstore/default/defaulticon.webp
title: Desktop-dev
authLevel: private
openMethod: default
diff --git a/docs/zh/developer/contribute/system-app/overview.md b/docs/zh/developer/contribute/system-app/overview.md
index 3f4fe0721..235ce15fd 100644
--- a/docs/zh/developer/contribute/system-app/overview.md
+++ b/docs/zh/developer/contribute/system-app/overview.md
@@ -1,18 +1,18 @@
-# 开发 Olares 的系统应用
+# 开发 beOS Pro 的系统应用
::: tip 前置知识：
- 用 Studio 调试第三方应用
- 用 Studio 开发程序
-- 了解 Olares 的架构和机制
+- 了解 beOS Pro 的架构和机制
:::
-经过一年半开发，Olares 团队在开发系统应用时已经逐渐迁移到 Studio 上。
+经过一年半开发，beOS Pro 团队在开发系统应用时已经逐渐迁移到 Studio 上。
下面我们将演示如何在 Studio 里调试 Desktop 的前端代码。
1. 在 Studio 中创建应用
2. 配置 [deployment.yaml](./deployment)
-3. 配置 [OlaresManifest.yaml](./olares-manifest)
+3. 配置 [BeOSManifest.yaml](./olares-manifest)
4. 安装应用
5. 配置 [nginx.conf](./install)
diff --git a/docs/zh/developer/develop/advanced/account.md b/docs/zh/developer/develop/advanced/account.md
index 349ff6bf6..b81481dd4 100644
--- a/docs/zh/developer/develop/advanced/account.md
+++ b/docs/zh/developer/develop/advanced/account.md
@@ -1,6 +1,6 @@
# 账户
-如果安装在 Olares 中的应用，需要同步系统的用户信息，以此作为应用中的用户，可以在应用 chart 中申明`SysEventRegistry`来获得系统中用户事件的回调。
+如果安装在 beOS Pro 中的应用，需要同步系统的用户信息，以此作为应用中的用户，可以在应用 chart 中申明`SysEventRegistry`来获得系统中用户事件的回调。
- 用户创建回调申明
diff --git a/docs/zh/developer/develop/advanced/ai.md b/docs/zh/developer/develop/advanced/ai.md
index 3cd40a397..087b86694 100644
--- a/docs/zh/developer/develop/advanced/ai.md
+++ b/docs/zh/developer/develop/advanced/ai.md
@@ -6,7 +6,7 @@ outline: [2, 3]
## API 前缀
-`agent.{username}.olares.com/api/controllers/console/api`
+`agent.{username}.beos.local/api/controllers/console/api`
## 基本应用管理 API
### 获取 App 列表
diff --git a/docs/zh/developer/develop/advanced/cli.md b/docs/zh/developer/develop/advanced/cli.md
index a23cc80a9..daebddff8 100644
--- a/docs/zh/developer/develop/advanced/cli.md
+++ b/docs/zh/developer/develop/advanced/cli.md
@@ -1,7 +1,7 @@
# CLI
-## Olares Installation Script in Command Line
+## beOS Pro Installation Script in Command Line
```sh
# Environment variable
@@ -11,18 +11,18 @@ export LOCAL_GPU_ENABLE=1 # Enable local GPU support if ha
export LOCAL_GPU_SHARE=1 # Enable GPU sharing
# Execute installation
-curl -fsSL https://olares.sh | bash -
+curl -fsSL https://beos.sh | bash -
```
-## Olares Uninstallation Script
+## beOS Pro Uninstallation Script
-- For Olares installed on Linux, Raspberry Pi, and Windows (Windows Subsystem for Linux):
+- For beOS Pro installed on Linux, Raspberry Pi, and Windows (Windows Subsystem for Linux):
```sh
cd install-wizard && bash uninstall_cmd.sh
```
-- For Olares Installed on Mac:
+- For beOS Pro Installed on Mac:
```sh
bash uninstall_macos.sh
@@ -30,7 +30,7 @@ curl -fsSL https://olares.sh | bash -
## Resolve IP Change Issue
-Services within the Kubernetes cluster rely on stable IPs and DNS resolution provided by the cluster's internal DNS. When you change the location of your Olares, its IP address changes. This can disrupt proper DNS resolution for your cluster and make Olares inaccessible.
+Services within the Kubernetes cluster rely on stable IPs and DNS resolution provided by the cluster's internal DNS. When you change the location of your beOS Pro, its IP address changes. This can disrupt proper DNS resolution for your cluster and make beOS Pro inaccessible.
To resolve this issue, run the following command in Ubuntu in your new network environment:
@@ -39,17 +39,17 @@ cd install-wizard && bash change_ip.sh
```
:::info
-This command is not applicable to Olares on macOS yet.
+This command is not applicable to beOS Pro on macOS yet.
:::
-## Add an Olares node locally
+## Add an beOS Pro node locally
**Before Install**
- Get the `internal IP address` of the **Master** node.
- Add the current machine's `public key` to the `authorized_keys` of the user who logged into the **Master** node.
```sh
-VERSION="1.3.0" # Version of Olares installed on the master node
+VERSION="1.3.0" # Version of beOS Pro installed on the master node
curl -LO https://github.com/beclab/olares/releases/download/${VERSION}/install-wizard-v${VERSION}.tar.gz
mkdir -p install_wizard
@@ -68,7 +68,7 @@ During the installation process, you will be asked to enter relevant information
- Mount the new hard drive at `/olares/data/minio/vol2`.
```sh
-VERSION="1.3.0" # Version of Olares installed on the master node
+VERSION="1.3.0" # Version of beOS Pro installed on the master node
curl -LO https://github.com/beclab/olares/releases/download/${VERSION}/install-wizard-v${VERSION}.tar.gz
mkdir -p install_wizard
@@ -109,7 +109,7 @@ You can also add hard drives to a new node machine separately from the Master no
`/olares/data/minio/vol4`
```sh
-VERSION="1.3.0" # Version of Olares installed on the master node
+VERSION="1.3.0" # Version of beOS Pro installed on the master node
curl -LO https://github.com/beclab/olares/releases/download/${VERSION}/install-wizard-v${VERSION}.tar.gz
mkdir -p install_wizard
@@ -121,9 +121,9 @@ bash scale_minio.sh -a node -v /olares/data/minio/vol{1...4} \
-n 192.168.1.101
```
-## Install a Custom Version of Olares
+## Install a Custom Version of beOS Pro
-To debug a program that involves the startup process of Olares, you may need to build a temporary local version of Olares and replace the service you're debugging.
+To debug a program that involves the startup process of beOS Pro, you may need to build a temporary local version of beOS Pro and replace the service you're debugging.
In other scenarios, consider using Control Hub or kubectl to update services.
@@ -150,9 +150,9 @@ cd ~/install-wizard
make uninstall
```
-## Restore Olares from a Snapshot
+## Restore beOS Pro from a Snapshot
-If you have enabled the backup feature of **Olares** and have backed up system data to **S3 storage**, you can select a snapshot from a specific point in time to restore Olares.
+If you have enabled the backup feature of **beOS Pro** and have backed up system data to **S3 storage**, you can select a snapshot from a specific point in time to restore beOS Pro.
```sh
@@ -168,7 +168,7 @@ export AWS_SECRET_ACCESS_KEY=
export CLUSTER_ID=
-VERSION="1.3.0" # Version of Olares installed on the master node
+VERSION="1.3.0" # Version of beOS Pro installed on the master node
curl -LO https://github.com/beclab/olares/releases/download/${VERSION}/install-wizard-v${VERSION}.tar.gz
mkdir -p install_wizard
@@ -177,6 +177,6 @@ cd install_wizard && tar zxvf ../install-wizard-${VERSION}.tar.gz
bash publicRestoreInstaller.sh
```
-If you back up your data to the **Olares Space**, you can directly download the restoration script from **Olares Space**.
+If you back up your data to the **Remote Space**, you can directly download the restoration script from **Remote Space**.
\ No newline at end of file
diff --git a/docs/zh/developer/develop/advanced/cookie.md b/docs/zh/developer/develop/advanced/cookie.md
index 5175483f7..380b8e45c 100644
--- a/docs/zh/developer/develop/advanced/cookie.md
+++ b/docs/zh/developer/develop/advanced/cookie.md
@@ -1,20 +1,20 @@
# Cookie
-Olares 系统中采用 SSO 的模式来为整个系统（包括所有安装的应用）实现授权认证。SSO 认证模式采用无侵入设计，使用 cookie 作为认证的凭证。
+beOS Pro 系统中采用 SSO 的模式来为整个系统（包括所有安装的应用）实现授权认证。SSO 认证模式采用无侵入设计，使用 cookie 作为认证的凭证。
系统会在认证登录后设置两个 cookie：
- **authelia_session**
- cookie 内容为 SSO 的 session id。作用域为用户的 Olares domain， `.olares.com`。
+ cookie 内容为 SSO 的 session id。作用域为用户的 beOS Pro domain， `.beos.local`。
- **auth_token**
- 用户认证的 authorization token。作用域为用户的 Olares domain， `.olares.com`。
+ 用户认证的 authorization token。作用域为用户的 beOS Pro domain， `.beos.local`。
为避免 cookie 冲突，任何应用（包括系统的内建应用，三方应用）都不可以设置 cookie 到用户的域，只可设置到应用自己的域下面。
-要使用这个功能只需要在应用 chart 的 [OlaresManifest.yaml](../package/manifest.md#resetcookie) 中申明：
+要使用这个功能只需要在应用 chart 的 [BeOSManifest.yaml](../package/manifest.md#resetcookie) 中申明：
```yaml
options:
diff --git a/docs/zh/developer/develop/advanced/database.md b/docs/zh/developer/develop/advanced/database.md
index 4096726d2..661348691 100644
--- a/docs/zh/developer/develop/advanced/database.md
+++ b/docs/zh/developer/develop/advanced/database.md
@@ -1,6 +1,6 @@
# 数据库
-Olares 系统中为所有应用提供了三种最流行的数据存储集群，覆盖 RDS、NoSQL、Cache 三种数据存储场景。
+beOS Pro 系统中为所有应用提供了三种最流行的数据存储集群，覆盖 RDS、NoSQL、Cache 三种数据存储场景。
## RDS
@@ -24,9 +24,9 @@ postgres:
## NoSQL
-Olares 中默认未部署 NoSQL 集群，但可以从应用市场中安装。要设置 NoSQL 集群，管理员需要安装 [**MongoDB**](https://market.olares.com/middleware/mongodb) 中间件。 安装后，[Percona Operator for MongoDB](https://github.com/percona/percona-server-mongodb-operator) 会自动管理 **MongoDB** 集群。然后，用户可以水平扩展 **MongoDB** 集群副本，以及对数据库执行备份和恢复操作。
+beOS Pro 中默认未部署 NoSQL 集群，但可以从应用市场中安装。要设置 NoSQL 集群，管理员需要安装 [**MongoDB**](https://market.beos.local/middleware/mongodb) 中间件。 安装后，[Percona Operator for MongoDB](https://github.com/percona/percona-server-mongodb-operator) 会自动管理 **MongoDB** 集群。然后，用户可以水平扩展 **MongoDB** 集群副本，以及对数据库执行备份和恢复操作。
-你可以在 [OlaresManifest.yaml](../package/manifest.md#middleware) 中指定 MongoDB 的详细配置，如下所示：
+你可以在 [BeOSManifest.yaml](../package/manifest.md#middleware) 中指定 MongoDB 的详细配置，如下所示：
```yaml
middleware:
@@ -47,7 +47,7 @@ options:
## Cache
-在 Cache 的集群方面，Olares 选用了 Redis Cluster。并通过定制化的[Redis Cluster Operator](https://github.com/beclab/redis-cluster-operator) 对集群进行管理，实现其云原生化。可以做到很方便简单的横向副本扩展。
+在 Cache 的集群方面，beOS Pro 选用了 Redis Cluster。并通过定制化的[Redis Cluster Operator](https://github.com/beclab/redis-cluster-operator) 对集群进行管理，实现其云原生化。可以做到很方便简单的横向副本扩展。
同时，为了保证 Redis 集群数据，用户与用户之间，应用与应用之间数据隔离无干扰，系统还增加了一个 Redis 集群代理，实现数据的`命名空间`隔离，并且对应用开发者来说，完全无感知，无需关心。
@@ -60,5 +60,5 @@ middleware:
namespace: db0
```
:::info 注意
-由于 Olares 采用的是 Redis Cluster 版本，所以开发者在使用时需详细了解 Redis Cluster 的使用限制。
+由于 beOS Pro 采用的是 Redis Cluster 版本，所以开发者在使用时需详细了解 Redis Cluster 的使用限制。
:::
\ No newline at end of file
diff --git a/docs/zh/developer/develop/advanced/file-upload.md b/docs/zh/developer/develop/advanced/file-upload.md
index 800785c5d..5adef3bf1 100644
--- a/docs/zh/developer/develop/advanced/file-upload.md
+++ b/docs/zh/developer/develop/advanced/file-upload.md
@@ -4,11 +4,11 @@ outline: [2, 3]
# 文件上传
-Olares 作为一个云端系统，存在很多将本地文件上传到云端的场景。Olares 应用运行时提供了一个通用的 file-upload 组件。简化应用对文件上传需求的开发。同时，file-upload 组件还提供了断点续传功能。
+beOS Pro 作为一个云端系统，存在很多将本地文件上传到云端的场景。beOS Pro 应用运行时提供了一个通用的 file-upload 组件。简化应用对文件上传需求的开发。同时，file-upload 组件还提供了断点续传功能。
## 如何安装
-只要在应用 chart 的 [OlaresManifest.yaml](../package/manifest.md#file-upload) 中申明
+只要在应用 chart 的 [BeOSManifest.yaml](../package/manifest.md#file-upload) 中申明
```yaml
upload:
fileType:
diff --git a/docs/zh/developer/develop/advanced/kubesphere.md b/docs/zh/developer/develop/advanced/kubesphere.md
index ff81f365f..a0ce4122c 100644
--- a/docs/zh/developer/develop/advanced/kubesphere.md
+++ b/docs/zh/developer/develop/advanced/kubesphere.md
@@ -1,14 +1,14 @@
# Kubesphere
-Olares 集成了 Kubesphere 的许多高级功能，如多用户系统和集群数据监控。要从 Kubesphere** 安装官方 console 工具，请从 Olares 代码存储库下载并安装它。
+beOS Pro 集成了 Kubesphere 的许多高级功能，如多用户系统和集群数据监控。要从 Kubesphere** 安装官方 console 工具，请从 beOS Pro 代码存储库下载并安装它。
```sh
curl -LO https://github.com/Above-Os/terminus-os/raw/main/third-party/ks-console/ks-console-v3.3.0.tgz
-# username 为 Olares 的登录用户
+# username 为 beOS Pro 的登录用户
sudo helm install console ./ks-console-v3.3.0.tgz \
-n user-space- \
--set username=
```
-安装后，刷新桌面。即可在 Olares 中看到 Console 的图标。 打开 Console，可用 Olares ID 和密码登录。
+安装后，刷新桌面。即可在 beOS Pro 中看到 Console 的图标。 打开 Console，可用 beOS ID 和密码登录。
diff --git a/docs/zh/developer/develop/advanced/provider.md b/docs/zh/developer/develop/advanced/provider.md
index bdc7d8306..df3da708f 100644
--- a/docs/zh/developer/develop/advanced/provider.md
+++ b/docs/zh/developer/develop/advanced/provider.md
@@ -39,7 +39,7 @@ status:
## 申请 Provider 的访问权限
-可在 [OlaresManifest.yaml](../package/manifest.md#sysdata) 中配置：
+可在 [BeOSManifest.yaml](../package/manifest.md#sysdata) 中配置：
```Yaml
sysData:
diff --git a/docs/zh/developer/develop/advanced/secret.md b/docs/zh/developer/develop/advanced/secret.md
index 252b6265b..91bc5f183 100644
--- a/docs/zh/developer/develop/advanced/secret.md
+++ b/docs/zh/developer/develop/advanced/secret.md
@@ -4,9 +4,9 @@ outline: [2, 3]
# 密钥
-在应用中，通常需要保存一些重要的用户信息，例如外部系统的“密码”和“访问令牌”。Olares 提供了一个统一的 Vault 安全存储各种密钥（基于 Infisical）。
+在应用中，通常需要保存一些重要的用户信息，例如外部系统的“密码”和“访问令牌”。beOS Pro 提供了一个统一的 Vault 安全存储各种密钥（基于 Infisical）。
-应用只需要做简单的申请，即可获得接口访问权限。申请方式是在应用 Chart 的 [OlaresManifest.yaml](../package/manifest.md#sysdata) 中添加 `sysData` 权限，例如：
+应用只需要做简单的申请，即可获得接口访问权限。申请方式是在应用 Chart 的 [BeOSManifest.yaml](../package/manifest.md#sysdata) 中添加 `sysData` 权限，例如：
```yaml
permission:
diff --git a/docs/zh/developer/develop/advanced/terminus-info.md b/docs/zh/developer/develop/advanced/terminus-info.md
index 13b87b14d..efdbf89a8 100644
--- a/docs/zh/developer/develop/advanced/terminus-info.md
+++ b/docs/zh/developer/develop/advanced/terminus-info.md
@@ -1,17 +1,17 @@
-# olares-info
+# beos-info
-olares-info 是一个无需鉴权的接口，我们将一些系统可以对外展示的信息放在这里。可以理解为它是房子的门牌。
+beos-info 是一个无需鉴权的接口，我们将一些系统可以对外展示的信息放在这里。可以理解为它是房子的门牌。
## 外部调用
```
-https://.olares.com/api/olares-info
+https://.beos.local/api/beos-info
```
## 字段含义
```json
-interface OlaresInfo {
+interface beOS ProInfo {
olaresId: string;
wizardStatus: string;
enable_reverse_proxy: boolean;
@@ -39,11 +39,11 @@ interface OlaresInfo {
| olaresId |
- 用户的 Olares ID。格式是：username@domain.com. |
+ 用户的 beOS ID。格式是：username@domain.com. |
| wizardStatus |
- Olares 的激活状态，有以下状态：
wait_activate_vault，vault_activating，vault_activate_failed，wait_activate_system，system_activating，system_activate_failed，wait_activate_network，network_activating，network_activate_failed，wait_reset_password，completed。
当状态为 completed 时，代表用户激活成功。在用户激活成功前，不推荐第三方程序进行太多业务相关的逻辑。
+ | beOS Pro 的激活状态，有以下状态：
wait_activate_vault，vault_activating，vault_activate_failed，wait_activate_system，system_activating，system_activate_failed，wait_activate_network，network_activating，network_activate_failed，wait_reset_password，completed。
当状态为 completed 时，代表用户激活成功。在用户激活成功前，不推荐第三方程序进行太多业务相关的逻辑。
|
@@ -52,11 +52,11 @@ interface OlaresInfo {
| tailScaleEnable |
- 用户是否激活了 TailScale。如果激活了私有入口，只能通过 VPN 访问。
用途：LarePass 在连接 Olares 时，不根据这个变量决定是否增加 local 访问。 |
+ 用户是否激活了 TailScale。如果激活了私有入口，只能通过 VPN 访问。
用途：beOS Pro app 在连接 beOS Pro 时，不根据这个变量决定是否增加 local 访问。 |
| osVersion |
- Olares 的系统版本 |
+ beOS Pro 的系统版本 |
| avatar |
diff --git a/docs/zh/developer/develop/advanced/websocket.md b/docs/zh/developer/develop/advanced/websocket.md
index 7ac944e75..40875829f 100644
--- a/docs/zh/developer/develop/advanced/websocket.md
+++ b/docs/zh/developer/develop/advanced/websocket.md
@@ -4,12 +4,12 @@ outline: [2, 3]
# Websocket
-WebSocket 是现代前端开发中使用最广泛的技术之一。为了简化 Olares 应用的使用与开发，Olares 应用程序运行时提供了一个通用的 WebSocket 组件。
+WebSocket 是现代前端开发中使用最广泛的技术之一。为了简化 beOS Pro 应用的使用与开发，beOS Pro 应用程序运行时提供了一个通用的 WebSocket 组件。
## 客户端
基于 JavaScript/TypeScript 的方式开发的客户端，采用 “ws” 库。
-应用服务提供 WebSocket 的路径格式：`wss://..olares.com/ws`
+应用服务提供 WebSocket 的路径格式：`wss://..beos.local/ws`
### 发送消息
@@ -162,7 +162,7 @@ Cookie: .... // v1.0.3 版本新增功能
## 应用部署 WebSocket 服务
-应用要使用这个功能只需要在应用 Chart 的 [OlaresManifest.yaml](../package/manifest.md#websocket) 中申明。
+应用要使用这个功能只需要在应用 Chart 的 [BeOSManifest.yaml](../package/manifest.md#websocket) 中申明。
```yaml
options:
websocket:
diff --git a/docs/zh/developer/develop/app-env-index.md b/docs/zh/developer/develop/app-env-index.md
index acd8001b2..1dd531b12 100644
--- a/docs/zh/developer/develop/app-env-index.md
+++ b/docs/zh/developer/develop/app-env-index.md
@@ -1,11 +1,11 @@
---
outline: [2, 3]
-description: 了解 Olares 应用在部署期间的变量注入机制：声明式环境变量（.Values.olaresEnv）与系统自动注入的运行时 Helm Values（.Values.*）。
+description: 了解 beOS Pro 应用在部署期间的变量注入机制：声明式环境变量（.Values.beosEnv）与系统自动注入的运行时 Helm Values（.Values.*）。
---
# 环境变量概览
-Olares 应用通过 app-service 将运行时信息与配置项注入到应用的 `values.yaml` 中。应用在 Helm 模板中通过 `.Values.*` 引用这些值。
+beOS Pro 应用通过 app-service 将运行时信息与配置项注入到应用的 `values.yaml` 中。应用在 Helm 模板中通过 `.Values.*` 引用这些值。
:::info 变量与 Helm 值
本文提到的“变量”主要指 Helm 值。它们不会自动进入容器环境变量。如需在容器内使用，请在模板中显式映射到 `env:`。
@@ -13,10 +13,10 @@ Olares 应用通过 app-service 将运行时信息与配置项注入到应用的
## 变量注入通道
-Olares 通过两种通道注入变量：
+beOS Pro 通过两种通道注入变量：
-- **声明式环境变量**：开发者在 `OlaresManifest.yaml` 的 `envs` 下声明变量。在部署时，app-service 会解析这些值并将其注入到 `values.yaml` 的 `.Values.olaresEnv` 路径下。
-- **系统注入的运行时变量**：由 Olares 在部署时自动注入，无需声明。不过，某些值（例如中间件）只有在声明相关依赖后才可用。
+- **声明式环境变量**：开发者在 `BeOSManifest.yaml` 的 `envs` 下声明变量。在部署时，app-service 会解析这些值并将其注入到 `values.yaml` 的 `.Values.beosEnv` 路径下。
+- **系统注入的运行时变量**：由 beOS Pro 在部署时自动注入，无需声明。不过，某些值（例如中间件）只有在声明相关依赖后才可用。
## 下一步
diff --git a/docs/zh/developer/develop/app-env-vars.md b/docs/zh/developer/develop/app-env-vars.md
index 9be272ed4..423afe01d 100644
--- a/docs/zh/developer/develop/app-env-vars.md
+++ b/docs/zh/developer/develop/app-env-vars.md
@@ -1,18 +1,18 @@
---
outline: [2, 4]
-description: 通过 `OlaresManifest.yaml` 中的 `envs` 声明并校验应用配置，并在模板中通过 `.Values.olaresEnv` 引用变量值。
+description: 通过 `BeOSManifest.yaml` 中的 `envs` 声明并校验应用配置，并在模板中通过 `.Values.beosEnv` 引用变量值。
---
# 声明式环境变量
-在 `OlaresManifest.yaml` 中使用 `envs` 字段来声明配置参数，例如密码、API 端点或功能开关。在部署过程中，app-service 会解析这些变量，并将其注入到 `values.yaml` 的 `.Values.olaresEnv` 中。你可以在 Helm 模板中通过 {{ .Values.olaresEnv.<envName> }} 引用。
+在 `BeOSManifest.yaml` 中使用 `envs` 字段来声明配置参数，例如密码、API 端点或功能开关。在部署过程中，app-service 会解析这些变量，并将其注入到 `values.yaml` 的 `.Values.beosEnv` 中。你可以在 Helm 模板中通过 {{ .Values.beosEnv.<envName> }} 引用。
## 变量来源
声明式变量可以从应用外部管理的配置中获取值：
-- **系统变量**：Olares 集群实例级别的环境变量，在系统安装时设置，或由管理员统一管理。集群中的所有用户共享。
-- **用户变量**：Olares 用户级别的环境变量，由用户自行管理。在同一集群中，不同用户的变量彼此独立。
+- **系统变量**：beOS Pro 集群实例级别的环境变量，在系统安装时设置，或由管理员统一管理。集群中的所有用户共享。
+- **用户变量**：beOS Pro 用户级别的环境变量，由用户自行管理。在同一集群中，不同用户的变量彼此独立。
应用本身无法直接修改这些变量。如需使用，需通过 `valueFrom` 字段映射。
@@ -22,12 +22,12 @@ description: 通过 `OlaresManifest.yaml` 中的 `envs` 声明并校验应用配
以下示例演示了如何将系统变量 `OLARES_SYSTEM_CDN_SERVICE` 映射为应用变量 `APP_CDN_ENDPOINT`：
-1. 在 `OlaresManifest.yaml` 中，在 `envs` 下声明一个应用变量，并将 `valueFrom.envName` 设置为系统变量名。
+1. 在 `BeOSManifest.yaml` 中，在 `envs` 下声明一个应用变量，并将 `valueFrom.envName` 设置为系统变量名。
```yaml
# 将系统变量 OLARES_SYSTEM_CDN_SERVICE 映射为应用变量 APP_CDN_ENDPOINT
- olaresManifest.version: '0.10.0'
- olaresManifest.type: app
+ beosManifest.version: '0.10.0'
+ beosManifest.type: app
envs:
- envName: APP_CDN_ENDPOINT
@@ -37,21 +37,21 @@ description: 通过 `OlaresManifest.yaml` 中的 `envs` 声明并校验应用配
envName: OLARES_SYSTEM_CDN_SERVICE
```
-2. 在 Helm 模板中，通过 `.Values.olaresEnv.` 引用该应用变量。
+2. 在 Helm 模板中，通过 `.Values.beosEnv.` 引用该应用变量。
```yaml
# 在容器环境变量中使用 APP_CDN_ENDPOINT
env:
- name: CDN_ENDPOINT
- value: "{{ .Values.olaresEnv.APP_CDN_ENDPOINT }}"
+ value: "{{ .Values.beosEnv.APP_CDN_ENDPOINT }}"
```
部署时，app-service 会解析引用的变量，并将值注入到 `values.yaml` 中：
```yaml
# 由 app-service 在部署时注入
-olaresEnv:
- APP_CDN_ENDPOINT: "https://cdn.olares.com"
+beosEnv:
+ APP_CDN_ENDPOINT: "https://cdn.beos.local"
```
可用环境变量的完整列表，请参阅[变量参考](#变量参考)。
@@ -62,7 +62,7 @@ olaresEnv:
### envName
-注入到 `values.yaml` 中的变量名。在模板中通过 {{ .Values.olaresEnv.<envName> }} 引用。
+注入到 `values.yaml` 中的变量名。在模板中通过 {{ .Values.beosEnv.<envName> }} 引用。
### default
@@ -128,12 +128,12 @@ envs:
```yaml
envs:
- envName: VERSION
- remoteOptions: https://app.cdn.olares.com/appstore/windows/version_options.json
+ remoteOptions: https://app.cdn.beos.local/appstore/windows/version_options.json
```
### description
-变量用途及有效取值范围的说明。显示在 Olares 界面中。
+变量用途及有效取值范围的说明。显示在 beOS Pro 界面中。
## 变量参考
@@ -143,11 +143,11 @@ envs:
| 变量 | 类型 | 默认值 | 可编辑 | 必填 | 描述 |
| --- | --- | --- | --- | --- | --- |
-| `OLARES_SYSTEM_REMOTE_SERVICE` | `url` | `https://api.olares.com` | 是 | 是 | Olares 远程服务端点，例如应用商店与 Olares Space。 |
-| `OLARES_SYSTEM_CDN_SERVICE` | `url` | `https://cdn.olares.com` | 是 | 是 | 系统资源 CDN 端点。 |
+| `OLARES_SYSTEM_REMOTE_SERVICE` | `url` | `https://api.beos.local` | 是 | 是 | beOS Pro 远程服务端点，例如应用商店与 Remote Space。 |
+| `OLARES_SYSTEM_CDN_SERVICE` | `url` | `https://cdn.beos.local` | 是 | 是 | 系统资源 CDN 端点。 |
| `OLARES_SYSTEM_DOCKERHUB_SERVICE` | `url` | 无 | 是 | 否 | Docker Hub 镜像或加速端点。 |
-| `OLARES_SYSTEM_ROOT_PATH` | `string` | `/olares` | 否 | 是 | Olares 根目录路径。 |
-| `OLARES_SYSTEM_ROOTFS_TYPE` | `string` | `fs` | 否 | 是 | Olares 文件系统类型。 |
+| `OLARES_SYSTEM_ROOT_PATH` | `string` | `/olares` | 否 | 是 | beOS Pro 根目录路径。 |
+| `OLARES_SYSTEM_ROOTFS_TYPE` | `string` | `fs` | 否 | 是 | beOS Pro 文件系统类型。 |
| `OLARES_SYSTEM_CUDA_VERSION` | `string` | 无 | 否 | 否 | 主机 CUDA 版本。 |
### 用户环境变量
diff --git a/docs/zh/developer/develop/app-sys-injected-variables.md b/docs/zh/developer/develop/app-sys-injected-variables.md
index 18e4e1a0d..77b73a9d4 100644
--- a/docs/zh/developer/develop/app-sys-injected-variables.md
+++ b/docs/zh/developer/develop/app-sys-injected-variables.md
@@ -1,11 +1,11 @@
---
outline: [2, 4]
-description: Olares 在应用部署期间注入到 `application values.yaml` 中的运行时变量。
+description: beOS Pro 在应用部署期间注入到 `application values.yaml` 中的运行时变量。
---
# 系统注入的运行时变量
-在部署时，Olares 会自动向应用的 `values.yaml` 注入由系统管理的变量。这些变量为只读，涵盖用户身份、存储路径、集群元数据、应用依赖以及中间件凭据等信息。
+在部署时，beOS Pro 会自动向应用的 `values.yaml` 注入由系统管理的变量。这些变量为只读，涵盖用户身份、存储路径、集群元数据、应用依赖以及中间件凭据等信息。
由于它们属于 Helm values，因此不会自动传递到容器内部。如需在容器内部使用，请在部署模板中通过 `env:` 显式映射。
@@ -31,7 +31,7 @@ spec:
## 变量参考
-“类型”列描述的是 Helm value 的数据类型，并不对应 `OlaresManifest.yaml` 中的 `type` 字段。
+“类型”列描述的是 Helm value 的数据类型，并不对应 `BeOSManifest.yaml` 中的 `type` 字段。
### 用户与身份信息
| 变量 | 类型 | 说明 |
@@ -64,7 +64,7 @@ spec:
| 变量 | 类型 | 说明 |
| -- | -- | -- |
-| `.Values.cluster.arch` | String | 集群 CPU 架构（例如 `amd64`）。Olares 目前不支持混合架构组成集群。 |
+| `.Values.cluster.arch` | String | 集群 CPU 架构（例如 `amd64`）。beOS Pro 目前不支持混合架构组成集群。 |
| `.Values.nodes` | List\ | 节点硬件元数据列表，注入在 `values["nodes"]`下。 |
`.Values.nodes` 中每个条目结构如下：
@@ -101,7 +101,7 @@ spec:
### 应用依赖
-当应用在 `OlaresManifest.yaml` 中声明对其他应用的依赖时，Olares 会将连接信息注入到 `values.yaml`。
+当应用在 `BeOSManifest.yaml` 中声明对其他应用的依赖时，beOS Pro 会将连接信息注入到 `values.yaml`。
| 变量 | 类型 | 说明 |
| -- | -- | -- |
@@ -130,7 +130,7 @@ spec:
### 中间件变量
-仅当在 `OlaresManifest.yaml` 的 `middleware` 部分声明中间件依赖时，才会注入对应变量。
+仅当在 `BeOSManifest.yaml` 的 `middleware` 部分声明中间件依赖时，才会注入对应变量。
PostgreSQL 与 Redis 为预安装组件。MongoDB、MinIO、RabbitMQ、MySQL 和 MariaDB 需要单独安装后方可使用。
diff --git a/docs/zh/developer/develop/distribute-index.md b/docs/zh/developer/develop/distribute-index.md
index e6a8017b8..9f9c05591 100644
--- a/docs/zh/developer/develop/distribute-index.md
+++ b/docs/zh/developer/develop/distribute-index.md
@@ -1,22 +1,22 @@
---
outline: [2, 3]
-description: 了解 Olares 中应用分发的整体机制。
+description: 了解 beOS Pro 中应用分发的整体机制。
---
-# 分发 Olares 应用
+# 分发 beOS Pro 应用
-Olares 的应用分发基于开放标准和自动化校验机制。如果你的应用已经打包为Olares 应用图表（OAC），即可发布到 Olares 应用市场，让用户能够轻松获取和安装。
+beOS Pro 的应用分发基于开放标准和自动化校验机制。如果你的应用已经打包为beOS Pro 应用图表（OAC），即可发布到 beOS Pro 应用市场，让用户能够轻松获取和安装。
-本指南将带你了解 Olares 应用分发的生命周期，理解应用市场的索引机制，如何发布、维护与推广应用。
+本指南将带你了解 beOS Pro 应用分发的生命周期，理解应用市场的索引机制，如何发布、维护与推广应用。
## 开始之前
在分发应用之前，先来了解以下核心概念：
-- **[Olares Application Chart（OAC）](/zh/developer/develop/package/chart.md)**
- 用于描述 Olares 应用的打包格式，包含元数据、所有权、版本信息以及安装配置。
+- **[beOS Pro Application Chart（OAC）](/zh/developer/develop/package/chart.md)**
+ 用于描述 beOS Pro 应用的打包格式，包含元数据、所有权、版本信息以及安装配置。
- **应用索引**
- 向 Olares 应用市场提供应用元数据的服务。Olares 提供默认的公共索引服务，你也可以部署自己的索引服务。
+ 向 beOS Pro 应用市场提供应用元数据的服务。beOS Pro 提供默认的公共索引服务，你也可以部署自己的索引服务。
- **Terminus-Gitbot**
自动验证系统，负责校验提交的应用并执行分发规则。
@@ -46,31 +46,31 @@ Olares 的应用分发基于开放标准和自动化校验机制。如果你的
### 1. 准备应用包
-分发应用之前，必须将其打包为 Olares 应用图表（OAC）。
+分发应用之前，必须将其打包为 beOS Pro 应用图表（OAC）。
在此阶段，开发者通常需要完成以下工作：
-- 在 Olares 主机上开发并测试应用。
+- 在 beOS Pro 主机上开发并测试应用。
- 验证应用的安装和升级行为。
- 完善 Chart 的元数据和目录结构。
-详情请参阅[Olares 应用图表（OAC）](/zh/developer/develop/package/chart.md)。
+详情请参阅[beOS Pro 应用图表（OAC）](/zh/developer/develop/package/chart.md)。
### 2. 提交应用到默认索引
-Olares 应用市场从 Git 仓库索引应用。 要将应用发布到默认的公共索引，开发者需要向官方仓库提交一个拉取请求（Pull Request，PR）。
+beOS Pro 应用市场从 Git 仓库索引应用。 要将应用发布到默认的公共索引，开发者需要向官方仓库提交一个拉取请求（Pull Request，PR）。
提交过程中：
- PR 标题用于声明操作类型。
- Terminus-Gitbot 验证文件范围、所有权和版本规则。
- 通过校验的 PR 会自动合并，无需人工审核。
-详情请参阅[提交 Olares 应用](/zh/developer/develop/submit-apps.md)。
+详情请参阅[提交 beOS Pro 应用](/zh/developer/develop/submit-apps.md)。
### 3. 自动校验与索引
当 PR 提交后，Terminus-Gitbot 会自动执行校验，确保提交内容符合分发规则。
-如果所有检查通过，PR 将自动合并。 稍后，应用应用就会出现在 Olares 应用市场。
+如果所有检查通过，PR 将自动合并。 稍后，应用应用就会出现在 beOS Pro 应用市场。
### 4. 管理应用生命周期
@@ -87,12 +87,12 @@ Olares 应用市场从 Git 仓库索引应用。 要将应用发布到默认的
### 5. 优化应用市场展示
-应用发布后，你可以通过添加图标、宣传图和头图来优化应用其在 Olares 应用市场中的展示效果。
+应用发布后，你可以通过添加图标、宣传图和头图来优化应用其在 beOS Pro 应用市场中的展示效果。
详情请参阅[推广你的应用](/zh/developer/develop/promote-apps.md)。
### 6. (可选) 发布付费应用
-Olares 应用市场同样支持付费应用分发。付费应用需要额外的身份注册、定价配置以及许可证管理。
+beOS Pro 应用市场同样支持付费应用分发。付费应用需要额外的身份注册、定价配置以及许可证管理。
详情请参阅[发布付费应用](/zh/developer/develop/paid-apps.md)。
\ No newline at end of file
diff --git a/docs/zh/developer/develop/index.md b/docs/zh/developer/develop/index.md
index 659b1b343..292005f61 100644
--- a/docs/zh/developer/develop/index.md
+++ b/docs/zh/developer/develop/index.md
@@ -1,8 +1,8 @@
-# 开发 Olares 应用
+# 开发 beOS Pro 应用
-Olares 应用开发依托于通用的 Web 技术与容器化方案。如果你熟悉 Web 应用构建或 Docker 容器技术，即可直接上手开发 Olares 应用，无需额外的技能储备。
+beOS Pro 应用开发依托于通用的 Web 技术与容器化方案。如果你熟悉 Web 应用构建或 Docker 容器技术，即可直接上手开发 beOS Pro 应用，无需额外的技能储备。
-本指南涵盖了 Olares 应用开发的全生命周期，从在 Studio 中编写第一行代码开始，一直到在 Market 上完成发布。
+本指南涵盖了 beOS Pro 应用开发的全生命周期，从在 Studio 中编写第一行代码开始，一直到在 Market 上完成发布。
## 准备工作
正式开始前，建议先了解以下核心概念：
@@ -10,21 +10,21 @@ Olares 应用开发依托于通用的 Web 技术与容器化方案。如果你
- [Network](../concepts/network.md)
## 第一步：使用 Studio 开发
-Olares Studio 是专为加速应用开发周期而设计的开发平台。它提供了预配置的工作区，支持直接在平台上构建、调试和测试应用。
+beOS Pro Studio 是专为加速应用开发周期而设计的开发平台。它提供了预配置的工作区，支持直接在平台上构建、调试和测试应用。
* **[部署应用](./tutorial/deploy.md)**： 学习如何基于现有 Docker 镜像快速部署应用，并在 Studio 中完成配置与测试。
* **[使用开发容器](./tutorial/develop.md)**： 创建远程开发环境 (Dev Container) 并连接至 VS Code，实现流畅的编码体验。
-* **[打包与上传](./tutorial/package-upload.md)**： 将运行中的应用转换为 Olares 兼容的安装包，并上传进行测试。
+* **[打包与上传](./tutorial/package-upload.md)**： 将运行中的应用转换为 beOS Pro 兼容的安装包，并上传进行测试。
* **[添加应用素材](./tutorial/assets.md)**： 配置图标、截图和应用描述，完善应用上架准备工作。
## 第二步：打包应用
-发布应用到 Olares Market 之前，需要按照 Olares Application Chart (OAC) 规范来组织应用结构。该格式在 Helm Charts 的基础上进行了扩展，增加了权限管理和沙箱机制等 Olares 专属特性。
+发布应用到 beOS Pro Market 之前，需要按照 beOS Pro Application Chart (OAC) 规范来组织应用结构。该格式在 Helm Charts 的基础上进行了扩展，增加了权限管理和沙箱机制等 beOS Pro 专属特性。
-* **[了解 Olares Application Chart](./package/chart.md)**： 了解应用包的文件结构与具体规范。
-* **[了解 `OlaresManifest.yaml`](./package/manifest.md)**： 全面介绍 `OlaresManifest.yaml` 文件，该文件用于定义应用的元数据、权限及与 Olares 系统对接的各项配置。
-* **[了解 Helm 扩展](./package/extension.md)**： 了解 Olares 在标准 Helm 部署之上增加的自定义字段与功能。
+* **[了解 beOS Pro Application Chart](./package/chart.md)**： 了解应用包的文件结构与具体规范。
+* **[了解 `BeOSManifest.yaml`](./package/manifest.md)**： 全面介绍 `BeOSManifest.yaml` 文件，该文件用于定义应用的元数据、权限及与 beOS Pro 系统对接的各项配置。
+* **[了解 Helm 扩展](./package/extension.md)**： 了解 beOS Pro 在标准 Helm 部署之上增加的自定义字段与功能。
## 第三步：提交应用
-应用构建并打包完毕后，即可将其分享给 Olares 社区。
+应用构建并打包完毕后，即可将其分享给 beOS Pro 社区。
-* **[提交至 Market](/zh/developer/develop/distribute-index.md)**： 了解如何将应用提交至 Olares Market 以进行审核与分发。
\ No newline at end of file
+* **[提交至 Market](/zh/developer/develop/distribute-index.md)**： 了解如何将应用提交至 beOS Pro Market 以进行审核与分发。
\ No newline at end of file
diff --git a/docs/zh/developer/develop/manage-apps.md b/docs/zh/developer/develop/manage-apps.md
index b39572908..4d14732ef 100644
--- a/docs/zh/developer/develop/manage-apps.md
+++ b/docs/zh/developer/develop/manage-apps.md
@@ -4,12 +4,12 @@ description: 学习如何更新、暂停或移除你的应用。
---
# 管理应用生命周期
-本文介绍应用发布后的管理操作，包括更新应用、暂停分发或从 Olares 应用市场移除应用。
+本文介绍应用发布后的管理操作，包括更新应用、暂停分发或从 beOS Pro 应用市场移除应用。
所有操作均通过提交指向 `beclab/apps:main` 的拉取请求（Pull Request，PR）完成。应用发布后，Terminus-Gitbot 支持以下三种生命周期操作：
- **UPDATE**：保持应用处于最新状态。发布新版本、修复问题或调整配置。
-- **SUSPEND**：暂停应用分发。在不影响现有用户的情况下，停止应用在 Olares Market 中的新发现、下载和安装。
+- **SUSPEND**：暂停应用分发。在不影响现有用户的情况下，停止应用在 beOS Pro Market 中的新发现、下载和安装。
- **REMOVE**：下架应用。永久停止应用分发，并防止该图表文件夹名被再次使用。
:::tip 降低冲突风险
@@ -18,7 +18,7 @@ description: 学习如何更新、暂停或移除你的应用。
## 控制文件
-控制文件是 OAC 根目录下的特殊空文件，用于管理应用在 Olares 应用市场中的分发状态。
+控制文件是 OAC 根目录下的特殊空文件，用于管理应用在 beOS Pro 应用市场中的分发状态。
| 文件名 | 用途 | 版本规则 | 内容 |
|--|--|--|--|
@@ -38,7 +38,7 @@ PR 必须满足以下要求：
- **无冲突**：PR 分支不得与 `beclab/apps:main` 冲突。
:::warning 不支持回滚
-Olares 应用市场不支持版本回滚。如出现问题，必须提交更高版本进行修复。
+beOS Pro 应用市场不支持版本回滚。如出现问题，必须提交更高版本进行修复。
:::
## 暂停应用（SUSPEND）
@@ -50,11 +50,11 @@ PR 必须满足以下要求：
- **控制文件**：OAC 根目录包含 `.suspend`文件，且不包含 `.remove`文件。
- **无冲突**：PR 分支不得与 `beclab/apps:main` 冲突。
-PR 合并后，应用将不再在 Olares 应用市场中展示。已安装该应用的用户仍可继续使用。
+PR 合并后，应用将不再在 beOS Pro 应用市场中展示。已安装该应用的用户仍可继续使用。
## 移除应用（REMOVE）
-若要从 Olares 应用市场永久移除应用，请提交类型为 `REMOVE` 的 PR。
+若要从 beOS Pro 应用市场永久移除应用，请提交类型为 `REMOVE` 的 PR。
要求如下：
diff --git a/docs/zh/developer/develop/mw-integrate-with-es.md b/docs/zh/developer/develop/mw-integrate-with-es.md
index ccf3d98c0..c65ef3149 100644
--- a/docs/zh/developer/develop/mw-integrate-with-es.md
+++ b/docs/zh/developer/develop/mw-integrate-with-es.md
@@ -1,10 +1,10 @@
---
outline: [2, 3]
-description: 了解如何在 Olares 中将你的应用接入 Elasticsearch 服务。
+description: 了解如何在 beOS Pro 中将你的应用接入 Elasticsearch 服务。
---
# 集成 Elasticsearch
-通过在 `OlaresManifest.yaml` 中声明 Elasticsearch 中间件，并将系统注入的配置值映射到容器的环境变量中，即可在应用中使用 Olares 提供的 Elasticsearch 服务。
+通过在 `BeOSManifest.yaml` 中声明 Elasticsearch 中间件，并将系统注入的配置值映射到容器的环境变量中，即可在应用中使用 beOS Pro 提供的 Elasticsearch 服务。
## 安装 Elasticsearch 服务
@@ -15,9 +15,9 @@ description: 了解如何在 Olares 中将你的应用接入 Elasticsearch 服
安装完成后，Elasticsearch 服务及其连接信息将显示在控制面板的中间件列表中。
-## 配置 `OlaresManifest.yaml`
+## 配置 `BeOSManifest.yaml`
-在 `OlaresManifest.yaml` 中添加所需的中间件配置。
+在 `BeOSManifest.yaml` 中添加所需的中间件配置。
- 使用 `username` 字段指定 Elasticsearch 用户名。
- 使用 `indexes` 字段申请一个或多个索引。每个索引名称将作为键注入到 `.Values.elasticsearch.indexes` 中。
@@ -53,7 +53,7 @@ containers:
value: "{{ .Values.elasticsearch.password }}"
# 索引名称
- # 使用在 OlaresManifest 中配置的索引名称（例如 aaa）
+ # 使用在 beOS ProManifest 中配置的索引名称（例如 aaa）
- name: ES_INDEX
value: "{{ .Values.elasticsearch.indexes.aaa }}"
```
diff --git a/docs/zh/developer/develop/mw-integrate-with-mariadb.md b/docs/zh/developer/develop/mw-integrate-with-mariadb.md
index 4165df27b..ce6211210 100644
--- a/docs/zh/developer/develop/mw-integrate-with-mariadb.md
+++ b/docs/zh/developer/develop/mw-integrate-with-mariadb.md
@@ -1,10 +1,10 @@
---
outline: [2, 3]
-description: 了解如何在 Olares 中将你的应用接入 MariaDB 服务。
+description: 了解如何在 beOS Pro 中将你的应用接入 MariaDB 服务。
---
# 集成 MariaDB
-通过在 `OlaresManifest.yaml` 中声明 MariaDB 中间件，并将系统注入的配置值映射到容器的环境变量中，即可在应用中使用 Olares 提供的 MariaDB 服务。
+通过在 `BeOSManifest.yaml` 中声明 MariaDB 中间件，并将系统注入的配置值映射到容器的环境变量中，即可在应用中使用 beOS Pro 提供的 MariaDB 服务。
## 安装 MariaDB 服务
@@ -15,9 +15,9 @@ description: 了解如何在 Olares 中将你的应用接入 MariaDB 服务。
安装完成后，MariaDB 服务及其连接信息将显示在控制面板的中间件列表中。
-## 配置 `OlaresManifest.yaml`
+## 配置 `BeOSManifest.yaml`
-在 `OlaresManifest.yaml` 中添加所需的中间件配置。
+在 `BeOSManifest.yaml` 中添加所需的中间件配置。
- 使用 `username` 字段指定数据库用户名。
- 使用 `databases` 字段申请一个或多个数据库。每个数据库的名称将作为键注入到 `.Values.mariadb.databases` 中。
@@ -54,7 +54,7 @@ containers:
value: "{{ .Values.mariadb.password }}"
# 数据库名称
- # 在 OlaresManifest 中配置的数据库名（例如：aaa）
+ # 在 beOS ProManifest 中配置的数据库名（例如：aaa）
- name: MDB_DB
value: "{{ .Values.mariadb.databases.aaa }}"
```
diff --git a/docs/zh/developer/develop/mw-integrate-with-minio.md b/docs/zh/developer/develop/mw-integrate-with-minio.md
index efa445c83..36ba2efe8 100644
--- a/docs/zh/developer/develop/mw-integrate-with-minio.md
+++ b/docs/zh/developer/develop/mw-integrate-with-minio.md
@@ -1,10 +1,10 @@
---
outline: [2, 3]
-description: 了解如何在 Olares 中将你的应用接入 MinIO 服务。
+description: 了解如何在 beOS Pro 中将你的应用接入 MinIO 服务。
---
# 集成 MinIO
-通过在 `OlaresManifest.yaml` 中声明 MinIO 中间件，并将系统注入的配置值映射到容器的环境变量中，即可在应用中使用 Olares 提供的 MinIO 服务。
+通过在 `BeOSManifest.yaml` 中声明 MinIO 中间件，并将系统注入的配置值映射到容器的环境变量中，即可在应用中使用 beOS Pro 提供的 MinIO 服务。
## 安装 MinIO 服务
@@ -15,9 +15,9 @@ description: 了解如何在 Olares 中将你的应用接入 MinIO 服务。
安装完成后，MinIO 服务及其连接信息将显示在控制面板的中间件列表中。
-## 配置 `OlaresManifest.yaml`
+## 配置 `BeOSManifest.yaml`
-在 `OlaresManifest.yaml` 中添加所需的中间件配置。
+在 `BeOSManifest.yaml` 中添加所需的中间件配置。
- 使用 `username` 字段指定 MinIO 的访问密钥（Access Key）。
- 使用 `buckets` 字段申请一个或多个存储桶。每个存储桶名称将作为键注入到 `.Values.minio.buckets` 中。
@@ -55,7 +55,7 @@ containers:
value: "{{ .Values.minio.password }}"
# 存储桶名称
- # 使用在 OlaresManifest 中配置的存储桶名称（例如 mybucket）
+ # 使用在 beOS ProManifest 中配置的存储桶名称（例如 mybucket）
- name: MINIO_BUCKET
value: "{{ .Values.minio.buckets.mybucket }}"
```
diff --git a/docs/zh/developer/develop/mw-integrate-with-mongodb.md b/docs/zh/developer/develop/mw-integrate-with-mongodb.md
index 44092b63a..0bc785d21 100644
--- a/docs/zh/developer/develop/mw-integrate-with-mongodb.md
+++ b/docs/zh/developer/develop/mw-integrate-with-mongodb.md
@@ -1,10 +1,10 @@
---
outline: [2, 3]
-description: 了解如何在 Olares 中将你的应用接入 MongoDB 服务。
+description: 了解如何在 beOS Pro 中将你的应用接入 MongoDB 服务。
---
# 集成 MongoDB
-通过在 `OlaresManifest.yaml` 中声明 MongoDB 中间件，并将系统注入的配置值映射到容器的环境变量中，即可在应用中使用 Olares 提供的 MongoDB 服务。
+通过在 `BeOSManifest.yaml` 中声明 MongoDB 中间件，并将系统注入的配置值映射到容器的环境变量中，即可在应用中使用 beOS Pro 提供的 MongoDB 服务。
## 安装 MongoDB 服务
@@ -15,9 +15,9 @@ description: 了解如何在 Olares 中将你的应用接入 MongoDB 服务。
安装完成后，MongoDB 服务及其连接信息将显示在控制面板的中间件列表中。
-## 配置 `OlaresManifest.yaml`
+## 配置 `BeOSManifest.yaml`
-在 `OlaresManifest.yaml` 中添加所需的中间件配置。
+在 `BeOSManifest.yaml` 中添加所需的中间件配置。
- 使用 `username` 字段指定 MongoDB 数据库用户。
- 使用 `databases` 字段申请一个或多个数据库。
@@ -58,7 +58,7 @@ containers:
value: "{{ .Values.mongodb.password }}"
# 数据库名称
- # 在 OlaresManifest 中配置的数据库名（例如：app_db）
+ # 在 beOS ProManifest 中配置的数据库名（例如：app_db）
- name: MONGODB_DATABASE
value: "{{ .Values.mongodb.databases.app_db }}"
```
diff --git a/docs/zh/developer/develop/mw-integrate-with-mysql.md b/docs/zh/developer/develop/mw-integrate-with-mysql.md
index 512a53477..7bbe8cb5a 100644
--- a/docs/zh/developer/develop/mw-integrate-with-mysql.md
+++ b/docs/zh/developer/develop/mw-integrate-with-mysql.md
@@ -1,10 +1,10 @@
---
outline: [2, 3]
-description: 了解如何在 Olares 中将你的应用接入 MySQL 服务。
+description: 了解如何在 beOS Pro 中将你的应用接入 MySQL 服务。
---
# 集成 MySQL
-通过在 `OlaresManifest.yaml` 中声明 MySQL 中间件，并将系统注入的配置值映射到容器的环境变量中，即可在应用中使用 Olares 提供的 MySQL 服务。
+通过在 `BeOSManifest.yaml` 中声明 MySQL 中间件，并将系统注入的配置值映射到容器的环境变量中，即可在应用中使用 beOS Pro 提供的 MySQL 服务。
## 安装 MySQL 服务
@@ -15,9 +15,9 @@ description: 了解如何在 Olares 中将你的应用接入 MySQL 服务。
安装完成后，MySQL 服务及其连接信息将显示在控制面板的中间件列表中。
-## 配置 `OlaresManifest.yaml`
+## 配置 `BeOSManifest.yaml`
-在 `OlaresManifest.yaml` 中添加所需的中间件配置。
+在 `BeOSManifest.yaml` 中添加所需的中间件配置。
- 使用 `username` 字段指定 MySQL 数据库用户。
- 使用 `databases` 字段申请一个或多个数据库。每个数据库名称将作为键注入到 `.Values.mysql.databases` 中。
@@ -54,7 +54,7 @@ containers:
value: "{{ .Values.mysql.password }}"
# 数据库名称
- # 在 OlaresManifest 中配置的数据库名（例如：aaa）
+ # 在 beOS ProManifest 中配置的数据库名（例如：aaa）
- name: MDB_DB
value: "{{ .Values.mysql.databases.aaa }}"
```
diff --git a/docs/zh/developer/develop/mw-integrate-with-pg.md b/docs/zh/developer/develop/mw-integrate-with-pg.md
index bb5ca9f3d..ae769805d 100644
--- a/docs/zh/developer/develop/mw-integrate-with-pg.md
+++ b/docs/zh/developer/develop/mw-integrate-with-pg.md
@@ -1,24 +1,24 @@
---
outline: [2, 3]
-description: 了解如何在 Olares 中将应用接入内置的 PostgreSQL 服务。
+description: 了解如何在 beOS Pro 中将应用接入内置的 PostgreSQL 服务。
---
# 集成 PostgreSQL
-通过在 `OlaresManifest.yaml` 中声明依赖，并将系统注入的配置值映射到容器的环境变量中，即可在应用中使用 Olares 提供的 PostgreSQL 服务。
+通过在 `BeOSManifest.yaml` 中声明依赖，并将系统注入的配置值映射到容器的环境变量中，即可在应用中使用 beOS Pro 提供的 PostgreSQL 服务。
:::info PostgreSQL 已安装
-PostgreSQL 服务在 Olares 中默认已安装。
+PostgreSQL 服务在 beOS Pro 中默认已安装。
:::
-## 配置 `OlaresManifest.yaml`
+## 配置 `BeOSManifest.yaml`
-在 `OlaresManifest.yaml` 中添加所需的中间件配置。
+在 `BeOSManifest.yaml` 中添加所需的中间件配置。
- 使用 `scripts` 字段指定数据库创建完成后需要执行的 SQL 脚本。
- 使用 `extensions` 字段为数据库添加所需的扩展。
:::info 脚本中的变量注入
-系统会提供两个变量 `$databasename` 和 `$dbusername`，在执行脚本时由 Olares 应用运行时自动替换。
+系统会提供两个变量 `$databasename` 和 `$dbusername`，在执行脚本时由 beOS Pro 应用运行时自动替换。
:::
**示例**
@@ -47,7 +47,7 @@ middleware:
containers:
- name: my-app
env:
- # 在 OlaresManifest 中配置的数据库名称，
+ # 在 beOS ProManifest 中配置的数据库名称，
# 对应 middleware.postgres.databases[i].name
# 注意：将 替换为 Manifest 中定义的实际名称（例如 immich）
- name: DB_POSTGRESDB_DATABASE
diff --git a/docs/zh/developer/develop/mw-integrate-with-rabbitmq.md b/docs/zh/developer/develop/mw-integrate-with-rabbitmq.md
index ee6583863..413caed39 100644
--- a/docs/zh/developer/develop/mw-integrate-with-rabbitmq.md
+++ b/docs/zh/developer/develop/mw-integrate-with-rabbitmq.md
@@ -1,10 +1,10 @@
---
outline: [2, 3]
-description: 了解如何在 Olares 中将你的应用接入 RabbitMQ 服务。
+description: 了解如何在 beOS Pro 中将你的应用接入 RabbitMQ 服务。
---
# 集成 RabbitMQ
-通过在 `OlaresManifest.yaml` 中声明 RabbitMQ 中间件，并将系统注入的配置值映射到容器的环境变量中，即可在应用中使用 Olares 提供的 RabbitMQ 服务。
+通过在 `BeOSManifest.yaml` 中声明 RabbitMQ 中间件，并将系统注入的配置值映射到容器的环境变量中，即可在应用中使用 beOS Pro 提供的 RabbitMQ 服务。
## 安装 RabbitMQ 服务
@@ -15,9 +15,9 @@ description: 了解如何在 Olares 中将你的应用接入 RabbitMQ 服务。
安装完成后，RabbitMQ 服务及其连接信息将显示在控制面板的中间件列表中。
-## 配置 `OlaresManifest.yaml`
+## 配置 `BeOSManifest.yaml`
-在 `OlaresManifest.yaml` 中添加所需的中间件配置。
+在 `BeOSManifest.yaml` 中添加所需的中间件配置。
- 使用 `username` 字段指定 RabbitMQ 用户。
- 使用 `vhosts` 字段申请一个或多个虚拟主机（vhost）。每个 vhost 名称将作为键注入到 `.Values.rabbitmq.vhosts` 中。
@@ -54,7 +54,7 @@ containers:
value: "{{ .Values.rabbitmq.password }}"
# Vhost
- # 在 OlaresManifest 中配置的 vhost 名称（例如：aaa）
+ # 在 beOS ProManifest 中配置的 vhost 名称（例如：aaa）
- name: RABBITMQ_VHOST
value: "{{ .Values.rabbitmq.vhosts.aaa }}"
```
diff --git a/docs/zh/developer/develop/mw-integrate-with-redis.md b/docs/zh/developer/develop/mw-integrate-with-redis.md
index 7f4c47452..079449feb 100644
--- a/docs/zh/developer/develop/mw-integrate-with-redis.md
+++ b/docs/zh/developer/develop/mw-integrate-with-redis.md
@@ -1,18 +1,18 @@
---
outline: [2, 3]
-description: 了解如何在 Olares 中将应用接入内置的 Redis 服务。
+description: 了解如何在 beOS Pro 中将应用接入内置的 Redis 服务。
---
# 集成 Redis
-通过在 `OlaresManifest.yaml` 中声明依赖，并将系统注入的配置值映射到容器的环境变量中，即可在应用中使用 Olares 提供的 Redis 服务。
+通过在 `BeOSManifest.yaml` 中声明依赖，并将系统注入的配置值映射到容器的环境变量中，即可在应用中使用 beOS Pro 提供的 Redis 服务。
:::info Redis 已安装
-Redis 服务在 Olares 中默认已安装。
+Redis 服务在 beOS Pro 中默认已安装。
:::
-## 配置 `OlaresManifest.yaml`
+## 配置 `BeOSManifest.yaml`
-在 `OlaresManifest.yaml` 中添加所需的中间件配置。
+在 `BeOSManifest.yaml` 中添加所需的中间件配置。
- 使用 `password` 字段指定 Redis 访问密码请求。
- 使用 `namespace` 字段申请 Redis 命名空间。
@@ -49,7 +49,7 @@ containers:
value: "{{ .Values.redis.password }}"
# 命名空间
- # 注意：请将 替换为 OlaresManifest 中定义的实际命名空间（例如 db0）
+ # 注意：请将 替换为 beOS ProManifest 中定义的实际命名空间（例如 db0）
- name: REDIS_NAMESPACE
value: {{ .Values.redis.namespaces. }}
```
diff --git a/docs/zh/developer/develop/mw-overview.md b/docs/zh/developer/develop/mw-overview.md
index 931d312d3..c90936c1a 100644
--- a/docs/zh/developer/develop/mw-overview.md
+++ b/docs/zh/developer/develop/mw-overview.md
@@ -1,14 +1,14 @@
---
outline: [2, 3]
-description: 了解 Olares 中的 middleware，并快速导航到各个已支持服务的数据访问与集成指南。
+description: 了解 beOS Pro 中的 middleware，并快速导航到各个已支持服务的数据访问与集成指南。
---
-# Olares 中的中间件
+# beOS Pro 中的中间件
中间件指位于应用与系统之间的基础设施服务，用于提供数据存储、消息通信等通用能力。
-Olares 的中间件指南分为两类：
+beOS Pro 的中间件指南分为两类：
- **访问与管理数据**：连接到正在运行的服务，用于查看数据和排查问题。
-- **应用集成**：通过 `OlaresManifest.yaml` 配置应用，使其使用某个中间件服务。
+- **应用集成**：通过 `BeOSManifest.yaml` 配置应用，使其使用某个中间件服务。
## 文档类型
@@ -29,11 +29,11 @@ Olares 的中间件指南分为两类：
应用集成类指南说明如何将应用连接到某个中间件服务。
当你的应用需要执行以下操作时，请阅读这类指南：
-- 在 `OlaresManifest.yaml` 中声明依赖
+- 在 `BeOSManifest.yaml` 中声明依赖
- 请求所需的服务资源
- 在应用中读取系统注入的连接信息
-集成过程是声明式的，并由 Olares 在部署阶段自动完成。
+集成过程是声明式的，并由 beOS Pro 在部署阶段自动完成。
## 支持的服务
diff --git a/docs/zh/developer/develop/mw-view-es-data.md b/docs/zh/developer/develop/mw-view-es-data.md
index 416922289..51f9abd39 100644
--- a/docs/zh/developer/develop/mw-view-es-data.md
+++ b/docs/zh/developer/develop/mw-view-es-data.md
@@ -1,10 +1,10 @@
---
outline: [2, 3]
-description: 了解如何在 Olares 中通过 Bytebase 查看并管理 Elasticsearch 数据。
+description: 了解如何在 beOS Pro 中通过 Bytebase 查看并管理 Elasticsearch 数据。
---
# 查看 Elasticsearch 数据
-Elasticsearch 需要先在应用市场安装后才能使用。本文将介绍安装流程，并说明如何在 Olares 中访问并管理 Elasticsearch 数据。
+Elasticsearch 需要先在应用市场安装后才能使用。本文将介绍安装流程，并说明如何在 beOS Pro 中访问并管理 Elasticsearch 数据。
## 安装 Elasticsearch 服务
diff --git a/docs/zh/developer/develop/mw-view-grafana-data.md b/docs/zh/developer/develop/mw-view-grafana-data.md
index f0661359c..f323b83d5 100644
--- a/docs/zh/developer/develop/mw-view-grafana-data.md
+++ b/docs/zh/developer/develop/mw-view-grafana-data.md
@@ -1,10 +1,10 @@
---
outline: [2, 3]
-description: 了解如何在 Olares 中使用 Grafana 仪表板可视化 Prometheus 指标。
+description: 了解如何在 beOS Pro 中使用 Grafana 仪表板可视化 Prometheus 指标。
---
# 使用 Grafana 查看数据
-在 Olares 中，你可以运行 Grafana，并连接到内置的 Prometheus 服务，从而可视化系统指标。本文将介绍如何安装流程，并说明如何连接数据源，以及导入仪表板。
+在 beOS Pro 中，你可以运行 Grafana，并连接到内置的 Prometheus 服务，从而可视化系统指标。本文将介绍如何安装流程，并说明如何连接数据源，以及导入仪表板。
## 安装 Grafana
@@ -30,7 +30,7 @@ description: 了解如何在 Olares 中使用 Grafana 仪表板可视化 Prometh
## 添加 Prometheus 数据源
-Olares 内置了 Prometheus 服务，可以收集系统指标。
+beOS Pro 内置了 Prometheus 服务，可以收集系统指标。
要将 Grafana 连接到该服务，请按以下步骤操作：
@@ -38,9 +38,9 @@ Olares 内置了 Prometheus 服务，可以收集系统指标。
2. 点击**添加数据源**，然后选择 **Prometheus**。
3. 在 **Prometheus server URL** 字段输入：
```text
- http://dashboard..olares.com
+ http://dashboard..beos.local
```
- 将 `` 替换为你的 Olares ID。
+ 将 `` 替换为你的 beOS ID。
4. 点击页面底部的**保存并测试**。如果连接成功，你将看到如下提示。
{width=90% style="margin-left:0"}
diff --git a/docs/zh/developer/develop/mw-view-mariadb-data.md b/docs/zh/developer/develop/mw-view-mariadb-data.md
index e6521b722..4e2d36a4e 100644
--- a/docs/zh/developer/develop/mw-view-mariadb-data.md
+++ b/docs/zh/developer/develop/mw-view-mariadb-data.md
@@ -1,10 +1,10 @@
---
outline: [2, 3]
-description: 了解如何在 Olares 中通过 CLI 或 Bytebase 查看并管理 MariaDB 数据。
+description: 了解如何在 beOS Pro 中通过 CLI 或 Bytebase 查看并管理 MariaDB 数据。
---
# 查看 MariaDB 数据
-MariaDB 需要先在应用市场安装后才能使用。本文将介绍安装流程，并说明如何在 Olares 中访问并管理 MariaDB 数据。
+MariaDB 需要先在应用市场安装后才能使用。本文将介绍安装流程，并说明如何在 beOS Pro 中访问并管理 MariaDB 数据。
## 安装 MariaDB 服务
@@ -30,9 +30,9 @@ MariaDB 需要先在应用市场安装后才能使用。本文将介绍安装流
## 通过 CLI 访问
-你可以使用 Olares 提供的终端直接访问数据库容器。
+你可以使用 beOS Pro 提供的终端直接访问数据库容器。
-1. 在控制面板左侧导航栏底部，打开 **Olares 终端**。
+1. 在控制面板左侧导航栏底部，打开 **beOS Pro 终端**。
2. 获取中间件容器名称：
```bash
diff --git a/docs/zh/developer/develop/mw-view-minio-data.md b/docs/zh/developer/develop/mw-view-minio-data.md
index 89d0aef8b..4eddd8a5d 100644
--- a/docs/zh/developer/develop/mw-view-minio-data.md
+++ b/docs/zh/developer/develop/mw-view-minio-data.md
@@ -1,10 +1,10 @@
---
outline: [2, 3]
-description: 了解如何在 Olares 中安装 MinIO，并通过 MinIO 控制台管理对象存储。
+description: 了解如何在 beOS Pro 中安装 MinIO，并通过 MinIO 控制台管理对象存储。
---
# 查看 MinIO 数据
-本文介绍如何在 Olares 中安装 MinIO，并通过 MinIO 控制台管理对象存储。
+本文介绍如何在 beOS Pro 中安装 MinIO，并通过 MinIO 控制台管理对象存储。
## 安装 MinIO 服务
@@ -19,7 +19,7 @@ description: 了解如何在 Olares 中安装 MinIO，并通过 MinIO 控制台
MinIO 控制台依赖 MinIO 服务，只有在 MinIO 服务就绪后才能安装。
-1. 在 Olares 应用市场中搜索 “MinIO Dashboard”。
+1. 在 beOS Pro 应用市场中搜索 “MinIO Dashboard”。
2. 点击**获取**，然后点击**安装**，并等待安装完成。
## 获取连接信息
diff --git a/docs/zh/developer/develop/mw-view-mongodb-data.md b/docs/zh/developer/develop/mw-view-mongodb-data.md
index 7018fa2d4..ed5cd3094 100644
--- a/docs/zh/developer/develop/mw-view-mongodb-data.md
+++ b/docs/zh/developer/develop/mw-view-mongodb-data.md
@@ -1,10 +1,10 @@
---
outline: [2, 3]
-description: 了解如何在 Olares 中通过 CLI 或 Bytebase 查看并管理 MongoDB 数据。
+description: 了解如何在 beOS Pro 中通过 CLI 或 Bytebase 查看并管理 MongoDB 数据。
---
# 查看 MongoDB 数据
-MongoDB 需要先在应用市场安装后才能使用。本文将介绍安装流程，并说明如何在 Olares 中访问并管理 MongoDB 数据。
+MongoDB 需要先在应用市场安装后才能使用。本文将介绍安装流程，并说明如何在 beOS Pro 中访问并管理 MongoDB 数据。
## 安装 MongoDB 服务
@@ -30,9 +30,9 @@ MongoDB 需要先在应用市场安装后才能使用。本文将介绍安装流
## 通过 CLI 访问
-你可以使用 Olares 提供的终端直接访问数据库容器。
+你可以使用 beOS Pro 提供的终端直接访问数据库容器。
-1. 在控制面板左侧导航栏底部，打开 **Olares 终端**。
+1. 在控制面板左侧导航栏底部，打开 **beOS Pro 终端**。
2. 获取中间件容器名称：
```bash
diff --git a/docs/zh/developer/develop/mw-view-mysql-data.md b/docs/zh/developer/develop/mw-view-mysql-data.md
index d805259c2..6f844f7cb 100644
--- a/docs/zh/developer/develop/mw-view-mysql-data.md
+++ b/docs/zh/developer/develop/mw-view-mysql-data.md
@@ -1,10 +1,10 @@
---
outline: [2, 3]
-description: 了解如何在 Olares 中通过 CLI 或 Bytebase 查看并管理 MySQL 数据。
+description: 了解如何在 beOS Pro 中通过 CLI 或 Bytebase 查看并管理 MySQL 数据。
---
# 查看 MySQL 数据
-MySQL 需要先在应用市场安装后才能使用。本文将介绍安装流程，并说明如何在 Olares 中访问并管理 MySQL 数据。
+MySQL 需要先在应用市场安装后才能使用。本文将介绍安装流程，并说明如何在 beOS Pro 中访问并管理 MySQL 数据。
## 安装 MySQL 服务
@@ -30,9 +30,9 @@ MySQL 需要先在应用市场安装后才能使用。本文将介绍安装流
## 通过 CLI 访问
-你可以使用 Olares 提供的终端直接访问数据库容器。
+你可以使用 beOS Pro 提供的终端直接访问数据库容器。
-1. 在控制面板左侧导航栏底部，打开 **Olares 终端**。
+1. 在控制面板左侧导航栏底部，打开 **beOS Pro 终端**。
2. 进入 MySQL 容器。容器名称是固定的。
```bash
diff --git a/docs/zh/developer/develop/mw-view-nats-data.md b/docs/zh/developer/develop/mw-view-nats-data.md
index 1f6ef107c..42d16a14a 100644
--- a/docs/zh/developer/develop/mw-view-nats-data.md
+++ b/docs/zh/developer/develop/mw-view-nats-data.md
@@ -1,10 +1,10 @@
---
outline: [2, 3]
-description: 了解如何在 Olares 中使用 NATS CLI 订阅和发布消息，并理解 NATS 主题的命名规则与权限模型。
+description: 了解如何在 beOS Pro 中使用 NATS CLI 订阅和发布消息，并理解 NATS 主题的命名规则与权限模型。
---
# 使用 NATS 订阅与发布消息
-本文介绍如何使用 `nats-box` CLI 工具在 Olares 集群内测试 NATS 的消息订阅与发布，并概述 NATS 的主题命名规则与权限模型。
+本文介绍如何使用 `nats-box` CLI 工具在 beOS Pro 集群内测试 NATS 的消息订阅与发布，并概述 NATS 的主题命名规则与权限模型。
## 获取连接信息
@@ -25,7 +25,7 @@ description: 了解如何在 Olares 中使用 NATS CLI 订阅和发布消息，
### 部署 `nats-box`
-1. 下载示例文件 [`nats-box.yaml`](http://cdn.olares.com/common/nats-box.yaml)，并将其上传到 Olares 机器。
+1. 下载示例文件 [`nats-box.yaml`](http://cdn.beos.local/common/nats-box.yaml)，并将其上传到 beOS Pro 机器。
2. 进入 YAML 文件所在目录，部署 `nats-box`：
```bash
kubectl apply -f nats-box.yaml
@@ -57,7 +57,7 @@ nats pub '{"hello":"world"}' --user=` | 来源标识。- **系统服务**：固定为 `os`。
- **第三方应用**：使用对应的 `appId`。
|
| 第二级 | `` | 标识事件或领域。
示例：`users`、`groups`、`files`、`notification`。 |
-| 第三级 |`` | 表示用户空间的 Olares ID。|
+| 第三级 |`` | 表示用户空间的 beOS ID。|
### 权限模型
diff --git a/docs/zh/developer/develop/mw-view-otel-data.md b/docs/zh/developer/develop/mw-view-otel-data.md
index 8974b84ac..5d6505960 100644
--- a/docs/zh/developer/develop/mw-view-otel-data.md
+++ b/docs/zh/developer/develop/mw-view-otel-data.md
@@ -1,16 +1,16 @@
---
outline: [2, 3]
-description: 了解如何在 Olares 集群中启用 OpenTelemetry 自动注入，并在 Jaeger 中查看 Trace 数据。
+description: 了解如何在 beOS Pro 集群中启用 OpenTelemetry 自动注入，并在 Jaeger 中查看 Trace 数据。
---
# 查看 OpenTelemetry 数据
-本文介绍如何在 Olares 集群中为服务启用 OpenTelemetry 自动注入，并通过 Jaeger 查看 Trace 数据。
+本文介绍如何在 beOS Pro 集群中为服务启用 OpenTelemetry 自动注入，并通过 Jaeger 查看 Trace 数据。
## 前提条件
- 目标服务以 Kubernetes 工作负载形式运行，例如 Deployment、StatefulSet 或 DaemonSet。
-- 你可以使用 `kubectl` 访问 Olares 集群。
+- 你可以使用 `kubectl` 访问 beOS Pro 集群。
- 你可以向目标服务发送请求流量。只有存在流量时才会生成 Trace 数据。
## 安装 Jaeger
@@ -24,8 +24,8 @@ Jaeger 用于可视化 Trace 数据，需要通过应用市场安装。
在启用自动注入之前，需要先准备 Trace 后端配置。
-1. 点击 [`otc.yaml`](https://cdn.olares.com/common/otc.yaml) 下载配置文件。
-2. 将该文件上传到你的 Olares 主机。
+1. 点击 [`otc.yaml`](https://cdn.beos.local/common/otc.yaml) 下载配置文件。
+2. 将该文件上传到你的 beOS Pro 主机。
3. 进入文件所在目录并执行：
```bash
kubectl apply -f otc.yaml
@@ -89,7 +89,7 @@ Jaeger 用于可视化 Trace 数据，需要通过应用市场安装。
instrumentation.opentelemetry.io/otel-go-auto-target-exe: "/root/app"
```
-### Olares 应用（Deployment）
+### beOS Pro 应用（Deployment）
1. 编辑 Deployment：
```bash
diff --git a/docs/zh/developer/develop/mw-view-pg-data.md b/docs/zh/developer/develop/mw-view-pg-data.md
index 6ea9b0b19..3eeea197c 100644
--- a/docs/zh/developer/develop/mw-view-pg-data.md
+++ b/docs/zh/developer/develop/mw-view-pg-data.md
@@ -1,10 +1,10 @@
---
outline: [2, 3]
-description: 了解如何在 Olares 中查看并管理 PostgreSQL 数据。
+description: 了解如何在 beOS Pro 中查看并管理 PostgreSQL 数据。
---
# 查看 PostgreSQL 数据
-PostgreSQL 服务在 Olares 中默认可用。本文将介绍如何在 Olares 中访问并管理 PostgreSQL 数据。
+PostgreSQL 服务在 beOS Pro 中默认可用。本文将介绍如何在 beOS Pro 中访问并管理 PostgreSQL 数据。
## 获取连接信息
@@ -21,9 +21,9 @@ PostgreSQL 服务在 Olares 中默认可用。本文将介绍如何在 Olares
## 通过 CLI 访问
-你可以使用 Olares 提供的终端直接访问数据库容器。
+你可以使用 beOS Pro 提供的终端直接访问数据库容器。
-1. 在控制面板左侧导航栏底部，打开 **Olares 终端**。
+1. 在控制面板左侧导航栏底部，打开 **beOS Pro 终端**。
2. 进入 PostgreSQL 容器。容器名称是固定的。
```bash
diff --git a/docs/zh/developer/develop/mw-view-rabbitmq-data.md b/docs/zh/developer/develop/mw-view-rabbitmq-data.md
index 0b8d4ae58..eee65532b 100644
--- a/docs/zh/developer/develop/mw-view-rabbitmq-data.md
+++ b/docs/zh/developer/develop/mw-view-rabbitmq-data.md
@@ -1,10 +1,10 @@
---
outline: [2, 3]
-description: 了解如何在 Olares 中安装 RabbitMQ，并通过 RabbitMQ Dashboard 管理 RabbitMQ 资源。
+description: 了解如何在 beOS Pro 中安装 RabbitMQ，并通过 RabbitMQ Dashboard 管理 RabbitMQ 资源。
---
# 查看 RabbitMQ 数据
-本文介绍如何在 Olares 中安装 RabbitMQ 服务，并通过 RabbitMQ 仪表盘管理数据。
+本文介绍如何在 beOS Pro 中安装 RabbitMQ 服务，并通过 RabbitMQ 仪表盘管理数据。
## 安装 RabbitMQ 服务
diff --git a/docs/zh/developer/develop/mw-view-redis-data.md b/docs/zh/developer/develop/mw-view-redis-data.md
index 561d6c5c5..9dc600111 100644
--- a/docs/zh/developer/develop/mw-view-redis-data.md
+++ b/docs/zh/developer/develop/mw-view-redis-data.md
@@ -1,10 +1,10 @@
---
outline: [2, 3]
-description: 了解如何在 Olares 中查看并管理 Redis 数据。
+description: 了解如何在 beOS Pro 中查看并管理 Redis 数据。
---
# 查看 Redis 数据
-Redis 服务在 Olares 中默认可用。本文将介绍如何在 Olares 中访问并管理 Redis 数据。
+Redis 服务在 beOS Pro 中默认可用。本文将介绍如何在 beOS Pro 中访问并管理 Redis 数据。
## 获取连接信息
@@ -20,9 +20,9 @@ Redis 服务在 Olares 中默认可用。本文将介绍如何在 Olares 中访
## 通过 CLI 访问
-你可以使用 Olares 提供的终端直接访问数据库容器。
+你可以使用 beOS Pro 提供的终端直接访问数据库容器。
-1. 在控制面板左侧导航栏底部，打开 **Olares 终端**。
+1. 在控制面板左侧导航栏底部，打开 **beOS Pro 终端**。
2. 进入 Redis 容器。容器名称是固定的。
```bash
diff --git a/docs/zh/developer/develop/package/chart.md b/docs/zh/developer/develop/package/chart.md
index 0739e3a94..83d53ff56 100644
--- a/docs/zh/developer/develop/package/chart.md
+++ b/docs/zh/developer/develop/package/chart.md
@@ -1,9 +1,9 @@
-# Olares 应用 Chart 包的结构
+# beOS Pro 应用 Chart 包的结构
-Olares 应用 Chart 基于 Helm Chart 的基础结构，扩展 Olares 特有信息，主要为：
+beOS Pro 应用 Chart 基于 Helm Chart 的基础结构，扩展 beOS Pro 特有信息，主要为：
```
|-- Chart.yaml # chart 的 metadata
-|-- OlaresManifest.yaml # Olares 应用的配置
+|-- BeOSManifest.yaml # beOS Pro 应用的配置
|-- templates # chart 安装部署模版文件
| |-- deployment.yaml # 应用部署脚本
|-- values.yaml # chart 安装部署参数
@@ -16,7 +16,7 @@ Olares 应用 Chart 基于 Helm Chart 的基础结构，扩展 Olares 特有信
```
AppName
|-- Chart.yaml # 必选: 包含了 chart 信息的 YAML文件
-|-- OlaresManifest.yaml # 必选: 应用的配置文档
+|-- BeOSManifest.yaml # 必选: 应用的配置文档
|-- values.yaml # 必选: chart 默认的配置值
|-- templates # 必选: 模板目录， 当和 values 结合时，可生成有效的 Kubernetes manifest 文件
| |-- NOTES.txt # 可选: 包含简要使用说明的纯文本文件
@@ -32,7 +32,7 @@ AppName
```
RecommendName
|-- Chart.yaml # 必选: 包含了 chart 信息的 YAML 文件
-|-- OlaresManifest.yaml # 必选: 推荐算法的配置文档
+|-- BeOSManifest.yaml # 必选: 推荐算法的配置文档
|-- values.yaml # 必选: chart 默认的配置值
|-- templates # 必选: 模板目录， 当和 values 结合时，可生成有效的 Kubernetes manifest 文件
| |-- NOTES.txt # 可选: 包含简要使用说明的纯文本文件
diff --git a/docs/zh/developer/develop/package/extension.md b/docs/zh/developer/develop/package/extension.md
index 7d934c87a..0f3bbad4f 100644
--- a/docs/zh/developer/develop/package/extension.md
+++ b/docs/zh/developer/develop/package/extension.md
@@ -1,6 +1,6 @@
-# Olares 对 Helm 进行的字段扩展
+# beOS Pro 对 Helm 进行的字段扩展
-在安装过程中，Olares 使用 [OlaresManifest.yaml](manifest.md) 中的配置将扩展字段注入到应用程序中。
+在安装过程中，beOS Pro 使用 [BeOSManifest.yaml](manifest.md) 中的配置将扩展字段注入到应用程序中。
这些扩展字段信息，可以在模版中直接引用，而无需在 values.yaml 中事先定义 （如果 values.yaml 中有相同的定义，会被系统覆盖）。
diff --git a/docs/zh/developer/develop/package/manifest.md b/docs/zh/developer/develop/package/manifest.md
index fb902c175..e137475bf 100644
--- a/docs/zh/developer/develop/package/manifest.md
+++ b/docs/zh/developer/develop/package/manifest.md
@@ -2,12 +2,12 @@
outline: [2, 3]
---
-# OlaresManifest 规范
+# beOS ProManifest 规范
-每一个 Olares 应用的 Chart 根目录下都必须有一个名为 `OlaresManifest.yaml` 的文件。`OlaresManifest.yaml` 描述了一个 Olares 应用的所有基本信息。Olares 应用市场协议和 Olares 系统依赖这些关键信息来正确分发和安装应用。
+每一个 beOS Pro 应用的 Chart 根目录下都必须有一个名为 `BeOSManifest.yaml` 的文件。`BeOSManifest.yaml` 描述了一个 beOS Pro 应用的所有基本信息。beOS Pro 应用市场协议和 beOS Pro 系统依赖这些关键信息来正确分发和安装应用。
:::info 提示
-最新的 Olares 系统使用的 Manifest 版本为: `0.11.0`
+最新的 beOS Pro 系统使用的 Manifest 版本为: `0.11.0`
- 移除 已不支持的sysData 配置项
- 修改 共享应用的案例
- 增加 apiVersion 字段说明
@@ -46,18 +46,18 @@ outline: [2, 3]
- 将 `spec`>`language` 改为 `spec`>`locale` 并支持 i18n
:::
-一个 `OlaresManifest.yaml` 文件的示例如下：
+一个 `BeOSManifest.yaml` 文件的示例如下：
-::: details `OlaresManifest.yaml` 示例
+::: details `BeOSManifest.yaml` 示例
```yaml
-olaresManifest.version: '0.10.0'
-olaresManifest.type: app
+beosManifest.version: '0.10.0'
+beosManifest.type: app
metadata:
name: helloworld
title: Hello World
description: app helloworld
- icon: https://app.cdn.olares.com/appstore/default/defaulticon.webp
+ icon: https://app.cdn.beos.local/appstore/default/defaulticon.webp
version: 0.0.1
categories:
- Utilities
@@ -66,7 +66,7 @@ entrances:
port: 8080
title: Hello World
host: helloworld
- icon: https://app.cdn.olares.com/appstore/default/defaulticon.webp
+ icon: https://app.cdn.beos.local/appstore/default/defaulticon.webp
authLevel: private
permission:
appCache: true
@@ -108,34 +108,34 @@ options:
```
:::
-## olaresManifest.type
+## beosManifest.type
- 类型：`string`
- 有效值： `app`、`recommend`、`middleware`
-Olares 市场目前支持 3 种类型的应用，各自对应不同场景。本文档以 “app” 为例来解释各个字段。其他类型请参考相应的配置指南。
+beOS Pro 市场目前支持 3 种类型的应用，各自对应不同场景。本文档以 “app” 为例来解释各个字段。其他类型请参考相应的配置指南。
- [推荐算法配置指南](recommend.md)
:::info 提示
-Olares Market 目前不展示 `recommend` 类型的应用，但你可以上传自定义 Chart 来给 Wise 安装推荐算法
+beOS Pro Market 目前不展示 `recommend` 类型的应用，但你可以上传自定义 Chart 来给 Wise 安装推荐算法
:::
-## olaresManifest.version
+## beosManifest.version
- 类型：`string`
-随着 Olares 更新，`OlaresManifest.yaml` 的配置规范可能会发生变化。你可以通过检查 `olaresManifest.version` 来确定这些更改是否会影响你的应用程序。 `olaresManifest.version` 由三个用英文句点分隔的整数组成。
+随着 beOS Pro 更新，`BeOSManifest.yaml` 的配置规范可能会发生变化。你可以通过检查 `beosManifest.version` 来确定这些更改是否会影响你的应用程序。 `beosManifest.version` 由三个用英文句点分隔的整数组成。
-- 第 1 位数字增加意味着引入了不兼容的配置项，未升级对应 `OlaresManifest.yaml` 的应用将无法分发或安装。
-- 第 2 位数字增加意味着分发和安装必须字段存在变化，但 Olares 系统仍兼容之前所有版本配置的应用分发与安装。我们建议开发者尽快更新升级应用的 `OlaresManifest.yaml` 文件。
+- 第 1 位数字增加意味着引入了不兼容的配置项，未升级对应 `BeOSManifest.yaml` 的应用将无法分发或安装。
+- 第 2 位数字增加意味着分发和安装必须字段存在变化，但 beOS Pro 系统仍兼容之前所有版本配置的应用分发与安装。我们建议开发者尽快更新升级应用的 `BeOSManifest.yaml` 文件。
- 第 3 位数字的改变，不影响应用分发和安装。
开发者可以使用 1-3 位的版本号来标识该应用遵循的配置版本。以下是有效版本的一些示例：
```yaml
-olaresManifest.version: 1
-olaresManifest.version: 1.1.0
-olaresManifest.version: '2.2'
-olaresManifest.version: "3.0.122"
+beosManifest.version: 1
+beosManifest.version: 1.1.0
+beosManifest.version: '2.2'
+beosManifest.version: "3.0.122"
```
## apiVersion
@@ -148,7 +148,7 @@ olaresManifest.version: "3.0.122"
## Metadata
-应用的基本信息，用于在 Olares 系统和应用市场中展示应用。
+应用的基本信息，用于在 beOS Pro 系统和应用市场中展示应用。
:::info 示例
```yaml
@@ -156,7 +156,7 @@ metadata:
name: nextcloud
title: Nextcloud
description: The productivity platform that keeps you in control
- icon: https://app.cdn.olares.com/appstore/nextcloud/icon.png
+ icon: https://app.cdn.beos.local/appstore/nextcloud/icon.png
version: 0.0.2
categories:
- Utilities
@@ -169,7 +169,7 @@ metadata:
- 类型：`string`
- 有效值：`^[a-z][a-z0-9]{0,29}$`
-Olares 中的应用的命名空间，仅限小写字母数字字符。最多 30 个字符，需要与 `Chart.yaml` 中的 `FolderName` 和 `name` 字段保持一致。
+beOS Pro 中的应用的命名空间，仅限小写字母数字字符。最多 30 个字符，需要与 `Chart.yaml` 中的 `FolderName` 和 `name` 字段保持一致。
### title
@@ -181,7 +181,7 @@ Olares 中的应用的命名空间，仅限小写字母数字字符。最多 30
- 类型：`string`
-Olares 应用市场中的应用名称下方显示的简短说明。
+beOS Pro 应用市场中的应用名称下方显示的简短说明。
### icon
@@ -216,7 +216,7 @@ OS 1.12 有效值：
- `AI`：AI
:::info 提示
-Olares OS 1.12.0 版本对应用商店的应用分类进行了调整，因此如果应用需要同时兼容 1.11 和 1.12 版本，请同时填写两个版本所需的分类。
+beOS Pro 1.12.0 版本对应用商店的应用分类进行了调整，因此如果应用需要同时兼容 1.11 和 1.12 版本，请同时填写两个版本所需的分类。
:::
## Entrances
@@ -262,14 +262,14 @@ entrances:
- 类型：`string`
-安装后 Olares 桌面的显示名称。长度不超过 `30` 个字符。
+安装后 beOS Pro 桌面的显示名称。长度不超过 `30` 个字符。
### icon
- 类型： `url`
- 可选
-应用安装后 Olares 桌面上的图标。图片文件必须是 `PNG` 或 `WEBP` 格式，不超过 `512 KB`，尺寸为 `256x256 px`。
+应用安装后 beOS Pro 桌面上的图标。图片文件必须是 `PNG` 或 `WEBP` 格式，不超过 `512 KB`，尺寸为 `256x256 px`。
### authLevel
@@ -289,7 +289,7 @@ entrances:
- 默认值：`false`
- 可选
-当 `invisible` 为` true` 时，该入口不会显示在 Olares 桌面上。
+当 `invisible` 为` true` 时，该入口不会显示在 beOS Pro 桌面上。
### openMethod
@@ -346,7 +346,7 @@ sharedEntrances:
host: sharedentrances-ollama
port: 0
title: Ollama API
- icon: https://app.cdn.olares.com/appstore/ollama/icon.png
+ icon: https://app.cdn.beos.local/appstore/ollama/icon.png
invisible: true
authLevel: internal
```
@@ -372,10 +372,10 @@ ports:
- 类型： `int`
- 可选
- 有效值： `0-65535`，保留端口 `22`, `80`, `81`, `443`, `444`, `2379`, `18088` 除外
-Olares 会为你的应用暴露指定的端口，这些端口可通过应用域名在本地网络下访问，如`84864c1f.your_olares_id.olares.com:46879`。对于每个公开的端口，Olares 会自动配置相同端口号的 TCP 和 UDP。
+beOS Pro 会为你的应用暴露指定的端口，这些端口可通过应用域名在本地网络下访问，如`84864c1f.your_olares_id.beos.local:46879`。对于每个公开的端口，beOS Pro 会自动配置相同端口号的 TCP 和 UDP。
:::info 提示
-暴露的端口只能通过本地网络或 Olares 专用网络访问。
+暴露的端口只能通过本地网络或 beOS Pro 专用网络访问。
:::
### protocol
@@ -490,13 +490,13 @@ spec:
versionName: '10.8.11'
# 此 Chart 包含的应用程序的版本。建议将版本号括在引号中。该值对应于 Chart.yaml 文件中的 appVersion 字段。请注意，它与 version 字段无关。
- featuredImage: https://app.cdn.olares.com/appstore/jellyfin/promote_image_1.jpg
+ featuredImage: https://app.cdn.beos.local/appstore/jellyfin/promote_image_1.jpg
# 当应用在应用市场上推荐时，会显示特色图像。
promoteImage:
- - https://app.cdn.olares.com/appstore/jellyfin/promote_image_1.jpg
- - https://app.cdn.olares.com/appstore/jellyfin/promote_image_2.jpg
- - https://app.cdn.olares.com/appstore/jellyfin/promote_image_3.jpg
+ - https://app.cdn.beos.local/appstore/jellyfin/promote_image_1.jpg
+ - https://app.cdn.beos.local/appstore/jellyfin/promote_image_2.jpg
+ - https://app.cdn.beos.local/appstore/jellyfin/promote_image_3.jpg
fullDescription: |
Jellyfin is the volunteer-built media solution that puts you in control of your media. Stream to any device from your own server, with no strings attached. Your media, your server, your way.
upgradeDescription: |
@@ -505,7 +505,7 @@ spec:
website: https://jellyfin.org/
doc: https://jellyfin.org/docs/
sourceCode: https://github.com/jellyfin/jellyfin
- submitter: Olares
+ submitter: beOS Pro
locale:
- en-US
- zh-CN
@@ -537,24 +537,24 @@ spec:
### i18n
-要在 Olares 应用市场中为应用添加多语言支持：
+要在 beOS Pro 应用市场中为应用添加多语言支持：
-1. 在 Olares Application Chart 根目录中创建一个 `i18n` 文件夹。
+1. 在 beOS Pro Application Chart 根目录中创建一个 `i18n` 文件夹。
2. 在 `i18n` 文件夹中，为每个支持的语言环境创建单独的子目录。
-3. 在每个语言环境子目录中，放置 `OlaresManifest.yaml` 文件的本地化版本。
+3. 在每个语言环境子目录中，放置 `BeOSManifest.yaml` 文件的本地化版本。
-Olares 应用市场将根据用户的区域设置自动显示相应的 `OlaresManifest.yaml` 文件的内容。
+beOS Pro 应用市场将根据用户的区域设置自动显示相应的 `BeOSManifest.yaml` 文件的内容。
:::info 示例
```
.
├── Chart.yaml
├── README.md
-├── OlaresManifest.yaml
+├── BeOSManifest.yaml
├── i18n
│ ├── en-US
-│ │ └── OlaresManifest.yaml
+│ │ └── BeOSManifest.yaml
│ └── zh-CN
-│ └── OlaresManifest.yaml
+│ └── BeOSManifest.yaml
├── owners
├── templates
│ └── deployment.yaml
@@ -588,7 +588,7 @@ spec:
:::
:::info 提示
-Olares 目前不支持混合架构的集群。
+beOS Pro 目前不支持混合架构的集群。
:::
### onlyAdmin
@@ -602,7 +602,7 @@ Olares 目前不支持混合架构的集群。
- 类型: `boolean`
- 可选
-当设置为 `true` 时，Olares 会强制以用户 ID “1000”（非 root 用户）运行应用程序。
+当设置为 `true` 时，beOS Pro 会强制以用户 ID “1000”（非 root 用户）运行应用程序。
## Middleware
- 类型：`map`
@@ -632,14 +632,14 @@ middleware:
- ALTER DATABASE $databasename SET search_path TO "$user", public, vectors;
- ALTER SCHEMA vectors OWNER TO $dbusername;
- COMMIT;
- # 操作系统提供了两个变量 $databasename 和 $dbusername，命令执行时会被 Olares 应用运行时替换。
+ # 操作系统提供了两个变量 $databasename 和 $dbusername，命令执行时会被 beOS Pro 应用运行时替换。
```
:::
使用 deployment YAML 中的中间件信息：
```yaml
# 对于 PostgreSQL，对应值如下
- env:
- - name: DB_POSTGRESDB_DATABASE # 你在 OlaresManifest 中配置的数据库名称，在 middleware.postgres.databases[i].name 中指定
+ - name: DB_POSTGRESDB_DATABASE # 你在 beOS ProManifest 中配置的数据库名称，在 middleware.postgres.databases[i].name 中指定
value: {{ .Values.postgres.databases. }}
- name: DB_POSTGRESDB_HOST
value: {{ .Values.postgres.host }}
@@ -687,7 +687,7 @@ host --> {{ .Values.mongodb.host }}
port --> "{{ .Values.mongodb.port }}" # yaml 文件中的端口和密码需要用双引号括起来。
username --> {{ .Values.mongodb.username }}
password --> "{{ .Values.mongodb.password }}" # yaml 文件中的端口和密码需要用双引号括起来。
-databases --> "{{ .Values.mongodb.databases }}" # 数据库的值类型是 map。你可以使用 {{ .Values.mongodb.databases. }} 获取数据库。 是你在 OlaresManifest 中配置的名称，在 middleware.mongodb.databases[i].name 中指定
+databases --> "{{ .Values.mongodb.databases }}" # 数据库的值类型是 map。你可以使用 {{ .Values.mongodb.databases. }} 获取数据库。 是你在 beOS ProManifest 中配置的名称，在 middleware.mongodb.databases[i].name 中指定
```
### MinIO
:::info 示例
@@ -800,7 +800,7 @@ middleware:
## Options
-此部分用于配置与Olares系统相关的选项。
+此部分用于配置与beOS Pro系统相关的选项。
### policies
- 类型：`list
