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
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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).
Forgot to close this one, we merged #181