extern/apprise
1
0
Fork 0
mirror of https://github.com/caronc/apprise.git synced 2025-07-14 21:25:04 +02:00
Code Issues Packages Projects Releases Wiki Activity

Updated persistent_storage (markdown)

Chris Caron
2024-08-22 21:40:49 -04:00
parent 2e326e4bc4
commit acd1de43a5
1 changed files with 11 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
persistent_storage.md

@ -37,3 +37,13 @@ The output may look like this:<br/>
The takeaway from the screenshot above is this is another way of looking at the storage and how it's been assigned to the URLs. The takeaway from the screenshot above is this is another way of looking at the storage and how it's been assigned to the URLs.
- You can see the grouping of multiple URLs sharing the same storage endpoint is also listed here. - You can see the grouping of multiple URLs sharing the same storage endpoint is also listed here.
- It will identify the current amount of disk storage you have in use for the given plugin as well - It will identify the current amount of disk storage you have in use for the given plugin as well
- Any plugin that does not even utilize peristent storage at all, will not show up in this list. In the screenshot before this one you will see `dbus://` where it is not identified `storage` results.
The possible disk states are:
- `unused`: The plugin is not occupying any persistent storage on disk
- `stale`: At one pint a plugin exists that wrote to a location that is no longer being referenced.
- You can clear these entries by simply typing:
```bash
apprise storage clean <STALE UID>
```
- `active`: The plugin contains data written into it's cached location.