This repository was archived by the owner on Jul 1, 2026. It is now read-only.
Wire dotfiles/install.sh into all four setup scripts - #64
Merged
Conversation
Each setup-*.sh now deploys the captured dotfiles automatically, as a non-fatal post-step right after the repo-clone step (which lands the workstation-bootstrap checkout that holds install.sh). Mirrors the adjacent claude-cost-export block exactly: -x-guarded so an older clone without dotfiles/install.sh skips cleanly, $WB_REPO reused, failure is a warning not a hard exit. No step renumbering — like cost-export it's an unnumbered sub-section. README updated: "not yet wired" -> "deployed by setup-*.sh". Prompt-Origin: Chris asked to wire dotfiles/install.sh into the setup scripts so a freshly-provisioned machine restores his captured local configs (alacritty et al.) without a manual step, following the just- added dotfiles/ capture directory. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Origin
Chris had just added the
dotfiles/capture directory (#63) with aninstall.shthat deploys hand-tuned local configs (alacritty et al.) onto amachine. He then asked to wire that installer into the provisioning scripts so
a freshly-provisioned or rebuilt machine restores those configs automatically,
without a manual post-provision step.
What changed
Each of the four
setup-*.shscripts now runsdotfiles/install.shautomatically, as a non-fatal post-step immediately after the existing
claude-cost-exportdeploy — i.e. after the repo-clone step that lands theworkstation-bootstrapcheckout containinginstall.sh:The block is identical across all four scripts (per the keep-in-sync rule)
and deliberately mirrors the adjacent
claude-cost-exportprecedent:-x-guarded — an older clone withoutdotfiles/install.shskips cleanly.$WB_REPO— already defined in the preceding "Installing Scripts"step; no new clone, no duplicated logic.
warn, never a hardexitmid-setup.TOTAL_STEPSand every existingN/$TOTAL_STEPSheader are untouched.dotfiles/README.mdupdated: the "Not yet wired into setup-.sh" sectionbecomes "Deployed by setup-.sh".
Verification
shellcheck --severity=warningclean on all four scripts.bash -nsyntax check passes on all four.Note (not in scope here)
The captured alacritty config pins
working_directory = "/home/cpitzi"(anabsolute path, because alacritty doesn't expand
~). Auto-deploying it assumesthe target runs as user
cpitzi. True for the homelab VMs and laptop; if afuture target uses a different username, that one value would need adjusting.
Flagging rather than fixing, since it's a property of the captured config, not
this wiring.
🤖 Generated with Claude Code