Back to commands

Hosting Operations

Read-only, can be slow

Create a SHA256 Checksum Manifest

You need checksums for key files before copying or archiving them.

Command

sha256sum source/app/config.yml source/content/index.md source/content/about.md source/assets/logo.svg

Before you run this

System impact: Read-only. Can create load on large logs, directories, filesystems, or process tables.

When not to use it: Do not paste checksum output containing sensitive filenames into public logs without review.

Expected output

SHA256 hashes followed by file paths.

System impact

Read-only, can be slow. Nothing changes. The command calculates SHA256 hashes and prints them.

Scope this to the smallest useful path or service on busy systems.

Recovery / rollback: no state is changed.

When to use it

Use before a backup, migration, or manual copy when byte-level verification matters.

When not to use it

Do not paste checksum output containing sensitive filenames into public logs without review.

Watch this command run

Command transcript

This sanitized transcript shows the commands and output shape without exposing host details.

demo@lab:~$

$ find source -type f -print | sort

source/app/config.yml
source/assets/logo.svg
source/content/about.md
source/content/index.md

$ sha256sum source/app/config.yml source/content/index.md source/content/about.md source/assets/logo.svg

5a453a017f0c3bfb78e8205c21f7fcba3e26b1cc406b48664217931d26c1c50d  source/app/config.yml
5836e81dfa7b529b8773edf3addc5a43e3397d0bf8afc1534728f5090e7b2a5f  source/content/index.md
1dc8e74b2fc81bc174426952064e702cd22719d42ae1290df8f5081df42a758f  source/content/about.md
6d6ddf6160dbd0685f29b421c8f85ad7ae4e7c6eb12ef9987cc699c7debd046a  source/assets/logo.svg
View commands shown

These are the commands shown in the sanitized transcript.

Commands shown

  1. find source -type f -print | sort
  2. sha256sum source/app/config.yml source/content/index.md source/content/about.md source/assets/logo.svg

next steps

Related commands

Hosting Operations State change

Restore One File From Last Good Release

Recover a config file without rolling back the whole branch.

cd /lab/git-recovery-rollback && git restore --source=release-2026-06-25-1000 -- app/config.yml
Hosting Operations Deletes data

Verify Restored File Checksums

A restore is not validated until the bytes match.

cd restore-dr && rm -rf restore-sandbox/full && mkdir -p restore-sandbox/full && tar -xf backups/2026-06-25/site.tar -C restore-sandbox/full && (cd restore-sandbox/full && sha256sum -c CHECKSUMS.sha256)
Hosting Operations Deletes data

Diff Restored Config Against Expected

A restored config can exist and still be the wrong config.

cd restore-dr && rm -rf restore-sandbox/full && mkdir -p restore-sandbox/full && tar -xf backups/2026-06-25/site.tar -C restore-sandbox/full && diff -u expected/app/config.yml restore-sandbox/full/app/config.yml
Hosting Operations Can be slow

Compare Artifact Checksums

Verify two artifact copies match before blaming deployment code.

sha256sum artifacts/app.tar.gz releases/current/app.tar.gz
Study mapping

Use this as independent command practice: read the notes, predict the output, then compare it with the example before using a real shell.

  • lpic1:103-gnu-unix-commands
  • lpic1:104-filesystems-permissions-fhs
  • lfcs:operations-deployment
  • lfcs:services-logs
  • lfcs:storage
  • risk:read-only

Useful for

  • LPIC-1 style command-line practice
  • LFCS style performance tasks
  • Linux+ style troubleshooting review

Independent study support only. No affiliation, endorsement, exam dumps, or real exam questions.