Reference

Docker & Git

How Goldenhost builds your repository, and the project settings that matter.

How a deploy works

Goldenhost clones the branch you choose, builds the Dockerfile, starts the container, and waits for it to answer. Only then is it marked running and attached to its address.

The container contract

• One HTTP port, bound to 0.0.0.0.
• A health check that returns a successful response after startup.
• Configuration from environment variables, not baked-in secrets.
• Exit on fatal startup errors so the failure is visible.
• No writing critical data to the container filesystem.

Monorepos

Point the Dockerfile path at the package you want to build, for example apps/web/Dockerfile. The build context is the repository root, so copy only what the image needs.

Build arguments and secrets

Build-time defaults belong in the Dockerfile as ARG values. Runtime secrets belong in the project's Environment tab. Secrets are never written to build logs.

Deployments and rollback

Every deploy keeps its commit, image tag, log, and status. To roll back, redeploy an earlier commit from the deployment list. Goldenhost does not rewrite deployment history.

A failed deploy does not replace the running version. Fix the commit, push, and deploy again.

Logs

Build logs show each build step and the first failure. Runtime logs show the most recent output from the running container. They are for debugging, not long-term retention.