· Engineering · 2 min read
How this website ships
sourceplane.ai began as an Orunbase baseline, deploys with orun on every merge, and gets its domain from a Terraform component. No one runs a deploy by hand.
This website is a small, honest example of the way we think software should ship.
It started as a baseline
The repository was built from astrowind, one of the public baselines in the Orunbase registry: a complete Astro and Tailwind CSS site, with its CI, its tooling and its operating docs, rebuilt under our name and live on its own stage and production environments within minutes.
It is declared, not scripted
The repository declares what it is. An intent.yaml names the environments, and each unit of code carries a component.yaml beside it: the site itself, and the Terraform that serves it on this domain. On every merge, orun plans only the components that changed and runs each one in the CI we already had. The site builds, deploys to stage and production on Cloudflare Workers, and is smoke-tested over HTTP.
Even the domain is a component
sourceplane.ai is attached to the site by a small Terraform component. It names the hostnames per environment, waits for the site’s Worker to exist, and keeps its state on the Orun platform. The credentials it uses are minted for each run from the workspace’s Cloudflare connection; nothing provider-shaped is stored in the repository.
Changing this page is a pull request. Shipping it is a merge.