Carbide docs

Bun frontend. Go API backend. Postgres database.

Carbide starts with three mandatory containers, checked-in infrastructure, and regression tests that protect the framework before it grows.

Install And Start

curl -fsSL https://raw.githubusercontent.com/ryangerardwilson/carbide/main/install.sh | bash
carbide new demo
cd demo
carbide run dev
carbide status

The installer builds the Go CLI. carbide help prints the command reference. carbide upgrade updates the installed CLI when a newer GitHub commit is available. Ctrl+C detaches from live dev logs; carbide follow logs attaches again; carbide status prints the container table; carbide stop dev stops the stack.

Product Contract

  • Apps run through a Bun/React/Tailwind frontend container, Go backend container, and Postgres container.
  • Postgres is mandatory, not one adapter among many.
  • The Bun frontend is the public entrypoint and proxies /api to the backend.
  • Infrastructure belongs in version-controlled code.
  • The default starter opens account creation first, then supports login, logout, and dashboard.
  • The first IaC target is generated Docker Compose for local development.
  • The CLI is implemented in Go and renders colored, aligned, script-safe output with full-width ILoveCandy-style per-container startup/shutdown animation, status tables, timestamped logs, live log follow, and queryable structured dev logs.

First Milestone

  1. Boot with one command.
  2. Serve the React app through Bun.
  3. Proxy /api to the Go backend.
  4. Create the first user with a Postgres-backed session.
  5. Open the dashboard.

Current Automation

The repo now has a CI gate for contract checks and a GitHub Pages workflow that publishes this documentation site from docs/site after pushes to main.