Selected work

Archive Desk for the terminal

Back up a project folder from the terminal.

Create, check, compare, restore. Four commands.

Needs Node.js 24 and nothing else. Tested on Windows with Node.js 24.19.0.

archive-desk-cli-source.zipa2c1 33ef ... bcf2 7dd4

Four commands, one saved baseline

Type your folders and the commands rewrite to match. Use an output folder outside the project.

Showing the example paths.

  1. 1

    Create and verify a backup

    node cli.mjs backup "C:\Projects\MyProject" --out "C:\Backups\project-new.zip"

    Saves a new ZIP and verifies it from disk. Never overwrites.

  2. 2

    Check a saved copy again

    node cli.mjs verify "C:\Backups\project-new.zip"

    Records, CRCs and every fingerprint.

  3. 3

    Compare the project later

    node cli.mjs compare "C:\Backups\project-new.zip" "C:\Projects\MyProject" --report "C:\Backups\project-new-comparison.json"

    JSON of added, removed, changed and unchanged paths.

  4. 4

    Restore into a new folder

    node cli.mjs restore "C:\Backups\project-new.zip" --out "C:\Recovered\project-new"

    New destination only. Each file is read back against the manifest.

    A partial restore is reported and left to inspect. No timestamps or permissions.

In a test run: 1 added, 1 removed, 1 changed and 2 unchanged. The project files stayed untouched.

Check what gets included

The command lists every skipped path. By default it leaves out common dependency and credential names:

  • .git, node_modules and .ssh
  • .env, .env.* and credentials.json
  • Files ending in .pem, .key, .p12 or .pfx

Filename patterns, not a content scan. Symlinks and special files are refused.

Not an atomic snapshot. Close editors first.

What has been checked

  • Twelve command tests pass, five for restore.
  • Unicode, empty and binary files restored, all 1,351 bytes matched.
  • Refused restores touched nothing.

Tested on Windows only. Linux and macOS have not been checked. There is no installer or scheduled sync.