Conductor Docs (#320)

Author: kraftp

docs/explanations/system-tables.md

@@ -102,11 +102,11 @@ Each entry represents a different event.
 ## Provenance Tables
 
 :::info
-The provenance database is only available for DBOS Cloud applications using the **experimental** time travel feature. To enable experimental time travel for your application, please specify `--enable-timetravel` [during deploy](../cloud-tutorials/cloud-cli#dbos-cloud-app-deploy).
+The provenance database is only available for DBOS Cloud applications using the **experimental** time travel feature. To enable experimental time travel for your application, please specify `--enable-timetravel` [during deploy](../production/dbos-cloud/cloud-cli#dbos-cloud-app-deploy).
 :::
 
 DBOS Cloud optionally maintains a provenance database for your application, which is an append-only versioned replica of your application database.
-It is the key enabler of [Interactive Time Travel](../cloud-tutorials/interactive-timetravel.md).
+It is the key enabler of [Interactive Time Travel](../production/dbos-cloud/interactive-timetravel.md).
 The provenance database name is your application database suffixed with `_dbos_prov`.
 For example, if your application database is named `hello`, then your provenance database is named `hello_dbos_prov`.
 The provenance database contains the history (within the time travel [data retention period](https://www.dbos.dev/pricing)) of each of your database tables.

docs/index.md

@@ -4,9 +4,8 @@ sidebar_position: 1
 
 # Welcome to DBOS!
 
-DBOS is a serverless platform for building reliable backend applications.
-Add lightweight annotations to your app to _durably execute_ it, making it resilient to any failure.
-Then, deploy your app to the cloud with a single command.
+DBOS is a library for building incredibly reliable programs.
+Add a few annotations to your application to **durably execute** it and make it **resilient to any failure**.
 
 ### Get Started
 

docs/integrations/adding-dbos-to-next.md

@@ -10,7 +10,7 @@ This guide shows you how to add the open source [DBOS Transact](https://github.c
 - Lightweight durable execution – DBOS [workflows](../typescript/tutorials/workflow-tutorial) run to completion exactly once.
 - Reliable background tasks - Use DBOS [queues](../typescript/tutorials/queue-tutorial.md) to run any task in the background and guarantee it eventually completes, no matter how long it takes.
 - Cron-style task scheduling – Automate recurring jobs with [cron-like scheduling](../typescript/tutorials/scheduled-workflows).
-- Built-in tracing and replay debugging – [Find workflows in the dashboard](../cloud-tutorials/monitoring-dashboard) and [re-run them locally](../typescript/tutorials/debugging.md).
+- Built-in tracing and replay debugging – [Find workflows in the dashboard](../production/dbos-cloud/monitoring-dashboard) and [re-run them locally](../typescript/tutorials/debugging.md).
 
 ## Architectural Overview
 Next.js is a framework that optimizes where and when [React](https://react.dev/) UI components render—whether on the client, server, or edge—while also handling routing, data fetching, and performance optimizations.  Part of this architecture involves the creation of minimized code bundles for handling requests.  These bundles can be loaded quickly in a “serverless” environment, leading to minimal request latency even when the server is “cold”.  This “serverless” style of deployment precludes any long-running jobs, background tasks that execute while no client requests are pending, or long-lived server objects such as WebSockets:
@@ -280,5 +280,3 @@ For Next.js server actions to work, it may be necessary to configure allowed ori
 - If your DBOS code is accessing the application database, check out the [transactions tutorial](../typescript/tutorials/transaction-tutorial) and consider database setup using [schema migration](../typescript/programming-guide#5-database-operations-and-transactions).
 - Review the [programming guide](../typescript/programming-guide) for information on job scheduling, queues, and other DBOS features.
 - Check out DBOS [programming examples](../examples)
-- Launch your Next.js app to [DBOS Cloud](../cloud-tutorials/application-management).
-

docs/integrations/nestjs.md

@@ -114,64 +114,3 @@ export class AppModule {}
 ```
 
 If you need multiple instances of your DBOS class, you must give them distinct names (`dbosService` in this case). You can create a dedicated provider for each or use a single provider for multiple classes, at your convenience.
-
-## Running in DBOS Cloud
-DBOS Cloud seamlessly autoscales your application to millions of users and provides built-in dashboards for observability and monitoring.
-
-#### 1. Install the DBOS Cloud CLI
-<section className="row list">
-
-<article className="col col--6">
-Run this command to install it.
-</article>
-
-<article className="col col--6">
-```shell
-npm i -g @dbos-inc/dbos-cloud@latest
-```
-</article>
-</section>
-
-#### 2. Define a Start Command
-<section className="row list">
-<article className="col col--6">
-First, install the Nest.js CLI alongside your project's dependencies:
-</article>
-
-<article className="col col--6">
-```shell
-npm install @nestjs/cli
-```
-</article>
-
-<article className="col col--6">
-Then, set the `start` command in the `runtimeConfig` section of your [`dbos-config.yaml`](../typescript/reference/configuration.md) to `npx nest start`
-
-To test that it works, try launching your application locally with `npx dbos start`.
-</article>
-
-<article className="col col--6">
-
-```yaml
-runtimeConfig:
-  start:
-    - "npx nest start"
-```
-
-</article>
-</section>
-
-#### 3. Deploy to DBOS Cloud
-<section className="row list">
-<article className="col col--6">
-Run this single command to deploy your application to DBOS Cloud!
-</article>
-
-<article className="col col--6">
-
-```shell
-dbos-cloud app deploy
-```
-
-</article>
-</section>

docs/production/dbos-cloud/_category_.json

@@ -0,0 +1,5 @@
+{
+    "label": "DBOS Cloud",
+    "position": 30
+}
+  

docs/cloud-tutorials/account-management.md renamed to docs/production/dbos-cloud/account-management.md

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 2
+sidebar_position: 30
 title:  Account Management
 description: Learn how to manage DBOS Cloud users
 toc_max_heading_level: 3

docs/cloud-tutorials/application-management.md renamed to docs/production/dbos-cloud/application-management.md

@@ -1,7 +1,6 @@
 ---
-sidebar_position: 1
+sidebar_position: 20
 title: Application Management
-description: Learn how to manage DBOS Cloud applications
 pagination_prev: null
 ---
 
@@ -20,7 +19,7 @@ Each time you deploy an application, the following steps execute:
 3. **Migration**: If you specify database migrations in your `dbos-config.yaml`, these are run on your cloud database.
 4. **Deployment**: Your application is deployed to a number of [Firecracker microVMs](https://firecracker-microvm.github.io/).
 By default, these have 1 vCPU and 512MB of RAM.
-The amount of memory allocated to each microVM is [configurable](../cloud-tutorials/cloud-cli.md#dbos-cloud-app-update).
+The amount of memory allocated to each microVM is [configurable](./cloud-cli.md#dbos-cloud-app-update).
 
 After an application is deployed, it is assigned a domain of the form `https://<username>-<app-name>.cloud.dbos.dev/`.
 If your account is part of an [organization](./account-management.md#organization-management), organization name is used instead of username.
@@ -103,9 +102,9 @@ Here are some useful tools to monitor and debug applications:
 
 - The [cloud console](https://console.dbos.dev) provides a web UI for viewing your applications and their traces and logs.
 
-- To retrieve the last `N` seconds of your application's logs, run [`dbos-cloud app logs -l <N>`](../cloud-tutorials/cloud-cli.md#dbos-cloud-app-logs). Note that new log entries take a few seconds to appear.
+- To retrieve the last `N` seconds of your application's logs, run [`dbos-cloud app logs -l <N>`](./cloud-cli.md#dbos-cloud-app-logs). Note that new log entries take a few seconds to appear.
 
-- To retrieve the status of a particular application, run [`dbos-cloud app status <app-name>`](../cloud-tutorials/cloud-cli.md#dbos-cloud-app-status). To list all applications, run [`dbos-cloud app list`](../cloud-tutorials/cloud-cli.md#dbos-cloud-app-list).
+- To retrieve the status of a particular application, run [`dbos-cloud app status <app-name>`](./cloud-cli.md#dbos-cloud-app-status). To list all applications, run [`dbos-cloud app list`](./cloud-cli.md#dbos-cloud-app-list).
 
 ### Managing Application Versions
 
@@ -116,7 +115,7 @@ You can view all previous versions of your application from the [cloud console](
 dbos-cloud app versions <app-name>
 ```
 
-You can redeploy a previous version of your application by passing `--previous-version <version-id>` to the [`app deploy`](../cloud-tutorials/cloud-cli.md#dbos-cloud-app-deploy) command.
+You can redeploy a previous version of your application by passing `--previous-version <version-id>` to the [`app deploy`](./cloud-cli.md#dbos-cloud-app-deploy) command.
 
 ```shell
 dbos-cloud app deploy --previous-version <version-id>
@@ -132,7 +131,7 @@ To update your application metadata, run:
 dbos-cloud app update <app-name>
 ```
 
-See the [DBOS Cloud CLI reference](../cloud-tutorials/cloud-cli.md#dbos-cloud-app-update) for a list of properties you can update. Note that updating an application metadata does not trigger a redeploy of the code, which you can do with the [`app deploy`](../cloud-tutorials/cloud-cli.md#dbos-cloud-app-deploy) command.
+See the [DBOS Cloud CLI reference](./cloud-cli.md#dbos-cloud-app-update) for a list of properties you can update. Note that updating an application metadata does not trigger a redeploy of the code, which you can do with the [`app deploy`](./cloud-cli.md#dbos-cloud-app-deploy) command.
 
 ### Deleting Applications
 

docs/cloud-tutorials/assets/cc-logs.png renamed to docs/production/dbos-cloud/assets/cc-logs.png

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 4
+sidebar_position: 50
 title: Bringing Your Own Database
 ---
 

docs/cloud-tutorials/assets/cc-orgs.png renamed to docs/production/dbos-cloud/assets/cc-orgs.png

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 11
+sidebar_position: 90
 title: CI/CD Best Practices
 ---
 

docs/cloud-tutorials/assets/cc-traces.png renamed to docs/production/dbos-cloud/assets/cc-traces.png

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 30
+sidebar_position: 1000
 title: Cloud CLI Reference
 description: DBOS Cloud CLI reference
 pagination_next: null
@@ -23,7 +23,7 @@ It provides a URL to a secure login portal you can use to create an account from
 
 **Arguments:**
 - `-u, --username <string>`: Your DBOS Cloud username. Must be between 3 and 30 characters and contain only lowercase letters, numbers, and underscores (`_`).
-- `-s, --secret [string]`: (Optional) An [organization secret](../cloud-tutorials/account-management.md#organization-management) given to you by an organization admin. If supplied, adds your newly registered account to the organization.
+- `-s, --secret [string]`: (Optional) An [organization secret](./account-management.md#organization-management) given to you by an organization admin. If supplied, adds your newly registered account to the organization.
 
 
 :::info
@@ -163,7 +163,7 @@ After restoration is complete, we recommend using [`change-database-instance`](#
 
 **Description:**
 This command links your own Postgres database instance to DBOS Cloud.
-Before running this command, please first follow our [tutorial](../cloud-tutorials/byod-management) to set up your Postgres database.
+Before running this command, please first follow our [tutorial](./byod-management) to set up your Postgres database.
 
 :::info
 This feature is currently only available to [DBOS Pro or Enterprise](https://www.dbos.dev/pricing) subscribers.

docs/cloud-tutorials/assets/dash-debug-wf.png renamed to docs/production/dbos-cloud/assets/dash-debug-wf.png

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 3
+sidebar_position: 40
 title: Database Management
 description: Learn how to manage DBOS Cloud database instances
 ---
@@ -28,7 +28,7 @@ Each application is deployed to an isolated database by default; you can configu
 :::
 
 :::info
-If you forget your database password, you can always [reset it](../cloud-tutorials/cloud-cli.md#dbos-cloud-db-reset-password).
+If you forget your database password, you can always [reset it](./cloud-cli.md#dbos-cloud-db-reset-password).
 :::
 
 To see a list of all provisioned instances and their statuses, run:
@@ -72,15 +72,15 @@ Database recovery is not available for [linked databases](./byod-management.md)
 :::
 
 DBOS Cloud can use [PostgreSQL point-in-time-recovery](https://www.postgresql.org/docs/current/continuous-archiving.html) to restore your database to a previous state, for example to recover from data corruption or loss.
-First, run the [`database restore`](../cloud-tutorials/cloud-cli.md#dbos-cloud-db-restore) to create a new database instance containing the state of your database instance at a previous point in time:
+First, run the [`database restore`](./cloud-cli.md#dbos-cloud-db-restore) to create a new database instance containing the state of your database instance at a previous point in time:
 
 ```shell
 dbos-cloud db restore <database-name> -t <timestamp> -n <new-db-instance-name>
 ```
 
 The timestamp must be in [RFC3339](https://datatracker.ietf.org/doc/html/rfc3339) format and must be within the backup retention period of your database (24 hours for free-tier users).
 
-After the database is restored, you can redeploy your applications to it with [`app change-database-instance`](../cloud-tutorials/cloud-cli.md#dbos-cloud-app-change-database-instance).
+After the database is restored, you can redeploy your applications to it with [`app change-database-instance`](./cloud-cli.md#dbos-cloud-app-change-database-instance).
 For each application connected to the original database instance, run:
 
 ```shell