-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Examples: further postgres setup? #49
Comments
Comparing those instructions with my usual self-instructions it looks like passing |
Oh, thanks for mentioning the difference between bare metal and Docker. I now recall that I used to also run via the Docker image but unthinkingly ran directly on my Mac today. So I think your hunch about the Docker image having the proper roles already set up is a good one. Alas, if I haven't already created the role, the createdb cmd will fail:
However thanks to https://stackoverflow.com/a/35308200 it turns out that Mac users can get the So, I'm not so sure we have anything to update. I suppose we could add a note specific to Mac users running homebrew-installed postgres locally... or just have this record of my experience here in the form of a closed issue for those particular users when/if needed. |
We could change the instructions to refer to the Docker image? Folks who want to use bare metal Postgres are likely to know their dev system well enough to translate the instructions across, and folks who are not deep into Postgres may be more comfortable with Docker magic to get started rather than having to figure out bare metal (and then the instructions would in theory be portable across all OSes). |
👍 I like that. I can work on adding this to the example READMEs |
I needed a few more postgres setup commands (edit: on Mac via homebrew-installed postgres) before I could successfully run the postgres examples and wanted to check in to see if I have them right.
I followed the README in each postgres example but hit the following errors in short order (here is the postgres server output):
I ran the following commands to get past these errors. Are these correct and should we add them (or similar) to the READMEs?
The text was updated successfully, but these errors were encountered: