Deployment and maintenance helpers for the workspace-host version of Spiderweb.

These scripts are Linux-specific. On macOS, use spiderweb-config config install-service to install the per-user launchd service instead.

cd scripts
sudo ./install-systemd.sh

This installs Spiderweb as a systemd-managed workspace host. It does not install or configure AI providers. External workers such as Spider Monkey should be deployed separately.

Useful overrides:

sudo PORT=18880 BIND_ADDR=127.0.0.1 SPIDER_WEB_ROOT=/srv/spiderweb ./install-systemd.sh
sudo OVERWRITE_CONFIG=1 ./install-systemd.sh

sudo systemctl start spiderweb
sudo systemctl stop spiderweb
sudo systemctl restart spiderweb
sudo systemctl status spiderweb
sudo journalctl -u spiderweb -f

After the service is running:

export SPIDERWEB_CONFIG=/etc/spiderweb/config.json
spiderweb-config auth status --reveal
spiderweb-control --url ws://127.0.0.1:18790/ --auth-token <admin-token> workspace_create '{"name":"Demo","vision":"Mounted workspace","template_id":"dev"}'
spiderweb-fs-mount --workspace-url ws://127.0.0.1:18790/ --auth-token <admin-or-user-token> --workspace-id <workspace-id> mount ./workspace

Then start an external worker, for example Spider Monkey, against the mounted directory.

sudo ./scripts/update.sh

sudo ./scripts/uninstall.sh

./scripts/full-reset.sh

Preflight:

./scripts/acheron-smoke.sh

Namespace-mode mount smoke:

./scripts/acheron-namespace-smoke.sh

Restart chaos test:

./scripts/acheron-chaos-restart.sh

Multi-node harness:

./scripts/acheron-multi-node-runtime.sh

Linux release archive:

./scripts/package-spiderweb-linux-release.sh --out-dir ./dist

This produces:

• dist/spiderweb-linux-<arch>.tar.gz
• dist/spiderweb-linux-<arch>.tar.gz.sha256

By default this packager pins the published SpiderVenoms release declared in scripts/spidervenoms-release.sh. Before packaging, Spiderweb now verifies that the published SpiderVenoms .sha256 asset still matches the pinned digest, then verifies the downloaded archive bytes locally before staging them.

Pinned published SpiderVenoms assets are currently supported for:

• linux/x86_64
• linux/arm64
• macos/arm64

For local development against a checkout instead, set:

SPIDERVENOMS_SOURCE_MODE=source

You can validate the cross-repo pin directly with:

./scripts/check-spidervenoms-release-pin.sh

Versioning policy:

• patch releases are the default path
• bigger version jumps must be explicit
• see docs/release-policy.md

The old Mother/provider bootstrap and embedded-runtime canary scripts were removed as part of the Spider Monkey split. Spiderweb no longer owns provider credentials, provider-backed chat, or Mother/system onboarding.