mirror of
https://github.com/OpenRouterTeam/spawn.git
synced 2026-05-06 16:31:08 +00:00
cf53ea1fb2
Consistently use log_step for progress/status messages ("Waiting for...",
"Fetching...", "Creating...") and reserve log_info for success/completion
messages. This gives users a clear visual distinction between operations
that are still running (cyan) vs operations that have completed (green).
Also adds periodic progress updates to silent polling loops in ramnode,
cherry, and netcup IP wait functions so users see activity during long waits.
Agent: ux-engineer
Co-authored-by: A <6723574+louisgv@users.noreply.github.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
||
|---|---|---|
| .. | ||
| lib | ||
| aider.sh | ||
| amazonq.sh | ||
| claude.sh | ||
| cline.sh | ||
| codex.sh | ||
| continue.sh | ||
| gemini.sh | ||
| goose.sh | ||
| gptme.sh | ||
| interpreter.sh | ||
| kilocode.sh | ||
| nanoclaw.sh | ||
| openclaw.sh | ||
| opencode.sh | ||
| plandex.sh | ||
| README.md | ||
Cherry Servers
Cherry Servers is a European cloud provider offering bare metal and cloud VPS with full root access, hourly billing, and a REST API.
Authentication
All Cherry Servers scripts require a CHERRY_AUTH_TOKEN environment variable.
Getting your API token
- Visit Cherry Servers Portal
- Click on your profile in the top right
- Navigate to API Tokens
- Create a new token or copy an existing one
Setting the token
export CHERRY_AUTH_TOKEN="your-token-here"
Configuration
Optional environment variables:
CHERRY_AUTH_TOKEN- API authentication token (required)CHERRY_DEFAULT_PLAN- Server plan (default:cloud_vps_1)CHERRY_DEFAULT_REGION- Deployment region (default:eu_nord_1)CHERRY_DEFAULT_IMAGE- OS image (default:Ubuntu 24.04 64bit)CHERRY_SERVER_NAME- Custom server hostname
Available Plans
Cherry Servers offers various cloud VPS and bare metal plans:
cloud_vps_1- 1 vCPU, 2GB RAM, 40GB SSD (default)cloud_vps_2- 2 vCPU, 4GB RAM, 80GB SSDcloud_vps_3- 4 vCPU, 8GB RAM, 160GB SSD- Bare metal plans available through the API
View all plans: https://portal.cherryservers.com/
Regions
Available regions:
eu_nord_1- Lithuania (default)eu_west_1- Netherlandsus_east_1- USA East Coastus_west_1- USA West Coastap_southeast_1- Singapore
Usage Examples
OpenClaw on Cherry Servers
export CHERRY_AUTH_TOKEN="your-token"
bash <(curl -fsSL https://raw.githubusercontent.com/OpenRouterTeam/spawn/main/cherry/openclaw.sh)
Goose on Cherry Servers
export CHERRY_AUTH_TOKEN="your-token"
bash <(curl -fsSL https://raw.githubusercontent.com/OpenRouterTeam/spawn/main/cherry/goose.sh)
Custom configuration
export CHERRY_AUTH_TOKEN="your-token"
export CHERRY_DEFAULT_PLAN="cloud_vps_2"
export CHERRY_DEFAULT_REGION="us_east_1"
bash <(curl -fsSL https://raw.githubusercontent.com/OpenRouterTeam/spawn/main/cherry/openclaw.sh)
How it works
- Authentication - Validates
CHERRY_AUTH_TOKENwith Cherry Servers API - SSH Key - Generates SSH key pair if needed and registers public key
- Project - Fetches your default project ID from Cherry Servers account
- Provisioning - Creates cloud VPS with specified plan, region, and image
- Connectivity - Waits for SSH access and cloud-init completion
- Agent Setup - Installs agent, injects OpenRouter credentials, launches interactive session
API Documentation
- API Docs: https://api.cherryservers.com/doc/
- CLI (cherryctl): https://github.com/cherryservers/cherryctl
- Portal: https://portal.cherryservers.com/
Pricing
Cherry Servers uses hourly billing with no long-term commitments. Prices vary by plan and region.
View current pricing: https://www.cherryservers.com/pricing
Notes
- All Cherry Servers instances use
rootuser for SSH access - Servers are created with your registered SSH key automatically attached
- Full root access and IP-KVM available
- Cloud-init is supported for automated setup
- Servers can be managed via API, CLI (cherryctl), or web portal