Planck v0.2.2

Bug fixes

Fresh installs via curl | sh were completely broken

Two separate bugs, both hit for real installing v0.2.1:

• docker compose run --rm setup requested a pseudo-TTY by default. When the
  install script itself runs via curl | sh (or irm | iex on Windows),
  stdin is the pipe feeding the script, not a real terminal, so TTY
  allocation failed outright ("the input device is not a TTY") and the whole
  install aborted before any service ever started. setup's entrypoint is a
  plain, non-interactive script — it never needed a TTY in the first place.
• dolt and beads are built locally rather than published as per-version
  images, and their build contexts only resolved correctly inside a full
  monorepo checkout — a standalone install has no planck_docker/ directory
  above compose.yml at all, so docker compose up failed immediately
  trying to build dolt from a path that doesn't exist.

Both are fixed structurally, not worked around: setup no longer requests a
TTY it doesn't need, and dolt/beads now build from a context relative to
compose.yml itself, with the install script downloading those two
directories from the tagged release alongside compose.yml.

Upgrading

You can run the following for upgrading planck:

Linux/MacOS

curl -fsSL https://thebroken.link/planck/install_docker.sh | sh

Or manually run the following:

cd ~/planck
if docker compose version >/dev/null 2>&1; then
  alias dc="docker compose"
else
  alias dc="docker-compose"
fi
dc -f compose.yml --env-file .env pull
dc -f compose.yml --env-file .env run --rm setup
dc -f compose.yml --env-file .env up -d

Windows

irm https://thebroken.link/planck/install_docker.ps1 | iex

Or manually run the following:

cd $HOME\planck
$Compose = if (docker compose version 2>$null) { @("docker","compose") } else { @("docker-compose") }
& $Compose -f compose.yml --env-file .env pull
& $Compose -f compose.yml --env-file .env run --rm setup
& $Compose -f compose.yml --env-file .env up -d

If your v0.2.1 install never actually came up (stuck at "Running first-run
setup..." with localhost:4000 unreachable), this release fixes exactly
that — a fresh curl | sh run should now complete end to end.