I get the following errors if I follow the tutorial to the letter (skipping letsencrypt) on Mac OS Sierra after running ./discourse-setup
Any idea what can cause this?
DISCOURSE_SMTP_PORT change failed.
DISCOURSE_SMTP_USER_NAME change failed.
DISCOURSE_SMTP_PASSWORD change failed.
web.ssl.template.yml NOT DISABLED--Are you using a non-standard template?
web.ssl.template.yml NOT DISABLED--Are you using a non-standard template?
Any help would be appreciated.
Reason for installing docker locally is that I want to try to get some custom plugins in docker running locally before I push them to production.
Aha, that one looks a lot better indeed. I’ll try later today, thanks.
Can I suggest Discourse make an install overview page? Something that explains the different ways of installing. Hopefully that will actually end up in google if you search for Discourse install
I’m using the link above to run discourse on my Mac.
Can anyone explain how can I connect to the postgresql server running inside docker? I’ve tried to map the port 5432 but weren’t able to connect using pgadmin.
psql -d postgres -c "ALTER USER postgres WITH PASSWORD '<new password>';"
By default, PostgreSQL uses peer authentication for local connections. It uses a feature of Linux whereby it can get the user that initiated the incoming connection, but this only works when the connection was made through the loopback-device (i.e. 127.0.0.1) or a UNIX socket.
When you’re connecting from a remote computer through the TCP socket, peer authentication isn’t available and the Discourse docker container is configured to have PostgreSQL fall back to MD5 authentication. This uses password hashes stored in the database itself, so these passwords are different from the system user passwords, hence passwd postgres , which changes the system login password, doesn’t affect Postgres.