move config.js to config.example.js

Makes it easier to maintain checkouts without upstream conflicts.
Custom config can be maintained via another branch or configuration
management software.
This commit is contained in:
Chad Phillips 2016-03-26 08:38:19 -06:00
parent 055f96bb03
commit 870f972d0b
6 changed files with 6 additions and 3 deletions

1
.gitignore vendored
View File

@ -3,6 +3,7 @@ node_modules
.idea/
*.iml
.*.tmp
config.js
deploy-local.sh
libs/app.bundle.*
libs/lib-jitsi-meet*

View File

@ -1,4 +1,4 @@
README.md
doc/debian/jitsi-meet/jitsi-meet.example
doc/debian/jitsi-meet/README
config.js
config.example.js

View File

@ -58,7 +58,7 @@ case "$1" in
# jitsi meet
JITSI_MEET_CONFIG="/etc/jitsi/meet/$JVB_HOSTNAME-config.js"
if [ ! -f $JITSI_MEET_CONFIG ] ; then
cp /usr/share/doc/jitsi-meet/config.js $JITSI_MEET_CONFIG
cp /usr/share/doc/jitsi-meet/config.example.js $JITSI_MEET_CONFIG
sed -i "s/jitsi-meet.example.com/$JVB_HOSTNAME/g" $JITSI_MEET_CONFIG
fi

2
debian/rules vendored
View File

@ -11,4 +11,4 @@ override_dh_auto_build:
override_dh_install:
dh_installdirs
dh_install -X/config.js -X/package.json
dh_install -X/config.example.js -X/package.json

View File

@ -159,6 +159,8 @@ Checkout and configure Jitsi Meet:
cd /srv
git clone https://github.com/jitsi/jitsi-meet.git
mv jitsi-meet/ jitsi.example.com
cd jitsi.example.com/
cp config.example.js config.js
```
Edit host names in `/srv/jitsi.example.com/config.js` (see also the example config file):