extern/apprise
1
0
Fork 0
mirror of https://github.com/caronc/apprise.git synced 2024-12-13 10:21:51 +01: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
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
persistent_storage.md

@ -36,4 +36,14 @@ The output may look like this:<br/>
![Screenshot from 2024-08-22 21-27-39](https://github.com/user-attachments/assets/2383d487-b873-4290-960e-c2e360565771)
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.
- 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.