WIP: Set up ejabberd for kosmos.org #9
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#9
Loading…
Reference in New Issue
No description provided.
Delete Branch "feature/7-ejabberd"
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?
TODO:
The config is based off the latest config on the Andromeda server, adapted for multiple vhosts (using a config to set the SQL schema to a version that supports multiple servers using the same DB, changed the mod_http_upload config to use the
@HOST@
variable, enable mod_muc separately)In addition to my comments on the unref'd original issue for this, please be aware that the config file on Andromeda is outdated, so all the commented things are 100% not safe to use until validating every single one. I don't know where the config comes from, but it was quite annoying when I tried to uncomment things here and there.
I don't think we should use outdated commented config as a basis for a new cookbook.
The version shouldn't be hardcoded in a cookbook. But also, I don't think the entire program should live in a version-number directory.
This would have been incredibly useful: https://github.com/processone/ejabberd/blob/master/ejabberd.yml.example
I managed to get the server 100% compliant on the Conversations test suite now: https://compliance.conversations.im/server/kosmos.org/
I hacked up a bad nginx config for delivering https://xmpp.kosmos.org/.well-known/host-meta which should turn the last red result into a green one. It's for announcing the URLs for bosh and websockets.
Edit: Argh, I think that was wrong and it actually has to go on
kosmos.org
instead.Regarding a couple of things I just saw in the updates:
Btw, it would be rather useful if the to-do list in the original PR description would be more precise/expressive and granular. I don't really know what "add more config" is about for example.
Also just found #1 which is related to this.
Right, changing that
I pushed that change by accident, I reverted it so I could enable backups on Andromeda without changing the Let's Encrypt setup for now
WIP: Set up ejabberd for a public kosmos.org and a private 5apps.comto WIP: Set up ejabberd for kosmos.orgClosing in favor of #24
Pull request closed