- Shell 100%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
Reaching the ansible-all-2 age key through the personal vault with `bw` does not work unattended: the CLI and the desktop app keep separate sessions and Linux has no unlock bridge between them. Secrets Manager is the machine-scoped path - a token per project, and sops asks for the key through SOPS_AGE_KEY_CMD, so it is never written to disk. install-sops-key.sh installs bws and the helper, pins bitwarden.eu (bws defaults to bitwarden.com), stores the token in ~/.config/sops/bws.conf and exports SOPS_AGE_KEY_CMD via environment.d. The token prompt is opt-in (--configure) or comes from BWS_ACCESS_TOKEN for re-runs. |
||
| .vscode | ||
| bashrc-folder-loader.sh | ||
| install-all.sh | ||
| install-anytype.sh | ||
| install-bitwarden.sh | ||
| install-dns-utils.sh | ||
| install-dotfiles.sh | ||
| install-keymapp.sh | ||
| install-locale.sh | ||
| install-podman.sh | ||
| install-signal.sh | ||
| install-sops-key.sh | ||
| install-stow.sh | ||
| install-tmux-resurrect.sh | ||
| install-vpn-widget.sh | ||
| install-wireguard.sh | ||
| install-yubikey-sshkey.sh | ||
| install-yubikey.sh | ||
| install-zen-browser.sh | ||
| README.md | ||
| remove-omarchy-webapps.sh | ||
omarchy-supplement
- Main: https://forgejo.gate.okaup.de/olli/omarchy-supplement
- Mirror: https://codeberg.org/olli/omarchy-supplement
Post-install scripts for Omarchy.
The flow (first-time setup)
- Clone omarchy-supplement
- Insert YubiKey
- Run
./install-all.sh— executes every script in dependency order and summarizes failures at the end; all scripts are idempotent and failed steps can be re-run individually - The YubiKey resident SSH key authenticates the private dotfiles repo (fallback: the Codeberg mirror)
- Bitwarden is installed along the way; afterwards, manually:
- Log in at bitwarden.eu (master password + YubiKey 2FA)
- Enable the SSH agent: Bitwarden Settings → SSH agent
- From then on the "Bitwarden SSH key" vault item authenticates all repos (the ssh config wiring this up comes from the dotfiles via stow); the resident keys stay registered on Forgejo and Codeberg as break-glass
SOPS age key (ansible-all-2)
install-sops-key.sh installs bws (Bitwarden Secrets Manager CLI) and a
helper that sops calls through SOPS_AGE_KEY_CMD. The age private key stays in
Bitwarden and is fetched at decrypt time, so it is never stored on disk.
This replaces fetching it from the personal vault with bw: the CLI and the
desktop app keep separate sessions, and the biometric bridge that would let the
CLI reuse an unlocked desktop app exists on Windows and macOS only.
Setup per account (web vault, once):
- Organization → Secrets Manager → project, e.g.
homelab - Secret
SOPS_AGE_KEY= theAGE-SECRET-KEY-…line - Machine account on that project with Can read → create an access token
Then per machine:
./install-sops-key.sh --configure # paste token; press Enter to accept the
# default secret name SOPS_AGE_KEY
BWS_SERVER_URL defaults to https://vault.bitwarden.eu; bws would
otherwise talk to bitwarden.com and fail with an auth error. The token lands in
~/.config/sops/bws.conf (0600), and SOPS_AGE_KEY_CMD is exported via
~/.config/environment.d/60-sops-age-key.conf — log out and back in before
sops sees it.
Unattended/CI: set BWS_ACCESS_TOKEN and BWS_SECRET_ID and run the script
without --configure.