PlanPusk Archive Restore Notes https://html.cafe/x0f7b83a1 Two original practical notes about local Python checksum manifests and restore comparisons. Free guide; optional paid affiliate storage recommendation is disclosed in each article. en Mon, 26 Oct 2026 22:43:39 GMT PlanPusk Project with Codex assistance Check a restored folder with relative paths and SHA-256 https://html.cafe/x0f7b83a1#utm_source=rssamplifier_archive&utm_medium=owned_rss&utm_campaign=nr184_archive_manifest urn:planpusk:nr184:manifest-v1 Mon, 26 Oct 2026 22:43:39 GMT PlanPusk Project Python Backups A folder can look complete after extraction while one file has changed or is missing. A small manifest makes that comparison explicit: record each relative path, its byte count and its SHA-256 digest before archiving, then record the restored folder and compare the two lists.

Keep the comparison outside the folders

Our free guide supplies two original Python scripts, archive_manifest.py and compare_manifests.py. They use the Python standard library. The example below assumes Python 3 and the two downloaded scripts are already available. The folder names are a synthetic example, not paths from a real project.

python3 archive_manifest.py ./original > before.jsonl
# Create and extract your archive to ./restored
python3 archive_manifest.py ./restored > after.jsonl
python3 compare_manifests.py before.jsonl after.jsonl

before.jsonl and after.jsonl sit outside the folders being scanned. Putting the output inside its own input folder can include a file that is changing during the scan. Use a stable source folder and keep the baseline manifest with your restore instructions.

Read the result in context

Equal paths, byte counts and digests provide evidence that the compared file contents match. A manifest alone does not contain the original file bytes, restore a missing file, or verify permissions and application behaviour. A practical restore check also opens the restored documents or project in the application that needs them.

The guide and script downloads are free without a website account, email or purchase. The scripts run locally after download; this workflow does not ask you to upload an archive to the guide.

Open the free restore guide and download both scripts.

Creator disclosure: this is original PlanPusk project material prepared with Codex assistance. Optional paid storage disclosure: the guide includes a pCloud affiliate link; we may receive a commission if you purchase through it. A storage purchase is optional and is not required to use either script. HTML.cafe adds a third-party script whose data collection we have not audited. No actual backup, purchase or profit is claimed by this worked example.

]]>
A folder can look complete after extraction while one file has changed or is missing. A small manifest makes that comparison explicit: record each relative path, its byte count and its SHA-256 digest before archiving, then record the restored folder and compare the two lists.

Keep the comparison outside the folders

Our free guide supplies two original Python scripts, archive_manifest.py and compare_manifests.py. They use the Python standard library. The example below assumes Python 3 and the two downloaded scripts are already available. The folder names are a synthetic example, not paths from a real project.

python3 archive_manifest.py ./original > before.jsonl
# Create and extract your archive to ./restored
python3 archive_manifest.py ./restored > after.jsonl
python3 compare_manifests.py before.jsonl after.jsonl

before.jsonl and after.jsonl sit outside the folders being scanned. Putting the output inside its own input folder can include a file that is changing during the scan. Use a stable source folder and keep the baseline manifest with your restore instructions.

Read the result in context

Equal paths, byte counts and digests provide evidence that the compared file contents match. A manifest alone does not contain the original file bytes, restore a missing file, or verify permissions and application behaviour. A practical restore check also opens the restored documents or project in the application that needs them.

The guide and script downloads are free without a website account, email or purchase. The scripts run locally after download; this workflow does not ask you to upload an archive to the guide.

Open the free restore guide and download both scripts.

Creator disclosure: this is original PlanPusk project material prepared with Codex assistance. Optional paid storage disclosure: the guide includes a pCloud affiliate link; we may receive a commission if you purchase through it. A storage purchase is optional and is not required to use either script. HTML.cafe adds a third-party script whose data collection we have not audited. No actual backup, purchase or profit is claimed by this worked example.

]]>
Read added, missing and changed files after a restore https://html.cafe/x0f7b83a1#utm_source=rssamplifier_archive&utm_medium=owned_rss&utm_campaign=nr184_compare_manifests urn:planpusk:nr184:compare-v1 Mon, 26 Oct 2026 22:43:39 GMT PlanPusk Project Python Backups A restore comparison is easier to act on when the differences are grouped by file path. Our free compare_manifests.py utility reads the JSONL output from archive_manifest.py and helps identify added, missing and changed files. Both scripts are available from the same free guide.

A small, synthetic example

Imagine that the source folder had notes.txt, checklist.txt and draft.txt. The restored folder has notes.txt, checklist.txt and extra.txt. The notes.txt digest still matches, while checklist.txt has different bytes.

  • notes.txt is unchanged in this example.
  • checklist.txt is changed: the path exists in both lists but its contents differ.
  • draft.txt is missing from the restored list.
  • extra.txt was added to the restored list.

Those are four paths across the two lists, with one in each group. They are illustrative filenames and conditions, not a manifest collected from anyone's files. An added file may be intentional, such as an extraction note; a changed file may also be an intentional edit. Compare against the state you actually intended to restore.

Keep a usable baseline

Generate the first manifest before packing the archive, save it outside the scanned folder, and keep a copy that can be found during a restore. Generate the second manifest after extraction. If a scan reports an error, resolve it before treating the comparison as complete. Matching checksums describe the bytes that were compared; they do not prove that a document opens correctly or that an archive contains every folder you meant to select.

Download the free manifest and comparison scripts with the worked command sequence. Python 3 is needed to run them locally. The guide itself requires no account or payment.

Creator disclosure: PlanPusk prepared this original explanation with Codex assistance. The guide offers a separate optional paid pCloud recommendation through an affiliate link, which may earn us a commission on a purchase. The free scripts do not require that service. The HTML.cafe hosting page adds a third-party script whose data collection we have not audited. This synthetic example contains no real manifests, project contents or customer data.

]]>
A restore comparison is easier to act on when the differences are grouped by file path. Our free compare_manifests.py utility reads the JSONL output from archive_manifest.py and helps identify added, missing and changed files. Both scripts are available from the same free guide.

A small, synthetic example

Imagine that the source folder had notes.txt, checklist.txt and draft.txt. The restored folder has notes.txt, checklist.txt and extra.txt. The notes.txt digest still matches, while checklist.txt has different bytes.

  • notes.txt is unchanged in this example.
  • checklist.txt is changed: the path exists in both lists but its contents differ.
  • draft.txt is missing from the restored list.
  • extra.txt was added to the restored list.

Those are four paths across the two lists, with one in each group. They are illustrative filenames and conditions, not a manifest collected from anyone's files. An added file may be intentional, such as an extraction note; a changed file may also be an intentional edit. Compare against the state you actually intended to restore.

Keep a usable baseline

Generate the first manifest before packing the archive, save it outside the scanned folder, and keep a copy that can be found during a restore. Generate the second manifest after extraction. If a scan reports an error, resolve it before treating the comparison as complete. Matching checksums describe the bytes that were compared; they do not prove that a document opens correctly or that an archive contains every folder you meant to select.

Download the free manifest and comparison scripts with the worked command sequence. Python 3 is needed to run them locally. The guide itself requires no account or payment.

Creator disclosure: PlanPusk prepared this original explanation with Codex assistance. The guide offers a separate optional paid pCloud recommendation through an affiliate link, which may earn us a commission on a purchase. The free scripts do not require that service. The HTML.cafe hosting page adds a third-party script whose data collection we have not audited. This synthetic example contains no real manifests, project contents or customer data.

]]>