bcherb2
a001406a33
A disposable ubuntu container, a fake private tier and a fake bootstrap endpoint, so the whole documented path — chezmoi init --apply, dotup pick, dotup private, cmp apply, dotsecrets — can run end to end without touching a real machine or a real credential. The fake tier mirrors the real one's structure (seven secrets and one alias) because dotsecrets is copied verbatim and the "8 exports, not 7" assertion depends on that cardinality; its ids are sequential and obviously synthetic. check-verbatim.sh keeps the fake tier's copies of shipped files honest, and snapshot.sh records file modes so a 644 where a 600 belongs is a diff.
37 lines
2.2 KiB
Cheetah
37 lines
2.2 KiB
Cheetah
# chezmoi configuration for the PRIVATE tier.
|
|
#
|
|
# Seven questions, asked once at `chezmoi init` and never again -- promptStringOnce
|
|
# reads the value already in the config if there is one. Nothing here is fetched
|
|
# over a network: your own name is not a rotatable secret, and making `apply`
|
|
# depend on an API call to learn your email address would be absurd.
|
|
#
|
|
# There is deliberately no `encryption` key and no [age] section. The one secret
|
|
# in this repo is an ordinary 600-mode file; see README.md for why that is the
|
|
# cheaper answer than a per-machine root secret that was already 0 bytes on one
|
|
# machine in three.
|
|
#
|
|
# WHERE THIS FILE LANDS -- read before changing the aliases.
|
|
# `dotup` runs `chezmoi init --apply --source ~/.local/share/dotfiles-private
|
|
# -c ~/.config/chezmoi/private.toml <url>`, so this template renders to
|
|
# private.toml and the public tier keeps chezmoi.toml. The `cmp` alias carries
|
|
# the same -c. Two sources, two configs, no overlap.
|
|
#
|
|
# It was not always so, and the bug is worth remembering. Both tiers rendered
|
|
# to the DEFAULT config path, so re-running the public installer overwrote this
|
|
# file and took the seven answers below with it. Nothing failed at the time:
|
|
# the templates degrade politely when their data is missing -- config.local
|
|
# emits a comment telling you to re-run init rather than failing the apply --
|
|
# so the symptom was `git commit` not knowing who you are, days later, with
|
|
# nothing pointing back at the install that caused it. A loud failure would
|
|
# have been a smaller bug.
|
|
|
|
[data]
|
|
gitName = {{ promptStringOnce . "gitName" "git user.name" | quote }}
|
|
gitEmail = {{ promptStringOnce . "gitEmail" "git user.email" | quote }}
|
|
gitSigningKey = {{ promptStringOnce . "gitSigningKey" "git signing key id (blank for none)" "" | quote }}
|
|
|
|
giteaWanSsh = {{ promptStringOnce . "giteaWanSsh" "gitea WAN ssh prefix" "ssh://git@git.example.invalid:222/" | quote }}
|
|
giteaLanSsh = {{ promptStringOnce . "giteaLanSsh" "gitea LAN ssh prefix" "ssh://git@10.99.99.99:2223/" | quote }}
|
|
giteaWanWeb = {{ promptStringOnce . "giteaWanWeb" "gitea WAN web url" "https://git.example.invalid/" | quote }}
|
|
giteaLanWeb = {{ promptStringOnce . "giteaLanWeb" "gitea LAN web url" "http://10.99.99.99:3001/" | quote }}
|