Document development workspaces - #124
Merged
Merged
Conversation
Explain workspace creation, owner SSH access, MCP lifecycle controls, preparation, and delivery into Standard environments. Link the guide from app environments, SSH keys, and MCP documentation.
csandanov
marked this pull request as ready for review
September 24, 2026 13:21
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Customers need a guide to creating a development workspace, connecting their tools, and delivering reviewed changes to a Standard environment. This adds that workflow with prerequisites, owner-only SSH access, MCP controls, preparation and restart behavior, costs, and recovery limits.
Adds navigation and related guidance in App environments, SSH keys, and MCP documentation.
Validation: the Wodby 2 documentation builds with MkDocs strict mode; rendered local links and anchors pass for all five changed pages; whitespace checks pass.
Keep this PR in draft until development workspace runtime acceptance is complete and the documented dashboard and MCP features are available. Merging to master publishes the documentation automatically.