Launch
Launch is the quickest path from zero to a running environment. It combines the creation of a Playspec and (optionally) a Playground into a single step.
How It Works
Launch supports two workflows:
1. Import from Template
Browse templates from Stargate or My Fleet, fill in any required variables, and click Launch. The platform:
- Substitutes your variable values into the template
- Creates a new Playspec from the resolved Docker Compose YAML
- Classifies services automatically
- Optionally creates a Playground immediately
2. Import from Docker Compose
Paste or load a docker-compose.yml file directly. The platform parses it, presents the detected services for classification (static vs dynamic), and creates a Playspec. You can then launch a Playground from it.
API Launch
You can also launch environments programmatically through the Launch API endpoint:
curl -X POST https://fibe.gg/api/launch \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "my-environment",
"compose_yaml": "services:\n web:\n image: nginx\n ports:\n - \"80:80\"",
"playroom_id": 1,
"create_playground": true
}'
This is particularly useful for CI/CD pipelines, automated testing, or scripted environment provisioning.
What Gets Created
| Create Playground | Result |
|---|---|
| Yes | A new Playspec and a running Playground |
| No | A new Playspec only — you can create Playgrounds from it later |
Template Variables
When importing from a template, the launch form displays fields for each declared template variable. Variables can have:
- Display names — Human-readable labels
- Validation rules — Regex patterns that enforce input format
- Auto-generated values — Random values for variables like
$$random__NAME