- Remove all features (universal image has everything)
- Simplified config to just image + scripts
- No dockerComposeFile reference
- Plain container that runs docker-compose internally
- Switch to universal:2 image which includes vim, curl, jq, tmux, etc.
- Remove redundant features (already in universal image)
- Simplify setup script - only install Superset-specific libs
- Keeps SSH feature for remote access
- Switch from docker-compose service to base Ubuntu container
- Add Docker-in-Docker to run docker-compose inside Codespace
- This provides git access and full dev environment
- Superset services run via docker-compose from within the container
- Use /workspaces instead of /app for Codespaces compatibility
- Fix postCreateCommand and postStartCommand paths
- Make startup script more flexible with directory detection
## Summary
Adds full GitHub Codespaces development environment configuration leveraging the new `docker-compose-light.yml` for efficient cloud development.
## Key Features
- **Lightweight Setup**: Uses `docker-compose-light.yml` which removes Redis/nginx for faster startup and lower resource usage
- **Multi-Instance Support**: Each Codespace gets isolated database volumes, perfect for testing multiple branches
- **Auto-Configuration**: Includes VS Code extensions, Python/TypeScript settings, and auto-start script
- **Developer Friendly**: Comprehensive README with SSH, VS Code, and browser connection instructions
## Implementation Details
### Files Added
- `.devcontainer/devcontainer.json` - Main configuration with:
- Docker-in-Docker support for compose
- Optimized VS Code extensions for Superset development
- Smart port forwarding (9001 for frontend, 8088 for API)
- 4-core/8GB recommended resources
- `.devcontainer/start-superset.sh` - Auto-start script that:
- Uses unique project names per Codespace
- Handles Docker daemon startup
- Shows clear status and credentials
- `.devcontainer/README.md` - Developer guide covering:
- Multiple connection methods (SSH, VS Code, browser)
- Port forwarding instructions
- Cost optimization tips
- Integration with `claude --yes` workflows
## Benefits
1. **Isolated Development**: No risk to local machine when using `claude --yes`
2. **Resource Efficiency**: Laptop stays cool, Codespaces handles the load
3. **Parallel Testing**: Spin up multiple instances for different features
4. **Quick Pause/Resume**: Auto-stops when idle, resumes in ~30 seconds
## Testing
Push to fork and create a Codespace to test. The environment auto-starts Superset and forwards port 9001 with HTTPS.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
