Skip to content
This repository was archived by the owner on Aug 3, 2021. It is now read-only.

Commit e1e5e6f

Browse files
author
Matt Zumwalt
committed
tutorial info for pack verify
1 parent d60ef89 commit e1e5e6f

File tree

1 file changed

+16
-2
lines changed

1 file changed

+16
-2
lines changed

tutorial/lessons/initialize-a-pack.md

Lines changed: 16 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -44,11 +44,25 @@ $ ipfs-pack verify --help
4444

4545
```
4646
$ ipfs-pack verify
47+
Pack verified successfully!
4748
```
4849

49-
## Step 3: Build a Local IPFS Object Store inside the Pack
50+
If any of the files in your pack have changed, the output will tell you which files have changed and conclude with the message `Pack verify found some corruption.` For example, if my pack contaiined a file called `styles/site.css` and I modified it after building the pack, I would get a message like:
5051

51-
This will build an IPFS repository in the root of the pack
52+
```
53+
Checksum mismatch on ./styles/site.css. (zb2rhof9xknpBt36jvWRPVADLfsk2zhL7y5dLUSRRNfMuTGnF)
54+
Pack verify found some corruption.
55+
```
56+
57+
## Step 3: Update the PackManifest
58+
59+
If you change any of the files in your pack, you can update the PackManifest by running `ipfs-pack make` again. This will update the PackManifest to accurately represent the current contents of the pack tree.
60+
61+
This is not like git, which keeps previous versions of your files when you commit new changes. On the contrary, the current version of ipfs-pack is specifically designed **not to duplicate** any of your content. This is so you can add any amount of data, possibly hundreds of Terabytes, without taking up extra storage.
62+
63+
## Step 4: Build a Local IPFS Object Store inside the Pack
64+
65+
This will build an IPFS repository in the root of your pack
5266

5367
```
5468
$ ipfs-pack repo --help

0 commit comments

Comments
 (0)