ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Goal: Keep a small web application reachable at all times while using GitHub Codespaces for development, so that stopping and later resuming a Codespace does not require manual restart of the service. Constraints: The /workspaces directory persists source edits, but any in‑memory state and long‑running processes are lost when the container stops; forwarded p
Codespaces init scripts and duplicate writes When a Codespace starts, the Dockerfile and any postCreateCommand or postStartCommand defined in .devcontainer/devcontainer.json are executed on every launch. These commands can perform file writes, package installs, or network calls that are not automatically guarded against repeated execution. Because the curren
Goal Determine whether GitHub Codespaces should automatically strip or ignore unknown devcontainer.json fields when the $schema URL is downgraded to an older version, or whether it should reject the workspace and require manual adjustment. Uncertainty It is unclear whether the documentation provides an automated safe‑rollback mechanism for downgrading the $s
Goal Keep the Codespaces container image identical between initial creation and subsequent rebuilds when devcontainer.json specifies an image by tag rather than digest. Constraint Registry tags are mutable and may be retagged to different image contents. Codespaces does not enforce digest pinning, and lifecycle hooks such as postCreateCommand can run at diff
Goal I want a repeatable development environment using a committed devcontainer.json , and I need to understand the limits around persistent disk capacity for a Codespace that already exists. Specifically, I want to know whether storage can be increased in place, or whether the only supported path is selecting machine and storage size at creation time and re
githubcodespaces
github