Carbide docs

Bun frontend, Go API backend, Postgres database.

The default Carbide UI uses React, Bun, and Tailwind in a container while the framework keeps auth, sessions, and data access in Go.

Runtime Model

browser -> frontend container -> /api proxy -> backend Go container -> Postgres

The frontend is the public entrypoint. It proxies /api and /health to the backend so browser requests stay same-origin.

Generated Frontend

view/
`-- web/
    |-- Dockerfile
    |-- bun.lock
    |-- index.html
    |-- package.json
    `-- src/
        |-- main.jsx
        |-- server.jsx
        `-- styles.css

The web app lives inside view/web. React owns page flow, forms, and dashboard rendering. The Go backend owns JSON responses, HttpOnly cookies, sessions, validation, and Postgres access.

Styling

The starter uses Tailwind as the required styling path. The frontend container installs with Bun and builds generated CSS from the checked-in Tailwind input.

Regression Requirements