- Replace all stale references (claude user, k8s/ dir, StatefulSet,
old Happy paths) with current state (app user, Helm chart, Deployment)
- Add full Helm chart reference table including new clusterAccess option
with usage examples for all five access levels
- Document Happy Coder daemon setup and startup flow accurately
- Update troubleshooting commands to match actual resource names
- Add Claude authentication notes (browser OAuth + API key fallback)
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Adds a clusterAccess value with five levels:
none — no cluster access (default, no RBAC resources created)
readonlyns — Role + RoleBinding: get/list/watch in release namespace
readwritens — Role + RoleBinding: full access in release namespace
readonly — ClusterRole + ClusterRoleBinding: get/list/watch cluster-wide
readwrite — ClusterRole + ClusterRoleBinding: full access cluster-wide
A ServiceAccount is created for the pod whenever access != none and
referenced in the Deployment's serviceAccountName.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
The daemon.state.json.lock lives on the home PVC and survives pod
restarts, causing happy daemon start to fail on every reboot. Moving
HAPPY_HOME_DIR to /workspace (emptyDir) means the entire happy state
directory is ephemeral and always clean on startup.
The rm -f in init-repo.sh is kept as a safety net for the within-run
case but is now a no-op on fresh starts.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
daemon.state.json.lock is left behind when the daemon crashes or is
killed (e.g. pod restart). On next startup happy daemon start sees the
lock and exits with "Failed to start daemon" without further detail.
Remove the lock file unconditionally at startup — if no daemon is
running, the lock is stale by definition.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
sudo -u failed because the app user is not in sudoers. It was unnecessary
anyway: startapp.sh (and init-repo.sh) run as the app user (UID 1000) so
happy daemon start already executes as the correct user with the right HOME.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
When init-repo.sh starts the happy daemon as root, HOME=/root so
Happy and Claude Code can't find credentials stored in /home/user.
The mobile app works when the user manually runs happy from a VSCode
terminal (as the user user) because the right home dir is in scope.
Use sudo -u with -E (preserve environment) so the daemon runs as the
correct user while still inheriting the pod's env vars (HAPPY_SERVER_URL,
HAPPY_WEBAPP_URL, ANTHROPIC_API_KEY, etc.).
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Chrome requires --no-sandbox and --disable-dev-shm-usage when running
inside a Docker container, otherwise it crashes silently and the OAuth
popup never completes.
- Add a /usr/local/bin/google-chrome wrapper that injects these flags
- Install xdg-utils so xdg-open can resolve browser handlers in VNC
- Set BROWSER env var to the wrapper so Claude Code and xdg-open both
use it when opening the Claude Max login URL
The OAuth callback (to localhost) works fine inside VNC because both
the browser and the Claude Code local auth server share the same
container network namespace.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Happy Coder requires the `claude` CLI to be present but it was never
installed in the image. Add @anthropic-ai/claude-code to the npm
global install step alongside happy-coder.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
baseimage-gui creates the app user (UID 1000) at runtime with
shell=/sbin/nologin and home=/dev/null. VSCode tries to spawn the
user's login shell for terminals, which fails with exit code 1.
Adds a cont-init script that runs as root after baseimage-gui's
adduser step and corrects both the shell and home directory.
Generated with [Claude Code](https://claude.ai/code)
via [Happy](https://happy.engineering)
Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Happy <yesreply@happy.engineering>
The npm package installs a binary named 'happy', not 'happy-coder'.
Use 'happy daemon start' to run it as a background service.
Also create $HOME on the PVC if it doesn't exist yet, which was
causing git config failures on fresh volumes.
Generated with [Claude Code](https://claude.ai/code)
via [Happy](https://happy.engineering)
Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Happy <yesreply@happy.engineering>
Introduces chart/ with deployment, service, and PVC templates driven
by Helm values instead of Kustomize variable substitution. Removes
the flux/ directory which is superseded by the chart.
Generated with [Claude Code](https://claude.ai/code)
via [Happy](https://happy.engineering)
Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Happy <yesreply@happy.engineering>
- Change hostname from antigravity.dev.farh.net to antigravity.farh.net
to match the gateway's *.farh.net listener
- Set SECURE_CONNECTION=0 since TLS is terminated at the gateway,
avoiding the redirect loop caused by the app doing its own HTTP->HTTPS redirect
Generated with [Claude Code](https://claude.ai/code)
via [Happy](https://happy.engineering)
Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Happy <yesreply@happy.engineering>
- Fix chown/sudo to use numeric UID/GID instead of hardcoded 'claude'
username (baseimage-gui creates users dynamically, name not available
at script runtime)
- Fix image name: ghcr.io/cpfarhood/devcontainer (matches github.repository)
- Fix ConfigMap name: antigravity-config -> antigravity (matches statefulset refs)
- Set github-repo in ConfigMap to headlamp-polaris-plugin
- Set HTTPRoute to external gateway at antigravity.dev.farh.net
- Add CLAUDE.md for Claude Code guidance
Generated with [Claude Code](https://claude.ai/code)
via [Happy](https://happy.engineering)
Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Happy <yesreply@happy.engineering>
Changed from incorrect `@happy-sdk/happy-coder` to correct `happy-coder`
package name. The scoped package doesn't exist on npm, causing Docker
build failures.
This fixes the v1.0.0 release Docker build.
Generated with [Claude Code](https://claude.ai/code)
via [Happy](https://happy.engineering)
Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Happy <yesreply@happy.engineering>
Changed SHA tag prefix from `{{branch}}-` to `sha-` to fix build
failures when creating releases from tags. The `{{branch}}` variable
is empty when building from tags (e.g., v1.0.0), which resulted in
invalid Docker tags like `:-7bdde95` instead of `sha-7bdde95`.
This fixes the v1.0.0 release build failure.
Generated with [Claude Code](https://claude.ai/code)
via [Happy](https://happy.engineering)
Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Happy <yesreply@happy.engineering>
Add comprehensive release management documentation and changelog.
New files:
- .github/workflows/tag-release.md: Complete release process guide
- Semantic versioning guidelines
- 3 methods for creating releases (CLI, git, web UI)
- Version bump guidelines (major/minor/patch)
- Pre-release support (alpha/beta/rc)
- Release checklist
- Docker image tagging strategy
- Example workflows
- CHANGELOG.md: Changelog following Keep a Changelog format
- Unreleased section with all current features
- Template for future releases
- Adheres to Semantic Versioning
Release Process:
1. Create annotated git tag (e.g., v1.0.0)
2. Push tag to GitHub
3. GitHub Actions automatically:
- Builds Docker image
- Pushes with multiple tags (v1.0.0, 1.0, 1, latest)
- Creates GitHub release with notes
Ready for v1.0.0 release!
Generated with [Claude Code](https://claude.ai/code)
via [Happy](https://happy.engineering)
Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Happy <yesreply@happy.engineering>
Add detailed documentation to enable autonomous deployment by other AI agents.
New files:
- DEPLOYMENT.md: Complete step-by-step deployment guide
- Prerequisites checklist
- Required vs optional variables clearly marked
- All configuration variables documented with examples
- Troubleshooting section
- Quick deploy example with all values
- Configuration summary table
- VARIABLES.md: Complete variables reference
- All variables listed with file, line, type, description
- Required variables clearly marked
- Optional variables with defaults
- Variables grouped by use case
- Quick copy templates
- Environment variables reference
Updated README.md:
- Add links to new documentation files
- Clear pointer to DEPLOYMENT.md for deployment
These docs enable another Claude Code instance to:
1. Identify all required configuration variables
2. Know where to find/set each variable
3. Understand what values are valid
4. Deploy successfully without human intervention
Generated with [Claude Code](https://claude.ai/code)
via [Happy](https://happy.engineering)
Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Happy <yesreply@happy.engineering>
Chris Farhood
github-actions[bot]