Kubernetes auto-sets DEVPI_PORT for service discovery, which conflicts
with our port configuration. Renamed to DEVPI_LISTEN_PORT.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Startup script checks for initialization and runs devpi-init if needed
- Root password passed via DEVPI_ROOT_PASSWORD env var from secret
- Secret template references 1Password vault item
- Updated README with setup instructions
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Add direct access config for host.containers.internal:5050 (insecure)
- Add mirror config for registry.tail8d86e.ts.net -> host.containers.internal:5050
- Revert statefulset to use registry.tail8d86e.ts.net (cleaner, if mirror works)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Use host.containers.internal:5050 instead of registry.tail8d86e.ts.net
- Minikube's CRI-O can't resolve Tailscale DNS, but can reach Zot via podman host
- Also update CLAUDE.md to spell out kubectl commands (fish abbreviations don't work in scripts)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Dockerfile for devpi-server + devpi-web image
- StatefulSet with 50Gi PVC for data persistence
- Tailscale Ingress for pypi.tail8d86e.ts.net
- README with setup and usage instructions
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
