Use Homebrew Postgres for production#24
Merged
Merged
Conversation
Production setup now uses native Homebrew PostgreSQL — no Docker VM overhead, starts at boot via brew services, eliminates the Docker Desktop startup race on reboot. Docker Compose remains available for isolated dev databases when needed. Co-Authored-By: Claude Opus 4.6 <[email protected]>
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.
Summary
brew services(launchd-managed)bin/preflightto check for Homebrew Postgres (required) and Docker (optional)Test plan
bin/preflightcorrectly detects Homebrew Postgres vs Dockerbrew install postgresql@17+brew services startworksdocker compose up -d postgresstill works for dev use🤖 Generated with Claude Code