Fixes detecting whether prosody was newly configured on update/install.
This commit is contained in:
parent
5a9ddc3a27
commit
e1ce5ae283
|
@ -40,7 +40,7 @@ case "$1" in
|
||||||
gunzip -c /usr/share/doc/jitsi-meet-prosody/prosody.cfg.lua-jvb.example.gz > /etc/prosody/prosody.cfg.lua
|
gunzip -c /usr/share/doc/jitsi-meet-prosody/prosody.cfg.lua-jvb.example.gz > /etc/prosody/prosody.cfg.lua
|
||||||
fi
|
fi
|
||||||
|
|
||||||
if [ "PROSODY_CONFIG_PRESENT" = "true" ]; then
|
if [ "$PROSODY_CONFIG_PRESENT" = "true" ]; then
|
||||||
cp /etc/prosody/prosody.cfg.lua /etc/prosody/prosody.cfg.lua.orig
|
cp /etc/prosody/prosody.cfg.lua /etc/prosody/prosody.cfg.lua.orig
|
||||||
fi
|
fi
|
||||||
sed -i "s/jitmeet.example.com/$JVB_HOSTNAME/g" /etc/prosody/prosody.cfg.lua
|
sed -i "s/jitmeet.example.com/$JVB_HOSTNAME/g" /etc/prosody/prosody.cfg.lua
|
||||||
|
@ -58,7 +58,7 @@ case "$1" in
|
||||||
ln -sf /var/lib/prosody/$JVB_HOSTNAME.key /etc/prosody/certs/$JVB_HOSTNAME.key
|
ln -sf /var/lib/prosody/$JVB_HOSTNAME.key /etc/prosody/certs/$JVB_HOSTNAME.key
|
||||||
ln -sf /var/lib/prosody/$JVB_HOSTNAME.crt /etc/prosody/certs/$JVB_HOSTNAME.crt
|
ln -sf /var/lib/prosody/$JVB_HOSTNAME.crt /etc/prosody/certs/$JVB_HOSTNAME.crt
|
||||||
|
|
||||||
if [ "PROSODY_CONFIG_PRESENT" = "true" ]; then
|
if [ "$PROSODY_CONFIG_PRESENT" = "true" ]; then
|
||||||
invoke-rc.d prosody reload
|
invoke-rc.d prosody reload
|
||||||
else
|
else
|
||||||
invoke-rc.d prosody restart
|
invoke-rc.d prosody restart
|
||||||
|
|
Loading…
Reference in New Issue