Set up ejabberd with Chef with two vhosts (kosmos and 5apps) #7

Closed
opened 2019-01-04 10:37:54 +00:00 by greg · 3 comments
Owner

I'm almost done with the cookbook, I will push a PR soon

I'm almost done with the cookbook, I will push a PR soon
greg self-assigned this 2019-01-04 10:37:54 +00:00
Owner

Nice! Shouldn't that be its own repo tho? This comment was about the IPFS cookbook. Must have mixed sth up.

<del>Nice! Shouldn't that be its own repo tho?</del> This comment was about the IPFS cookbook. Must have mixed sth up.
Owner

Regarding ejabberd: please be aware that I manually tweaked the config on andromeda!

Personally, I wouldn't put anything in Chef until we have a good setup. Otherwise it's too much hassle to work with. But if you absolutely want to do it in Chef already, then please make sure the server doesn't restart on config changes (it will kick out everyone from every chat room and clients usually don't reconnect automatically). One can use ejabberdctl reload_config to reload all config, including replaced TLS certs and whatnot. (It's optimized for 100% uptime when spreading ejabberd over several servers/nodes. Erlang style.)

Regarding ejabberd: please be aware that I manually tweaked the config on andromeda! Personally, I wouldn't put anything in Chef until we have a good setup. Otherwise it's too much hassle to work with. But if you absolutely want to do it in Chef already, then *please* make sure the server doesn't restart on config changes (it will kick out everyone from every chat room and clients usually don't reconnect automatically). One can use `ejabberdctl reload_config` to reload *all* config, including replaced TLS certs and whatnot. (It's optimized for 100% uptime when spreading ejabberd over several servers/nodes. Erlang style.)
Owner

We agreed that this issue should not include the 5apps config, as that migration is entirely separate from configuring ejabberd with Chef in the first place.

We agreed that this issue should not include the 5apps config, as that migration is entirely separate from configuring ejabberd with Chef in the first place.
greg closed this issue 2019-05-16 09:22:17 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: kosmos/chef#7
No description provided.