Documentation Index
Fetch the complete documentation index at: https://www.qovery.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Manage Remote Development Environments (RDE). RDE allows platform teams to provision isolated, pre-configured development environments for developers. The system works as follows:- Blueprints — Template projects/environments that serve as the source for cloning.
- RDE instances — Cloned from a blueprint, with optional RBAC isolation and member invitation.
- Project-level:
BLUEPRINT_PROJECT_ID = <project ID>marks a project as a blueprint. - Environment-level:
BLUEPRINT_KEY = <blueprint project ID>links environments to their blueprint.
Commands
info
Show RDE platform overview. Usage:-o, --organization(string) — Organization Name
create
Provision a new Remote Development Environment by cloning a blueprint environment into a new project. This command:- Creates a new project for the RDE
- Creates an RBAC role with scoped permissions (unless
--skip-rbac) - Clones the blueprint environment into the new project
- Updates the TTL job to target the new environment (if present)
- Invites the developer via email (unless
--skip-invite) - Triggers deployment (unless
--skip-deploy)
-b, --blueprint(string) — Blueprint Project Name to clone from-c, --cluster(string) — Cluster Name where to create the RDE-e, --email(string) — Email address to invite the developer-n, --name(string) — Name for the new RDE (will create projectrde-<name>)-o, --organization(string) — Organization Name--skip-deploy— Skip deployment after cloning--skip-invite— Skip member invitation--skip-rbac— Skip RBAC role creation
list
List all Remote Development Environments, optionally filtered by blueprint. Shows name, blueprint, status, uptime, and workspace URL for each RDE. Usage:-b, --blueprint(string) — Filter by Blueprint Project Name--json— JSON output-o, --organization(string) — Organization Name
status
Show detailed status of an RDE. Usage:-n, --name(string) — RDE Name-o, --organization(string) — Organization Name
start
Start (deploy) an RDE. Usage:-n, --name(string) — RDE Name-o, --organization(string) — Organization Name-w, --watch— Watch deployment status until it’s ready or an error occurs
start-all
Start (deploy) all RDE environments. Usage:-b, --blueprint(string) — Filter by Blueprint Project Name-o, --organization(string) — Organization Name
stop
Stop an RDE. Usage:-n, --name(string) — RDE Name-o, --organization(string) — Organization Name-w, --watch— Watch stop status until it completes or an error occurs
stop-all
Stop all RDE environments. Usage:-b, --blueprint(string) — Filter by Blueprint Project Name-o, --organization(string) — Organization Name
logs
Fetch recent logs from an RDE workspace. Usage:-n, --name(string) — RDE Name-o, --organization(string) — Organization Name
urls
List workspace URLs for running RDEs. Usage:-b, --blueprint(string) — Filter by Blueprint Project Name-o, --organization(string) — Organization Name
upgrade
Upgrade one or all RDE environments using one of two strategies:- image (default) — Redeploy the environment (re-pulls latest images).
- reclone — Delete the environment, re-clone from blueprint, and deploy. Warning: uncommitted changes will be lost with
reclone.
--name is provided, upgrades a single RDE. Otherwise, upgrades all RDEs.
Usage:
-b, --blueprint(string) — Filter by Blueprint Project Name (when upgrading all)-n, --name(string) — RDE Name (omit to upgrade all)-o, --organization(string) — Organization Name-s, --strategy(string) — Upgrade strategy:image(redeploy) orreclone(full re-clone). Default:image
delete
Fully remove an RDE by:- Stopping the environment (if running)
- Deleting the environment
- Deleting the project
- Deleting the RBAC role
RDE-<name>(if exists) - Deleting the API token
ttl-<name>(if exists)
-n, --name(string) — RDE Name-o, --organization(string) — Organization Name-w, --watch— Watch deletion status
delete-all
Delete all RDE environments permanently. Requires the--confirm flag.
This will delete the environment, project, RBAC role, and API token for each RDE.
Usage:
-b, --blueprint(string) — Filter by Blueprint Project Name--confirm— Confirm deletion of all RDE environments-o, --organization(string) — Organization Name
Blueprint Commands
Manage RDE blueprint projects and environments. A blueprint is a project with a template environment that serves as the source for cloning new Remote Development Environments.blueprint register
Register an existing project as an RDE blueprint by setting theBLUEPRINT_PROJECT_ID project-level variable and BLUEPRINT_KEY on the first DEVELOPMENT environment.
The project must already exist and contain at least one environment.
Usage:
-o, --organization(string) — Organization Name-p, --project(string) — Project Name to register as a blueprint
blueprint unregister
Remove theBLUEPRINT_PROJECT_ID and BLUEPRINT_KEY environment variables from the project and its environment. This does not delete the project itself.
Usage:
-o, --organization(string) — Organization Name-p, --project(string) — Blueprint Project Name to unregister
blueprint list
List all RDE blueprints. Usage:--json— JSON output-o, --organization(string) — Organization Name
blueprint status
Show detailed status of a blueprint. Usage:-o, --organization(string) — Organization Name-p, --project(string) — Blueprint Project Name
blueprint deploy
Deploy a blueprint environment. Usage:-o, --organization(string) — Organization Name-p, --project(string) — Blueprint Project Name-w, --watch— Watch deployment status until it’s ready or an error occurs
blueprint stop
Stop a blueprint environment. Usage:-o, --organization(string) — Organization Name-p, --project(string) — Blueprint Project Name-w, --watch— Watch stop status until it completes or an error occurs
Examples
Set Up and Provision an RDE
Manage RDE Lifecycle
Upgrade and Clean Up
Related Commands
qovery environment- Manage environmentsqovery project- Manage projectsqovery cluster- Manage clustersqovery log- View service logsqovery shell- Access container shell