Skip to content

v0.2.0: Public launch: licence, docs and guides, website, examples, secret scan

Choose a tag to compare

View all tags
@cmmichael cmmichael released this 28 Oct 15:24
· 9 commits to main since this release
v0.2.0
3c43f05

Everything needed to open the repository, on top of the allowed-users work from claude-code-web#10. Merging this merges claude-code-web#10 too.

What's in it

  • Licence and policies. MIT LICENSE, THIRD_PARTY_NOTICES.md (the MIT shim from con-ant/hass-addons, ttyd, xterm.js), SECURITY.md with private reporting, and CONTRIBUTING.md with the release labels and checks.
  • README rebuilt around who it's for. On a Mac or PC, use the Claude app. On a NAS or home server, use this. Then a quick start, reaching it from elsewhere, allowed users, a setup check, images and updates, and a comparison with HolyClaude, claudebox and beevelop/docker-claude, taken from their READMEs.
  • Guides. docs/synology.md (Container Manager, folders first, SSH tunnel for the first login, the Tailscale package), docs/pomerium.md and docs/tailscale.md (a sidecar, or Tailscale already on the host). Each ends with a check and a troubleshooting table built from the refusal reasons.
  • Use cases (docs/use-cases.md, and a section on the site and in the README): example prompts for managing a Docker stack, Pomerium and other proxy configs, restarting containers (through a read-only socket proxy), monitoring and backups, Home Assistant and Pi-hole, git and media. Recipes cover a Synology, a Raspberry Pi (arm64), read-only Docker access and git.
  • Examples. examples/pomerium/ is a full Pomerium + claude stack (config, compose, env template) plus the route on its own. examples/tailscale/ is unchanged.
  • Setup checks. /api/whoami returns who the user check sees. A refusal returns its reason (audience, proxy address, user), so a proxy setup can be checked from a browser.
  • Website (site/, published by the new pages workflow): one page with a logo, an architecture diagram and two screenshots. They're rendered from a real Claude Code session reviewing a sample NAS compose file, with the address and folder replaced by placeholders. The badge's session list is illustrative.
  • Secret scan. CI runs gitleaks over the full history.
  • Docker Hub. The image workflow also publishes to docker.io/<user>/claude-code-remote-container once the DOCKERHUB_USERNAME variable and the DOCKERHUB_TOKEN secret are set.
  • Unit test hardening. The front end can bind port 0 and report the port, which removes a pick-then-listen race seen once locally.

After merging

  • Make the repository public, then turn on Pages (Settings → Pages → Source: GitHub Actions).
  • Make the GHCR package public (Package settings → Change visibility). The Synology guide and the README use the published image without a login.
  • Docker Hub, optional: create an access token and add DOCKERHUB_USERNAME (variable) and DOCKERHUB_TOKEN (secret).

Labelled release:minor because it adds new settings (/api/whoami, Docker Hub publishing).

🤖 Generated with Claude Code

https://claude.ai/code/session_01R5XxmiR28R15untFmoAMDW

Image: ghcr.io/cmmichael/claude-code-remote-container:0.2.0 (also :0.2)
Digest: sha256:7705386793dee5e116b55635ed99f7c012bc63a59c8179ebc60ad2aecbcd5fc3
Changes: v0.1.0...v0.2.0

Assets 2
Loading