lizard scale
Scale a service (replicas / CPU / memory / storage).
Usage
lizard scale [flags]Flags
| Flag | Description |
|---|---|
--replicas <n> | Replicas 1–10 (apps) |
--cpu <cores> | 1, 2, 3, or 4 |
--memory <mb> | 128–8192 MB |
--storage <mb> | Addon volume size, grow-only |
Examples
Scale replicas horizontally
lizard scale --service api --replicas 5Each replica is its own Firecracker micro-VM behind the load balancer. Make sure your app is stateless so replicas are interchangeable.
Scale CPU and memory vertically
lizard scale --service api --cpu 4 --memory 8192Grow addon storage
lizard scale --service postgres --storage 8192Addon data volumes are grow-only — you can increase storage but not shrink it.
See also
- Scaling — horizontal vs. vertical scaling and growing addon storage
- lizard metrics — check CPU / memory / network / disk before and after scaling
- lizard ps — check replica status after a scale change
- Observability → Metrics — resource and cost monitoring