grim/containers/prosody

Launch via prosody and not prosodyctl and remove the explict posix load and the use of daemonize

2020-02-11, Gary Kramlich
36bb8a889535
Parents 06d0b419921c
Children 1174c22d8e65
Launch via prosody and not prosodyctl and remove the explict posix load and the use of daemonize
2 files changed, 1 insertions(+), 6 deletions(-)
  • +1 -1
    Dockerfile
  • +0 -5
    prosody.cfg.lua
    • --- a/Dockerfile Tue Feb 11 21:30:47 2020 -0600
    +++ b/Dockerfile Tue Feb 11 21:46:08 2020 -0600
    @@ -63,7 +63,7 @@
    # bosh
    EXPOSE 5280 5281
    -CMD ["prosodyctl", "start"]
    +CMD ["prosody", "-F"]
    USER prosody
    --- a/prosody.cfg.lua Tue Feb 11 21:30:47 2020 -0600
    +++ b/prosody.cfg.lua Tue Feb 11 21:46:08 2020 -0600
    @@ -6,7 +6,6 @@
    ---------- Server-wide settings ----------
    admins = { }
    use_libevent = true
    -daemonize = false;
    pidfile="/run/prosody/prosody.pid";
    consider_bosh_secure = true;
    @@ -44,14 +43,10 @@
    "prometheus"; -- enable the prometheus plugin
    "admin_telnet"; -- useful for debugging
    -
    - "posix"; -- the posix module, we explicitly load it to tell it to not daemonize
    }
    modules_disabled = {}
    -daemonize = false
    -
    allow_registration = false
    c2s_require_encryption = true