YOUR OMARCHY
IS NOW
A LINK.
Back up your own machine—or share its packages, plugins, web apps, and theme without personal files. One setup. One link.
# share the build, not your data ❯ ress share ✓ packages · plugins · web apps · theme ✓ no dotfiles · no keys · no home directory Share this line: ress apply ress.sh/gh/you/my-omarchy # or keep the whole machine for yourself ❯ ress backup ▮
Your setup, as a link
A loadout describes what is installed, not what is in your files. It contains no dotfiles, keys, or home-directory data.
The profile records package names, pinned plugin repositories, web app URLs, and a theme. Push it to a public repo and anyone can apply it.
ress apply previews everything it would add or change—including
packages, plugins, web apps, and the theme—and does nothing until you confirm.
It makes the link short. GitHub holds the loadout. ress expands it locally before making any request.
Keep the whole machine
Packages, dotfiles, themes, plugins, web apps, and enabled user services—captured to an ordinary git repo.
❯ omarchy plugin add https://github.com/tsouth89/omarchy-resurrect --enable ❯ ~/.config/omarchy/plugins/tsouth89.resurrect/bin/ress link ❯ ress init --remote https://github.com/you/my-omarchy-vault.git ❯ ress backup
Keep the vault locally or push it somewhere private. There is no ress account, server, or service to sign up for.
On a new Omarchy machine, restore from a TTY before you even have a desktop. The ISO is already installed — ress only fetches what that install is missing.
❯ omarchy plugin add https://github.com/tsouth89/omarchy-resurrect --yes ❯ ~/.config/omarchy/plugins/tsouth89.resurrect/bin/ress restore \ --from https://github.com/you/my-omarchy-vault
Read before root
A recovery tool touches the bones of your system. It should explain itself without a privacy policy.
Nothing at install time
Adding the plugin clones files. No install hooks, post-install scripts, or sudo.
Preview, then confirm
Everything a loadout would add or change is listed before installation. Nothing is removed.
Profiles cannot embed code
Only names and URLs. Plugins and git themes still contain code, so they are shown and pinned to the exact commit you accepted.
Four verbs, no fifth
Install a package, add a plugin, add a web app, set a theme. No profile field is run as a command.
Credentials never travel
Keys, tokens and hosts.yml are always excluded from captures. Secrets are opt-in and age-encrypted.
ress.sh only redirects
No storage and no accounts. GitHub hosts the profile; links expand locally before any request.