devbox v0.2.0-beta is the MVP beta release.

This release tightens the project around one clear path: clone the repo, run the setup script, switch to the dev user, and enter a disposable but polished Docker-based SWE workstation.

git clone https://github.com/1iis/devbox.git
cd devbox
chmod +x scripts/*.sh
./scripts/setup.sh

After setup, login to user dev then get in the container.

sudo -iu dev
cd ~/.devbox
./scripts/dev-in.sh

What changed:

• fresh-host setup is now the primary supported entrypoint
• setup.sh is simpler and no longer mutates before explicit converge
• env.zsh is clarified as create-once local runtime shell state
• the installed host-side repo lives at /home/dev/.devbox
• daily entry is normalized through ./scripts/dev-in.sh
• GitHub CLI and Codex state persist through Docker named volumes
• fresh Ubuntu VM validation passed for the full happy path
• make check passes in the installed workflow

The supported runtime path is still intentionally boring: direct Docker Compose from an interactive logged-in dev user.

The systemd unit can be installed and enabled, but full systemd-managed runtime with reliable interactive SSH-agent semantics remains deferred.

This is still beta software, but it is now a usable MVP.

First beta of devbox: a small, opinionated SWE workstation setup for an Ubuntu host plus a disposable Docker container.

This release is a stepping stone toward the MVP. The core workflow works and has been validated on a fresh Ubuntu VM, but some edges are still rough and the project remains tailored to our own workstation pattern.

What works

• host bootstrap via host/sync.py;
• fresh-host convenience setup via scripts/setup.sh;
• dedicated dev work user with UID/GID 1111 by default;
• active host-side repo/config copy at /home/dev/.devbox;
• Docker Compose runtime under /home/dev/.config/dev-env;
• direct Compose workflow from an interactive dev login;
• matching dev user inside the container;
• Zsh, Oh My Zsh, Powerlevel10k, and shared shell config on host and container;
• shared work directories, shell history, Git config, aliases, and SSH metadata;
• SSH auth/signing through host-owned keys and SSH agent forwarding;
• persistent GitHub CLI auth via the gh-config Docker volume;
• persistent Codex config via the codex-config Docker volume;
• SSH key import/generation for sign and dev keys;
• Makefile helpers for check/build/shell/logs/ps/up/down;
• managed-file repair and container rebuild/recovery workflow.

Known limitations

• This is beta software and still opinionated around our own workflow.
• Direct Compose from logged-in dev is the supported runtime path.
• The systemd unit can be installed/enabled, but full systemd-managed startup with interactive SSH-agent behavior is deferred.
• Some docs/templates are still pragmatic rather than polished.
• Command naming and helper scripts may change before a stable release.
• Tested primarily on fresh Ubuntu VM/local-host workflows.
• No packaged devbox CLI yet.
• No published container image; build locally from this repo.

Notes

Private SSH keys are intended to remain on the host. The container receives SSH agent access and selected public/config files, not copied private key material.

⚠️ WARNING: early alpha

Tests & fixes

⚠️ WARNING: early alpha

This is an experimental workstation/bootstrap project. It is intended for testing on disposable VMs, spare machines, or carefully reviewed personal hosts. Do not run it blindly on an important workstation.

This alpha includes:

• host-side desired-state sync via host/sync.py
• Docker Compose dev container configuration
• zsh/oh-my-zsh/p10k shell setup
• Git/GitHub/SSH-agent-oriented workflow
• basic Makefile/scripts/CI checks

Known limitations:

• real-host validation is still in progress
• Ubuntu/systemd/Docker assumptions are not fully hardened
• secrets must be reviewed by the user before use
• container rebuild/lifecycle UX is still intentionally minimal

Recommended test flow:

1. Review README.md, host/sync.py, and container/docker-compose.yml
2. Test first on a disposable Ubuntu VM or VPS
3. Run make check
4. Run python3 host/sync.py status
5. Only then try enable, start, or restart