Devcontainer Lifecycle
Six ordered hook phases that take a development container from host-side preparation to an attached, ready workspace.
.devcontainer/lifecycle/
8Trait
Order is explicit and visible, usually through numeric prefixes or a declared sequence.
Six ordered hook phases that take a development container from host-side preparation to an attached, ready workspace.
.devcontainer/lifecycle/
8Content-hashed CSS and JS are cached for a year as immutable; everything else is revalidated on every request and kept fresh by invalidation.
public/
2Plans live on disk as a tree of milestone folders and issue files that a planner reserves and syncs into Gitea, moving from slug-only drafts to ID-prefixed synced names.
<root>/
1Make modules register their targets and requirements into shared lists, and aggregate targets are composed from whatever registered.
scripts/build/
5Early in-container hooks that create container-local state — user-home caches, CLI configuration, directories — before repository-driven setup runs.
.devcontainer/lifecycle/on-create.d/
4Every change moves through the same Build → Test → Publish pipeline locally, on the pull request, and on merge, ending in a deployment only where there is one.
docs/RELEASING.md
2One small runner turns each lifecycle event into a directory of .sh hooks, run in lexical order and stopped by the first failure.
.devcontainer/lifecycle/
1Repository documentation is staged from docs/ into .cache/docs-site/ and mounted into a Hugo site, so the docs stay where they are owned.
.cache/docs-site/
2make deploy is the whole deployment model: build the site, initialise and apply its Terraform root, upload public/, and invalidate the CDN.
scripts/deploy.sh
5Workflow YAML decides when automation runs and in what order, and hands the work itself to stable repository commands and reusable actions.
.gitea/workflows/
4No specification matches every filter.