Project workspace
Understand the project canvas, environments, services, databases, settings, and daily deployment workflow.
The project workspace is the operating view for one application. It keeps the application topology, environments, services, databases, deployments, configuration, networking, usage, and access policy together.
Open a project
- Open Projects from the Autodisc dashboard.
- Select a project.
- Choose the environment from the project breadcrumb.
Every project starts with a production environment. Additional persistent or preview environments are isolated from production.
Read the canvas
Each node is a deployable service or managed database in the selected environment. A connection between nodes means that one service depends on a resource or another service.
Select a node to open its service panel:
| Tab | Use it for |
|---|---|
| Deployments | Deployment history, build state, health, and redeploy |
| Logs | Live or retained application output |
| Metrics | CPU and memory behavior |
| Files | Supported persistent or mutable service files |
| Networking | Generated domains, custom domains, TCP, and private networking |
| Details | Source, commands, sizing, lifecycle, and deletion |
The dock at the bottom of the canvas contains project-wide actions:
- Deploy All rebuilds or restarts eligible services in the selected environment.
- Stop All stops the environment's services without deleting their configuration.
- Add Service adds source, an image, a template, or a managed database.
- Project Settings opens environment-aware variables, usage, webhooks, members, and project controls.
A normal production workflow
- Connect the repository.
- Set up the repository contract: build, start, port, health, variables, dependencies, and migrations.
- Optionally ask Autodisc to propose those changes.
- Review the exact source and resource proposal.
- Add user-supplied secrets under Project Settings → Variables.
- Build and deploy into a non-production environment.
- Inspect deployments, logs, metrics, networking, and real application behavior.
- Promote an immutable release or deploy the approved revision to production.
Scope and safety
Project and environment selection matter. A setting changed in staging does not silently alter production. Managed-resource creation, cost-bearing changes, and generated source changes require explicit approval.
Stopping a service preserves its definition. Deleting a service, database, environment, or project is different and may remove provider resources and data. Autodisc shows a destructive-action confirmation when deletion is supported.