Skip to content

klingtnet/docker-prosody

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

12 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Docker-Prosody

Quickstart

Create the Data Container

docker create --name prosody-data --volume /etc/prosody --volume /var/log/prosody --volume /var/lib/prosody klingtdotnet/prosody

Edit the Config File

  • enter admin users
  • make security settings
  • add virtual hosts, preferably in /etc/prosody/conf.avail/ and symlink them to /etc/prosody/conf.d/
docker run --rm --volumes-from prosody-data -it klingtdotnet/vim vim /etc/prosody/prosody.cfg.lua

Register an Admin User

  • replace ADMIN, HOST, PASSWORD with the actual values
  • note that the HOST has to be defined as virtual host first
docker run --rm --volumes-from prosody-data -it klingtdotnet/prosody prosodyctl register ADMIN HOST PASSWORD

Import Certificates Into the Data Container

docker run --rm --volumes-from prosody-data --volume /path/to/certs:/cert -it klingtdotnet/prosody /bin/bash
  • copy your certificates from /cert to /etc/prosody or wherever you like them to be

Run

  • now you can run prosody
docker run --rm -p 5222:5222 -p 5269:5269 --volumes-from prosody-data -it klingtdotnet/prosody prosodyctl start

as SystemD unit

  • cp prosody@.service /etc/systemd/system/ && cp prosody /etc/sysconfig/
  • customize the port numbers in /etc/sysconfig/prosody and add any port you want to expose in the ExecStart lifecycle of your /etc/systemd/system/prosody@.service (you have at least to export the S2S and C2S ports)
  • instead of editing /etc/systemd/system/prosody@.service you can override only the ExecStart lifecycle using systemctl edit prosody@ or override the whole file with systemctl edit --full prosody@

About

A debian based docker container for the prosody XMPP server

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages