dropbits Documentation

Packs (CLI + Admin)

Packs are optional feature bundles under dropbits/packs/. Brochure boots load no pack PHP until a capability is enabled. Install writes a DB row; enable runs the activation recipe.

CLI (operators)

From dropbits/:

./bin/site pack-install <name>     # available (DB row); PHP not loaded yet
./bin/site enable <capability>     # activate recipe + load pack PHP
./bin/site disable <capability>    # deactivate

Examples shipped with the kernel: contact, newsletter, migration, playground, mail (password reset), and others as packs land on disk.

Deploy ships pack files. Activation stays explicit — migrate never auto-enables new packs. After a code deploy, check Admin → Site for “available” chips, or enable on the install via CLI.

Admin (site owners)

Same tools, different UI:

  1. Admin → Site → Packs & capabilities
  2. Install & enable for a pack on disk but not installed
  3. Enable / disable for an installed capability

Quiet chips in the edit session can point at the same available list.

Owner-oriented copy: Packs & capabilities.

Not in v8

  • No AdminHub package grid
  • No catalog-packages browse hub
  • No config evaluator “compose helpers” install path

See also