Package Exports
- dweb-log
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (dweb-log) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
dweb-log
view history of a dweb in the CLI
dweb-log prints all changes, the file versions, and information about the dweb:
❯ dweb-log dweb://64375abb733a62fa301b1f124427e825d292a6d3ba25a26c9d4303a7987bec65
1 [put] / 0 B (0 blocks)
2 [put] /README 175 B (1 block)
3 [put] /dweb.json 309 B (1 block)
4 [put] /far-manzanar.csv 2.0 MB (31 blocks)
5 [put] /far-minidoka.csv 2.1 MB (33 blocks)
6 [put] /far-poston.csv 3.6 MB (55 blocks)
7 [put] /wra-master.csv 73 MB (1111 blocks)
Log synced with network
Archive has 7 changes (puts: +7, dels: -0)
Current Size: 80 MB
Total Size:
- Metadata 436 B
- Content 80 MB
Blocks:
- Metadata 8
- Content 1232Install
If you already have dweb installed, run it with dweb log!
npm install -g dweb-logUsage
You can view history for a local dweb (any directory with a .dweb folder):
dweb-log /my-dataOr view history for a remote dweb using the dweb link:
dweb-log dweb://64375abb733a62fa301b1f124427e825d292a6d3ba25a26c9d4303a7987bec65 Options:
--live, -l: Keep process running and view live history