Create a SETFOP template from a source directory. The template captures filesystem metadata.
setfop create <template_name> <source_path> Example: setfop create my-template /etc/myapp
Prevent. Protect. Preserve. — That's the SETFOP way.
// About
SETFOP is a Linux utility crafted with a singular purpose — to give you precise control over ownership and permissions without compromise. Designed for administrators, DevOps engineers, and power users who believe a stable system is not a luxury, but a baseline requirement.
At its core, SETFOP is built on three uncompromising principles: preventing configuration drift before it begins protecting critical paths from unsafe or unintended changes, and preserving the integrity of your environment through every operation.
Prevent
Stop permission drift before it spreads. SETFOP captures and controls ownership and access states at the source — before inconsistencies take hold.
Protect
Shield critical paths with deliberate enforcement. Every change is validated, applied with intent and guarded against unsafe modification.
Preserve
Sustain stability through consistency. Because a controlled system is not just secure — it is reliable, reproducible, and built to last.
// Contact
Find us where the conversation is happening.
SETFOP CLI
Use the SETFOP command-line interface to create templates, apply filesystem metadata, validate destinations, inspect templates and logs, and view SETFOP information.
$ setfop help
Create a SETFOP template from a source directory. The template captures filesystem metadata.
setfop create <template_name> <source_path> Example: setfop create my-template /etc/myapp
Apply a template to a destination target. Use --dry-run when you want to preview the operation.
setfop apply <template_name> <destination_path> [--dry-run] Example: setfop apply my-template /tmp/testroot Dry-run: setfop apply my-template /tmp/testroot --dry-run
Verify a destination filesystem against an existing SETFOP template specification.
setfop validate <template_name> <destination_path> Example: setfop validate my-template /tmp/testroot
List the SETFOP templates currently available.
setfop list-templates Example: setfop list-templates
List the operation logs generated by SETFOP.
setfop list-logs Example: setfop list-logs
Display the SETFOP banner and CLI information.
setfop info Example: setfop info
Display the SETFOP command usage and help information.
setfop help Example: setfop help
Display the installed SETFOP version.
setfop version Example: setfop version
Capture filesystem metadata from your source directory into a SETFOP template.
Use apply to deploy the template, or use --dry-run first to preview what SETFOP will do.
Run validate against the destination to verify the filesystem against the specification.
/var/lib/setfop/templates/<name>.setfop/var/log/setfop/Placeholder paragraph one. This is dummy text standing in for the real introduction you will write about why SETFOP holds this verse close — the idea of carrying what is missing and preserving what already stands, mirrored in how the utility treats ownership and permissions on a system.
Placeholder paragraph two. Replace this with a short reflection on prevention — how discipline applied early removes the need for correction later, and how that same principle shapes the way SETFOP approaches configuration drift before it ever becomes a problem.
Placeholder paragraph three. Use this space to connect protection and preservation back to the reader — why a system that is watched over deliberately, rather than left to entropy, is one that lasts. Swap in your own words whenever you are ready.