Add PostgreSQL primary server support to the ejabberd cookbook #180

New Issue

greg · 2020-06-10T16:36:05Z

greg commented

2020-06-10 16:36:05 +00:00

As ejabberd and PostgreSQL are both running on andromeda, the cookbook generated a config file that had localhost as the SQL server hardcoded, and created the user and database locally.

Similar to the kosmos_gitea cookbook, we need a recipe to run on the primary PostgreSQL server to create the PostgreSQL user and database, and add authorizations for the ejabberd servers. The default recipe needs to be changed to use the IP of the PostgreSQL primary instead of localhost (when ejabberd and pg primary are not running on the same server).

As ejabberd and PostgreSQL are both running on andromeda, the cookbook generated a config file that had localhost as the SQL server hardcoded, and created the user and database locally. Similar to the kosmos_gitea cookbook, we need a recipe to run on the primary PostgreSQL server to create the PostgreSQL user and database, and add authorizations for the ejabberd servers. The default recipe needs to be changed to use the IP of the PostgreSQL primary instead of localhost (when ejabberd and pg primary are not running on the same server).

greg self-assigned this 2020-06-10 16:36:05 +00:00

greg referenced this issue from a commit

2020-06-10 16:44:18 +00:00

Add PostgreSQL primary support to the kosmos-ejabberd cookbook * Move the PostgreSQL user and database creation to a pg_db recipe * Generate access rights for the ejabberd servers in the pg_db recipe * Connect to the PostgreSQL primary instead of localhost Refs #180

greg referenced this issue

2020-06-10 16:45:44 +00:00

Add PostgreSQL primary support to the kosmos-ejabberd cookbook #181

greg commented

2020-07-30 09:07:12 +00:00

Forgot to close this one, we merged #181

greg closed this issue

2020-07-30 09:07:12 +00:00