Get the kernel
How to obtain the Dropbits runtime for self-hosting. Dist = the dropbits/ tree (kernel, packs, bin/site) — not the marketing website/ shell on dropbits.org.
Codeberg
| -- | -- |
| Product repo | codeberg.org/fkamos/dropbits |
| Default branch | v8 (runtime tree) |
| Clone URL | https://codeberg.org/fkamos/dropbits.git |
git clone https://codeberg.org/fkamos/dropbits.git
cd dropbits
# or explicitly: git clone -b v8 …
The Codeberg tip is the runtime tree (what lives under dropbits/ in the development monorepo): kernel, packs, bin/site, public guides under docs/, plus LICENSE/README. Older v4 history remains on branch v4 (archived tip tag 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-v8-<date>.zip
Attach that artifact to a Codeberg Release on tag v8.x (or similar) and link it from this page when published. Until a release is attached on Codeberg, prefer git clone as above.
After you have dropbits/
- Install locally — migrate, seed, serve the minimal demo
- Install on server — lean DocumentRoot +
DROPBITS_SITE - 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 — v8 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
- Site directory layout
- Upgrade a deployed site
- Kernel notes: dropbits/README.md