install the server part and the front part separately

install the server part and the front part separately

With the daemon on a machine of its own, the two hosts do not need the
same tree. -m says which one is being installed:

  full    what it has always installed, on one machine
  server  the machine that runs brisk-spush
  front   the machine that runs nginx and php-fpm

The php goes on both, and so do the .js. The frontend serves admin.php,
usermgmt.php and the rest through php-fpm, and those include the same
Obj/ tree - usermgmt.php and mailmgr.php reach spush/brisk-spush.phh for
USOCK_PATH_PFX - so only brisk-spush.php itself, the daemon entry point,
is dropped on the front. The .js are needed daemon side too, because
index.php decides whether to emit the custom.js tag by looking for the
file on disk.

What the daemon never serves is what only a browser asks for, and that is
where the trees part: no stylesheets, no sounds, no brisk-img, nothing
from docroot/. Measured on this installation, "server" installs 85 files
against the 335 of "full", the 223 images being most of the difference.

The frontend has no daemon, so none of the private directories - ftok,
legal, proxy - means anything there: "front" implies -W, which already
meant exactly that. Each mode says at the end what it installed and what
has to be installed on the other machine.

-U now also documents its tcp form, and an unknown mode is refused rather
than silently treated as full.

Checked by installing all three modes into a scratch tree: full 335 files,
server 85 with 443 ftok entries and no image, front 334 with no ftok
entry, no legal directory and no brisk-spush.php.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>