Chef recipes for Kosmos XMPP server #32
No Reviewers
Labels
Clear labels
monitoring
bug
design
dev environment
docs
duplicate
enhancement
feature
good first issue
idea
invalid
kredits-1
kredits-2
kredits-3
on hold
ops
question
security
ui/ux
wontfix
service
discourse
Kosmos Community Forums
Infrastructure metrics, alerts, notifications, etc.
service
accounts
Kosmos Accounts
service
drone-ci
Kosmos Drone CI
service
email
mail.kosmos.org
service
garage
S3-compatible object storage
service
gitea
Kosmos Gitea
service
ipfs
Kosmos IPFS
service
lightning
Lightning address, lndhub, etc.
service
mastodon
kosmos.social
service
nostr
Relays, Blossom server, etc.
service
postgres
Database cluster
service
remotestorage
Portable data storage for the Web
service
wiki
Kosmos Wiki
service
xmpp
Kosmos Chat
Something is not working
Graphic/visual design
Config, builds, CI, deployment, etc.
Documentation
This issue or pull request already exists
Improving existing functionality
New functionality
Dive in, and start contributing
Something to consider
Not a bug
Small contribution
Medium contribution
Large contribution
Currently not actionable
Manual IT ops activities
Looking for an answer
release
major
release
minor
release
patch
All your base are belong to us
User interface, process design, etc.
This won't be fixed
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: kosmos/chef#32
Reference in New Issue
Block a user
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.
Replaces #24, history cleaned up on top of the current master
TODO:
/var/www/xmpp.kosmos.org/uploads) owned by ejabberd, but/var/www/xmpp.kosmos.org/.well-known/should be owned by www-dataWhy does the folder have to be owned by ejabberd? It's only important that it can write to it, no?
ejabberd (and no one else) needs read and write access to that folder. Do you have other users/groups in mind?
Not particularly, just asking why it's necessary for the user to own it. Seems weird to me.
I found an issue with the postgresql db creation, I'm fixing it. Then I'll make the cookbook configurable so we can use the same cookbook for kosmos and 5apps (with a different config)
I thought we're going to pair on that?
This is finally good to go. Includes the current config for kosmos.org and 5apps.com, firewall rules, Let's Encrypt setup. When we run this on andromeda the only thing that should change is that we'll be running the latest ejabberd (19.02, we're on 18.06 right now)
I had to fix an issue with the backups (since we're using a different PostgreSQL user for andromeda and ejabberd, everything is done now
This is running on andromeda, this PR can be merged! I added you as an assignee since you created the configuration and paired on the 5apps migration
Great!
That's fine. But the things we did after starting to track kredits are only a medium contribution imo. It would be unfair to count stuff from before tracking officially started, as that's part of the initial kredits for core contributors.
Set up ejabberd for kosmos.orgto Chef cookbook for Kosmos XMPP serverChef cookbook for Kosmos XMPP serverto Chef recipes for Kosmos XMPP server