Skip to content
d_devboxby 508.dev/ DocumentationDashboard ↗
Browse documentation
DOCUMENTATION / Prepare your host

Prepare your Linux host

Use a Linux machine you own, with an unprivileged development account and a persistent home directory. Configure and verify SSH access first. Use a VPN or relay for private machines; this setup never opens a public management port.

Choose the setup path

PathUse it whenHosted account needed?
Direct SSHYou want repo transfer, editor/agent launch and explicit-port tunnelsNo
Enrolled daemonYou also want hosted observations, tool inventory and relay coordinationYes, plus an operator-signed release

Check prerequisites

Run this on the host as the intended development user:

TERMINAL
curl -fsSL https://devbox.508.dev/host.sh | sh

The default is a read-only check. It reports missing tools, Python archive-safety support, user systemd availability and persistent user services.

Prepare Debian or Ubuntu

Review the script first if you prefer. This command uses sudo only to install prerequisites and enable lingering for the current account:

TERMINAL
curl -fsSL https://devbox.508.dev/host.sh | sh -s -- --prepare

Or download and inspect it before preparing the host:

TERMINAL
curl -fsSL https://devbox.508.dev/host.sh -o prepare-host.sh
less prepare-host.sh
sh prepare-host.sh --prepare

It installs Git, tmux, Python 3, OpenSSL, curl, CA certificates and the OpenSSH client through apt. It enables the user's persistent systemd manager using loginctl enable-linger. Reconnect your SSH session if the user manager is not available yet.

The script does not install or configure SSH, change firewall rules, enroll the machine, download a daemon, install vendor tools or grant agent permissions. Run it as your development user, not sudo sh.

Other distributions need equivalent tools installed by an administrator. Signed enrollment requires a supported systemd host, an Ed25519 SSH host key and Python with tarfile.data_filter. The current signed machine baseline is Linux x86-64; direct SSH does not imply that every architecture has a signed daemon artifact.

Connect without enrollment

Back on your laptop, add your independently verified SSH alias:

TERMINAL
devbox connection add home --ssh my-box
cd ~/src/my-app
devbox setup --computer home
devbox open --computer home --with shell

Plain SSH and older hosts can use the canonical prepare/reuse path. Native workspace inventory and automatic service attribution require the current host helper; a missing helper does not install an unsigned replacement.

Optional signed daemon enrollment

Your operator must supply an HTTPS signed-release manifest and the public verification key through a trusted channel. There is no public production daemon release channel bundled into the pilot client.

TERMINAL
devbox up my-box \
  --manifest-url https://releases.example.com/stable.json \
  --public-key ./trusted-release-key.pem

Replace the example URL and key with operator-provided values. The laptop verifies the release before sending it over pinned SSH. A browser approval explicitly binds the host to your account. The command waits for an observed heartbeat; an accepted request is not installation success.

If a desktop keyring is unavailable, --allow-private-file explicitly permits private local credential files. Never put tokens in an image or paste vendor credentials into this command.

After setup

Install Claude, Codex or other tools on the host using their supported installers. Sign in there through their supported interactive flows. Configure your own OS security updates and backups. Development servers and agents share the account's privileges; worktrees are not sandboxes.

Development machines. Your code. Your control.
Private pilot · Feature availability is called out in each guide.