Choosing where to start

There are four ways in. Each one says what it gives you on the first day and what it commits you to afterwards.

The whole path

npm create barako-app@latest

A Next.js project, a compose file that runs the API and the console, seeded content and working sign-in.

Commits you to: barakoCMS on .NET 10 and PostgreSQL, barakoBrew for editing, and a Next.js site. You can replace the site or the deploy step later without touching content.

The API only

docker compose up -d

barakoCMS behind a frontend you build yourself. Content modelling, roles, workflows and delivery are there; a user interface is not.

Commits you to: running PostgreSQL, and writing every screen your editors use, or adding barakoBrew later. Swagger is the only built-in surface. Start with the barakoCMS quickstart.

The site engine only

npm i barakopress

For when barakoCMS already runs and the public site needs rendering.

Commits you to: blog-shaped content. barakoPress is new, has no theme system yet, and reads barakoCMS only.

Deploys only

brew install arnelirobles/tap/baryovm

Agentless deploys and host hardening for any VM you own. Nothing to do with content.

Commits you to: VMs you can reach over SSH. There is no control plane and no agent, by design.

Not sure

Start with the path. It describes what each stage hands to the next, which is usually what decides it.