This guide explains how to use the Torrust Tracker Deployer in GitHub Codespaces without installing any dependencies locally.
GitHub Codespaces provides a cloud-based development environment that comes pre-configured with all the tools needed to run the Torrust Tracker Deployer:
- ✅ OpenTofu (Terraform alternative)
- ✅ Ansible
- ✅ Rust toolchain
- ✅ All project dependencies
This means you can use the deployer directly from your browser without installing anything on your local machine.
- Navigate to the torrust-tracker-deployer repository
- Click the Code button
- Select the Codespaces tab
- Click Create codespace on main
The environment will initialize automatically (takes 2-3 minutes):
- Downloads the Docker image with all dependencies
- Builds the project with
cargo build - Configures VS Code extensions
The Codespace comes pre-configured with:
- VS Code Extensions:
- Rust Analyzer (Rust language support)
- Even Better TOML (TOML formatting)
- YAML (YAML validation)
- GitHub Copilot (AI assistance)
- Settings:
- Agent skills enabled for Copilot
- JSON schema validation for environment files
- TOML formatter configuration
Once your Codespace is running, use the deployer normally. See the main documentation:
Once your Codespace is running, use the deployer normally. See the main documentation:
- User Guide - Complete deployer documentation
- Quick Start Guides - Step-by-step deployment guides
- Command Reference - All available commands
- Cloud Providers: All cloud provider deployments (Hetzner, AWS, Azure, GCP, etc.)
- Databases: SQLite, MySQL, PostgreSQL
- All CLI Commands:
create,provision,configure,release,run,destroy, etc. - E2E Tests: All tests except those requiring LXD
- Linting: All linters (
cargo run --bin linter all) - Documentation: View and edit all project documentation
- Local LXD Provider: Codespaces runs in containers, not VMs
- Nested virtualization is not available
- Cannot use
provider.type = "lxd"in environment configs - Use cloud providers instead
When using cloud provider credentials, use GitHub Codespaces secrets instead of committing them to files:
- Go to your Codespaces settings
- Under Secrets, click New secret
- Add your secrets (API tokens, SSH keys, passwords)
- Reference them as environment variables in your configuration files
Documentation: Managing Codespaces Secrets
If you have GitHub Copilot enabled, it can assist with deployment tasks. Copilot has access to:
- Project documentation (
AGENTS.md) - Agent skills (
.github/skills/) - Architecture guides and ADRs
Codespaces auto-stop after 30 minutes of inactivity. To stop manually:
- Go to https://github.com/codespaces
- Find your Codespace
- Click Stop codespace
To completely remove the Codespace and its data:
- Go to https://github.com/codespaces
- Find your Codespace
- Click Delete
GitHub Codespaces usage is billed based on compute time and storage. See GitHub Codespaces pricing for current rates.
Tips:
- Auto-stop is enabled by default (30 minutes)
- Delete Codespaces after use to avoid storage costs
- Use smaller machine types when sufficient
- GitHub Codespaces Documentation
- Devcontainer Specification
- User Guide - Complete deployer documentation
- Command Reference - All available commands