Astropress

Start with the local path that Astropress validates most heavily.

Start Astropress with the local SQLite-backed flow, understand what is supported today, and use the CLI without guessing at the product boundary.

Quick start

astropress new my-site
cd my-site
bun install
astropress doctor
astropress dev

Default release posture

Treat the local SQLite-backed admin and the static public example as the reference implementation. Move to hosted adapters when you need them, but do not assume every hosted path has the same maturity today.

Two setup choices

Astropress now separates App Host from Content Services. App Host means where the Astro app runs. Content Services means where Astropress stores content, media, auth, sessions, and the service API that powers admin actions.

CLI examples

astropress new my-site --app-host vercel --content-services supabase
astropress new brochure --app-host github-pages --content-services none
astropress new team-site --app-host cloudflare-pages --content-services cloudflare

What editors get

Package-owned admin routes cover pages, posts, media, redirects, comments, users, translations, settings, and revisions. The intended workflow is editor-first, not Git-first.

Git sync remains useful for export, backup, review, and static deploy workflows, but the content database is the canonical source of truth.