gb stop
Stop a running Genbox environment.
Synopsis
gb stop [name] [options]Description
Pauses a running environment, preserving all data. Stopped environments don’t consume compute credits but still use storage.
Arguments
| Argument | Description |
|---|---|
name | Optional. Environment name. If not provided, stops current/default environment. |
Options
| Option | Description |
|---|---|
-y, --yes | Skip confirmation prompt |
Examples
# Stop specific environment
gb stop feature-auth
# Stop without confirmation
gb stop feature-auth -yWhat Gets Preserved
- All file changes
- Database data
- Redis data (if persistent)
- PM2 configurations
- Environment variables
Cost Implications
| State | Compute Cost | Storage Cost |
|---|---|---|
| Running | Yes (by size) | Yes |
| Stopped | No | Yes |
| Destroyed | No | No |
When to Use Stop vs Destroy
Use stop when:
- Taking a break but returning soon
- Want to preserve database state
- Working on multiple features
Use destroy when:
- Completely done with the environment
- Want to free all resources
- Starting fresh
Notes
- Stopped environments can be resumed with
gb start - Storage costs are minimal but not zero
- Consider
gb destroyfor unused environments
See Also
gb start- Resume stopped environmentgb destroy- Permanently deletegb extend- Prevent auto-destroy
Last updated on