Install everything by default: Homebrew, the Brewfile, the shell, Claude Code - #13
Merged
Merged
Conversation
…ude Code The role only ever shared a Homebrew prefix somebody else had already put there, and on a stock cloud image -- which has none -- every brew task skipped as a green tick. The account came up without gh, zellij, or anything else this repo is about, and the host preset had to downgrade the shell to /bin/bash to get past the guard. A standard run should provision the standard setup, so the role now installs the prefix when it is missing, installs the login shell before creating the account, and the Brewfile and Claude Code default to on. The separate-filesystem check flips to off, because the default home is on the root volume and demanding otherwise failed every ordinary box. Claude-Session: https://claude.ai/code/session_01SW9Cwp9MTZBr5Yk577frw6
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The role only ever shared a Homebrew prefix somebody else had already put there, and on a stock cloud image -- which has none -- every brew task skipped as a green tick. The account came up without gh, zellij, or anything else this repo is about, and the host preset had to downgrade the shell to /bin/bash to get past the guard.
A standard run should provision the standard setup, so:
dev_user_brew_install, default true), refusing clearly over a root connection since the installer will not run as uid 0.dev_user_brewfileanddev_user_claude_codedefault to on.dev_user_home_require_separate_fsflips to off: the default home is on the root volume, and demanding otherwise failed every ordinary box before it had done anything.hosts/lily.ymldrops the four workaround overrides and keeps only the ssh keys, the overlay opt-out, and the sudo/docker grant.Verified on a fresh cloud box: full run in ~3.5 minutes, ok=30 changed=7 failed=0, with brew, gh, zellij, and the zsh login shell all in place afterward.
Note the new requirement stated in site.yml: the invoking account needs passwordless sudo, because the Homebrew installer calls sudo itself rather than inheriting the play's escalation.
https://claude.ai/code/session_01SW9Cwp9MTZBr5Yk577frw6