Choose a development workspace
Select Development workspace in the app settings step when creating an environment. Your checkout and supporting services run together.
Dev workspaces
A development environment with your whole stack
Edit a persistent Git checkout alongside your running application services. Connect over SSH or use Wodby Agent from the dashboard.
- Persistent code and private home directory
- SSH access for your editor and coding tools
- Preview changes before sending them through CI/CD
See common workflows
Make a change in your running application
Install the Drupal Redis module with Composer and enable it with Drush. Check whether the PHP Redis extension and a Redis-compatible service are available. Leave the changes uncommitted for review.
Open Chats in a Drupal workspace and ask Wodby Agent to install a module. It can check the running services, edit the checkout, and run Composer and Drush.
Inspect the files in your shared checkout
Review the uncommitted changes in this workspace. Explain what each file changes and which checks I should run before committing. Do not modify, commit, or push anything.
Open Status and select a changed file to view its diff. You can review edits made by an agent or through your SSH editor in the same place.
Work on the code your app runs
A workspace starts from a Git repository and runs your application from a shared working checkout. Supporting services, such as databases and caches, run alongside it. Edit the code and preview the result through the app’s endpoints. Reload behavior depends on the service: some pick up edits directly, while others need a restart.
Keep the tools you know
Use the connection details in the dashboard to connect over SSH with your registered key. Open an SSH-capable editor, use the terminal, or run a coding agent with your own account. You can also open Wodby Agent chats in the browser and use your organization’s AI credits. SSH and workspace coding access belong to the workspace owner.
Keep development connected to delivery
Commit and push changes for review, then release them to a standard staging or production environment through CI/CD. A workspace does not build and deploy a new image for every source change. Pull upstream changes when you choose; the dashboard pull action refuses to overwrite tracked edits or diverging commits.
Pause and return to your work
The code checkout and private home directory survive normal restarts and pauses. Pause the environment when you do not need it, and resume to continue working. Persistent storage remains allocated and billable. The workspace runner also counts as an app service while running.
Create a workspace for a compatible stack
Choose workspace mode when creating a new environment with a supported stack and Git source. Wodby checks service and cluster compatibility before creation. Existing standard environments cannot be converted in place. Workspaces are for development: code services run with one replica, without autoscaling, and scheduled jobs stay disabled.