Operations
Use these pages when you already have a Firecube product and need to inspect, recover, clean up, archive, or restore it.
Operations commands work against a product URI:
For S3 products, use the full S3 URI:
Preflight
Check the CLI surface before running destructive commands:
For storage-deleting operations on local products, make sure the storage config points at the product root:
export FIRECUBE_STORAGE_TYPE=local
export FIRECUBE_STORAGE_DRIVER=fsspec
export FIRECUBE_TARGET_PATH=/data/products
For S3 products, configure the S3 storage settings and credentials described in Configuration Reference.
Common Tasks
| Task | Start here |
|---|---|
| Inspect product state | Inspect ChunkManager State |
| Recover from a crashed run | Recover Runs And Claims |
| Delete stale data or reingest a range | Delete And Reingest |
| Rebuild snapshots | Snapshots |
Create a portable .tgm archive |
Create Archives |
| Inspect or validate an archive | Inspect And Validate Archives |
| Restore an archive to Zarr | Restore Archives |
Safety Rules
- Run dry-run commands first when available.
- Use
--yes-i-really-mean-itonly after the dry-run output matches what you intend to change. - Use
--forceonly for the specific commands where it is documented. It is an operational bypass, not a confirmation flag. - Keep
.firecube/with the product unless you are intentionally discarding Firecube run history and cleanup state.
Next Steps
- ChunkManager Operations — operate the product-local
.firecube/control plane - Archive Operations — create, inspect, validate, or restore
.tgmarchives - ChunkManager Records — understand the model before running commands