WIP: Set up ejabberd for kosmos.org #24
No reviewers
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#24
Loading…
Reference in New Issue
No description provided.
Delete Branch "feature/7-ejabberd_rebased"
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?
Replaces #9, rebased against master and added Let's Encrypt setup
Refs #7
Needs to be rebased after we merge my Chef 14 PR, that includes the postgresql cookbooks
TODO:
/var/www/xmpp.kosmos.org/uploads
) owned by ejabberd, but/var/www/xmpp.kosmos.org/.well-known/
should be owned by www-dataMissed a merge conflict.
WIP: Set up ejabberd for kosmos.orgto Set up ejabberd for kosmos.orgI think this is good to go now. I have added the
max_user_conferences
option and enabled theadmin_update_sql
module to switch to the new schema that allows multiple virtual hosts using the same PostgreSQL database (introduced in 18.03, https://blog.process-one.net/ejabberd-18-03/)It seems like this should be set to "open", according to the linked issue, no?
Fixed in
ce4a4bf
I have started from the current config file on Andromeda again (
6b316f2
)Set up ejabberd for kosmos.orgto WIP: Set up ejabberd for kosmos.orgClosed in favor of #32
Pull request closed