README: Add note about DB fix for Apple Silicon #4282
Conversation
README.md
Outdated
| @@ -129,6 +130,7 @@ You can sign up [here](https://join.slack.com/t/rubyforgood/shared_invite/zt-21p | |||
| Please let us know by opening up an issue! We have many new contributors come through and it is likely what you experienced will happen to them as well. | |||
|
|
|||
| - *"My RBENV installation didn't work!"* - The rbenv repository provides a [rbenv-doctor script](https://github.com/rbenv/rbenv-installer#rbenv-doctor) to verify the installation and check if a ruby version is installed | |||
| - *"I see a database segmentation fault"* - If you're running Apple Silicon, adding `gssencmode: "disable"` to `config/database.yml` should resolve this. | |||
There was a problem hiding this comment.
database.yml is checked into git though. Is there a way to solve this that doesn't involve making a file dirty for your own machine?
There was a problem hiding this comment.
I've tested this on Intel Mac and the option seems okay there too. Assuming it's all okay in Linux too, we could just add it to the development section of database.yml for everyone, instead of changing the docs?
gssencmode
This option determines whether or with what priority a secure GSS TCP/IP connection will be negotiated with the server. There are three modes:
disable
only try a non-GSSAPI-encrypted connection
[...]
In development, not encrypting connections seems okay as a default?
There was a problem hiding this comment.
I think so, yep. I'm good with changing this in the YAML. I'll grab it and see if it causes any problems, and if not we should be good to merge.
There was a problem hiding this comment.
This is fine on linux as well -- I'd prefer adding it to the database.yml (development and test?) and not mentioning it in the README.
|
I tried this out on Mac and it was fine. I'm good with moving this to database.yml. Feel free to repurpose this PR to do that. |
|
Ran into this issue today ended up adding |
|
Thanks all. I've moved the change to |
|
@sampart: Your PR |
Description
My colleague @mgriffin encountered this problem, and solved it with the change mentioned. Here's fuller error output from him:
I've also very slightly tweaked a couple of other bits of the README to hopefully make it clearer.
Type of change
How Has This Been Tested?
Local setup