Removes username and password for dev db #50
Merged
Conversation
This file contains 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
This is a bit chaotic of a change, but I think it's worth it. On a mac when you install postgres (`brew install postgres`) it creates a user login for the current user and a database for that user. It configures the system to trust the current user to login to postgres without a password _because the user has already logged into the system_. On linux this configuration is almost exactly the same. The database will already trust pg users logging in with system users which name matches, but by default there is no user created. (At least this is true for the debian/ubuntu postgres install.) This is easily remidied by running: `createuser --createdb $(whoami)`. Before this change, the configuration requires that everyone create a login to their local postgres with a password that matches this project password. After this change, anyone with a properly set up local database can connect without any manual setup. After this is merged, local development servers will need to be rebooted and `bin/rails db:reset` will need to be run again.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is a bit chaotic of a change, but I think it's worth it. Let me know what you think.
On a mac when you install postgres (
brew install postgres) it creates a user login for the current user and a database for that user. It configures the system to trust the current user to login to postgres without a password because the user has already logged into the system.On linux this configuration is almost exactly the same. The database will already trust pg users logging in with system users which name matches, but by default there is no user created. (At least this is true for the debian/ubuntu postgres install.) This is easily remidied by running:
createuser --createdb $(whoami).Before this change, the configuration requires that everyone create a login to their local postgres with a password that matches this project password.
After this change, anyone with a properly set up local database can connect without any manual setup.
After this is merged, local development servers will need to be rebooted and
bin/rails db:resetwill need to be run again.