Set up ejabberd with Chef with two vhosts (kosmos and 5apps) #7
Labels
No Label
service
accounts
service
discourse
service
drone-ci
service
email
service
garage
service
gitea
service
ipfs
service
mastodon
service
postgres
service
remotestorage
service
wiki
service
xmpp
bug
design
dev environment
docs
duplicate
enhancement
feature
good first issue
idea
invalid
kredits-1
kredits-2
kredits-3
on hold
ops
question
release
major
release
minor
release
patch
security
ui/ux
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: kosmos/chef#7
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I'm almost done with the cookbook, I will push a PR soon
Nice! Shouldn't that be its own repo tho?This comment was about the IPFS cookbook. Must have mixed sth up.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.)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.