Self-hosted, Self-Improving, Federated Everything App — dev management, agent orchestration, persistent mind, digital twin, second brain, and creative pipeline from a single dashboard over Tailscale to port the user into the OS
JavaScript ai-agentsdashboarddeveloper-toolsdigital-twinquantified-selfsecond-brainself-hostedtailscale
#!/bin/bash
set -e
# Anchor to the script's own directory so relative paths (e.g. the
# `node -e import('./server/lib/tailscale.js')` detection below) work
# regardless of where the user invokes ./setup.sh from.
cd "$(dirname "$0")"
echo "==================================="
echo " PortOS Setup"
echo "==================================="
echo ""
# Check for Node.js
if ! command -v node &> /dev/null; then
echo "Node.js is required but not installed."
echo "Install it from: https://nodejs.org/"
exit 1
fi
# Keep the pre-install check on the same owner as npm run setup/start/dev.
# Running the Node script here handles excluded release lines (23/25) as well
# as patch floors, without a second semver implementation in shell.
if ! node scripts/checkNodeVersion.js; then
exit 1
fi
# `npm run setup` is the all-in-one: submodules + root/client/server/autofixer
# deps + the trusted native rebuilds (scripts/trusted-rebuilds.js) + data dir, db, and browser
# setup. install:all is kept as a backward-compat alias.
echo "Installing dependencies and running setup..."
if ! PORTOS_DEFER_SETUP_GUIDE=1 npm run setup; then
echo ""
echo "==================================="
echo " Setup incomplete"
echo "==================================="
echo ""
echo "Fix the issue above, then re-run: ./setup.sh"
echo ""
exit 1
fi
echo ""
# macOS Tailscale.app CLI is sandboxed (`tailscale cert` can't write outside its
# container → EPERM). Detection delegates to server/lib/tailscale.js so the
# candidate path list stays a single source of truth.
# --input-type=module is required: `node -e` defaults to CommonJS even when
# the package.json declares "type":"module", so a top-level import() in the
# command would be a syntax error and the detection would silently always
# fail (suppressed by `2>/dev/null`). Without this flag the whole
# auto-install branch never runs on macOS.
if node --input-type=module -e "import('./server/lib/tailscale.js').then(m => process.exit(m.hasOnlySandboxedTailscale() ? 0 : 1)).catch(() => process.exit(1))" 2>/dev/null; then
echo "Detected Tailscale.app without the unsandboxed CLI."
echo "Installing tailscale via Homebrew so 'tailscale cert' can write to data/certs/..."
brewInstalled=0
if command -v brew &> /dev/null; then
if brew install tailscale; then
brewInstalled=1
else
echo "⚠️ brew install tailscale failed — HTTPS via Tailscale won't work until you install it manually."
fi
else
echo "⚠️ Homebrew not found. Install brew (https://brew.sh) then run: brew install tailscale"
echo " Without it, the 'Enable HTTPS' button on the Instances page will fail with EPERM."
fi
# Re-run cert setup now that the unsandboxed CLI is available. `npm run
# setup` already made a safe attempt with only the sandboxed CLI, but it
# deliberately stayed on HTTP rather than silently creating a self-signed
# fallback. This second attempt can now write the trusted cert files.
if [ "$brewInstalled" = "1" ]; then
echo "Re-running cert provisioning with the freshly-installed Tailscale CLI..."
npm run setup:cert || echo "⚠️ setup:cert failed — re-run manually if needed."
fi
echo ""
fi
# ffmpeg is a runtime dependency for the media/video features (camera-device
# enumeration at GET /api/media/devices, video generation, thumbnailing, audio
# mux) — server/lib/ffmpeg.js shells out to the `ffmpeg` binary. It's not an npm
# package, so without this the features fail at runtime with `spawn ffmpeg
# ENOENT`. Install it via the platform package manager when it's missing.
# Fail-soft: PortOS still boots without it; only the media/video paths degrade.
ensure_ffmpeg() {
if command -v ffmpeg &> /dev/null; then
return 0
fi
echo "ffmpeg not found — required for camera devices, video generation, and thumbnails."
case "$(uname -s)" in
Darwin)
if command -v brew &> /dev/null; then
echo "Installing ffmpeg via Homebrew..."
brew install ffmpeg || echo "⚠️ brew install ffmpeg failed — install manually: brew install ffmpeg"
else
echo "⚠️ Homebrew not found. Install brew (https://brew.sh) then run: brew install ffmpeg"
fi
;;
Linux)
# Prefix installs with sudo only when not already root — a root
# container (e.g. the Docker image) has no sudo binary, so prefixing
# unconditionally would fail to install despite apt-get being present.
maybe_sudo=""
[ "$(id -u)" -ne 0 ] && maybe_sudo="sudo"
if [ -n "$maybe_sudo" ] && ! command -v sudo &> /dev/null; then
echo "⚠️ Not root and sudo unavailable — install ffmpeg manually (e.g. apt-get install ffmpeg)."
elif command -v apt-get &> /dev/null; then
echo "Installing ffmpeg via apt-get${maybe_sudo:+ (may prompt for sudo)}..."
$maybe_sudo apt-get update && $maybe_sudo apt-get install -y ffmpeg || echo "⚠️ apt-get install ffmpeg failed — install manually: ${maybe_sudo:+sudo }apt-get install ffmpeg"
elif command -v dnf &> /dev/null; then
echo "Installing ffmpeg via dnf${maybe_sudo:+ (may prompt for sudo)}..."
$maybe_sudo dnf install -y ffmpeg || echo "⚠️ dnf install ffmpeg failed — install manually: ${maybe_sudo:+sudo }dnf install ffmpeg"
elif command -v pacman &> /dev/null; then
echo "Installing ffmpeg via pacman${maybe_sudo:+ (may prompt for sudo)}..."
$maybe_sudo pacman -S --noconfirm ffmpeg || echo "⚠️ pacman -S ffmpeg failed — install manually: ${maybe_sudo:+sudo }pacman -S ffmpeg"
else
echo "⚠️ No known package manager (apt-get/dnf/pacman). Install ffmpeg manually so media/video features work."
fi
;;
*)
echo "⚠️ Unrecognized platform — install ffmpeg manually so media/video features work."
;;
esac
echo ""
}
ensure_ffmpeg
# Install/update slash-do (project-level slash commands for Claude Code et al.)
# via npx. Auto-detects the installed AI environments and lays down the latest
# command set under ~/.claude/commands (or per-environment equivalent). The
# git submodule at lib/slashdo is the in-repo source for inline command loading
# from CoS agents — `npx slash-do@<pinned>` complements that by keeping the
# user-global command pool current. Failures are non-fatal: PortOS still works
# without the global slash commands.
SLASHDO_VERSION="$(tr -d '[:space:]' < scripts/SLASHDO_VERSION)"
echo "Installing/updating slash-do commands (npx slash-do@${SLASHDO_VERSION})..."
# Pipe "a" so slash-do's "multiple environments detected" prompt auto-selects
# all detected envs instead of hanging on readline when stdin is not a TTY.
if ! echo a | npx --yes "slash-do@${SLASHDO_VERSION}"; then
echo "⚠️ slash-do install failed — skipping (you can re-run later: npx slash-do@${SLASHDO_VERSION})"
fi
echo ""
# Optional Ghostty setup. Skip on non-TTY (CI, piped stdin) so `read` doesn't
# abort the script under `set -e`, and `||` the read itself so a Ctrl-D in an
# interactive shell defaults to "skip" instead of aborting.
if [ -t 0 ]; then
setup_ghostty=""
read -p "Set up Ghostty terminal themes? (y/N): " setup_ghostty || true
if [[ $setup_ghostty =~ ^[Yy]$ ]]; then
node scripts/setup-ghostty.js
fi
fi
echo ""
# Optional: start PortOS now. Accept y/yes/Y/YES (and Enter) to start, n/no
# to skip, and reprompt on anything else so a stray "asdf" doesn't silently
# launch pm2. On non-TTY (CI, piped stdin) default to "no" so the script
# completes unattended without auto-launching pm2. A Ctrl-D inside the loop
# is treated as "no" so the script can still finish cleanly.
start_now=0
if [ -t 0 ]; then
while true; do
answer=""
if ! read -p "Start PortOS now via pm2? (Y/n): " answer; then
start_now=0
break
fi
case "$answer" in
""|[Yy]|[Yy][Ee][Ss])
start_now=1
break
;;
[Nn]|[Nn][Oo])
start_now=0
break
;;
*)
echo "Please answer yes or no (y/n)."
;;
esac
done
fi
# Print the URL the user should open. Delegates to scripts/print-access-url.js
# so we share the same cert detection (file presence AND PEM parseability) the
# server uses — otherwise we'd advertise HTTPS URLs the server isn't serving.
print_access_url() {
node scripts/print-access-url.js
}
if [ "$start_now" = "1" ]; then
echo ""
echo "Starting PortOS..."
npm start
# Open the dashboard in the PortOS-managed browser. Fail-soft.
node scripts/open-ui-in-browser.js || true
echo ""
echo "==================================="
echo " PortOS is running"
echo "==================================="
echo ""
print_access_url
echo ""
node scripts/setup-guide.js --assume-active
echo "Logs: npm run pm2:logs"
echo "Stop: npm run pm2:stop"
echo ""
else
echo "==================================="
echo " Setup Complete!"
echo "==================================="
echo ""
echo "Start PortOS:"
echo " Development: npm run dev"
echo " Production: npm start"
echo " Stop: npm run pm2:stop"
echo " Logs: npm run pm2:logs"
echo ""
print_access_url
echo ""
node scripts/setup-guide.js
echo ""
fi