dropbits Documentation

Get the kernel

How to obtain the Dropbits runtime for self-hosting. Dist = playground/ (hub) + sibling dropbits/ (kernel, packs, bin/site) — not the marketing website/ shell on dropbits.org.

Codeberg

----
Product repocodeberg.org/dropbits/dropbits
Default branchv9
Clone URLhttps://codeberg.org/dropbits/dropbits.git
git clone -b v9 https://codeberg.org/dropbits/dropbits.git
cd dropbits
php playground/bin/serve
# open http://127.0.0.1:8090/  — create a site, edit at /<id>/
php playground/bin/deploy <id>

Kernel CLI lives under dropbits/:

cd dropbits
./bin/site migrate
./bin/site seed-minimal
./bin/site boot

The Codeberg v9 tip is the clone-and-run tree. Older v8 / v4 history may remain on other branches or tags (e.g. archive/v4-2026-07).

Normative Spec / architecture companions stay in the product monorepo — see Repo docs layout and Contributing in a full clone.

Release zip

Build a self-host zip from the monorepo (same contents as the Codeberg tip):

# from product monorepo root
bash website/scripts/make-release-zip.sh
# → dist/dropbits-v9-<date>.zip

Maintainers: push product updates to Codeberg org branch v9 (see remotes in the contributor clone). Optional runtime-only orphan export remains npm run publish:codeberg / scripts/publish-codeberg-v8.sh — do not aim that force-with-lease at v9.

Attach a release zip to a Codeberg Release when cut. Until then, prefer git clone as above.

After you have the clone

  1. Install locally — hub php playground/bin/serve, or migrate/seed the minimal demo
  2. Install on server — DocumentRoot …/public + DROPBITS_SITE
  3. Content-owned deploy — ship code, migrate; never overwrite live content by default

What this is not

  • Not a hosted playground CTA — run the demo on your machine or server (operators may run a separate playground host)
  • Not AdminHub / config evaluator — v9 Admin is on the live page
  • Not “download the whole marketing site” — public docs are published HTML; contributors reading SPEC use the monorepo

See also