cleanup
The blocklet cleanup command allows you to perform specific maintenance operations on a blocklet, such as clearing its cache or resetting its backup configuration.
This command is useful for managing a blocklet's state, freeing up resources, or disabling automated features without removing the blocklet itself.
Usage#
blocklet cleanup <target> --app-did <did>Arguments#
Name | Description |
|---|---|
| Required. The cleanup operation to perform. See below for available targets. |
Targets#
Target | Description |
|---|---|
| Clears all cache data associated with the specified blocklet. |
| Disables the auto-backup configuration for the blocklet by clearing its backup endpoint and disabling the feature. |
Options#
Name | Description |
|---|---|
| Required. The DID of the blocklet to clean up. |
Examples#
Clear a Blocklet's Cache#
To remove all cache files for a specific blocklet, use the cache target. This can help resolve issues related to stale data.
blocklet cleanup cache --app-did z8iZpK4LAnB9g9v2mXJddW1rFw2d9rT4n2pQkUpon success, you will see a confirmation message listing the cleared cache keys:
Cache for app z8iZpK4LAnB9g9v2mXJddW1rFw2d9rT4n2pQk cleared: [cleared keys]Disable Auto-Backup for a Blocklet#
To disable automated backups for a blocklet, use the backup target. This action resets the backup endpoint and turns off the auto-backup setting in the blocklet's configuration.
blocklet cleanup backup --app-did z8iZpK4LAnB9g9v2mXJddW1rFw2d9rT4n2pQkA successful operation will produce the following output:
Blocklet z8iZpK4LAnB9g9v2mXJddW1rFw2d9rT4n2pQk auto-backup disabledAfter performing cleanup tasks, you might want to inspect the blocklet's current configuration. You can do this using the meta command.