9ef74eeb53
After node-config was bumped to 3.3.9 (from 3.3.6), it started throwing errors if configurations are mutated without the ALLOW_CONFIG_MUTATIONS env var set. We mutate some configs directly, but I every time I added one of those I made sure that they are always deep cloned. However, we hit an issue with kurento-client mutating a config input, which is an indirect mutation. So, to prevent further surprises I'm allowing mutations on production while prohibiting them in dev envs until I'm 100% sure nothing, direct on indirect, improperly mutates configuration values.
22 lines
666 B
Desktop File
22 lines
666 B
Desktop File
[Unit]
|
|
Description=BigBlueButton WebRTC SFU
|
|
Wants=redis-server.service
|
|
After=syslog.target network.target freeswitch.service kurento-media-server.service redis-server.service
|
|
PartOf=bigbluebutton.target
|
|
|
|
[Service]
|
|
WorkingDirectory=/usr/local/bigbluebutton/bbb-webrtc-sfu
|
|
ExecStart=/usr/bin/node server.js
|
|
Restart=always
|
|
SyslogIdentifier=bbb-webrtc-sfu
|
|
User=bigbluebutton
|
|
Group=bigbluebutton
|
|
Environment=NODE_ENV=production
|
|
Environment=NODE_CONFIG_DIR=/etc/bigbluebutton/bbb-webrtc-sfu/:/usr/local/bigbluebutton/bbb-webrtc-sfu/config/
|
|
Environment=ALLOW_CONFIG_MUTATIONS=true
|
|
CPUSchedulingPolicy=fifo
|
|
Nice=19
|
|
|
|
[Install]
|
|
WantedBy=multi-user.target bigbluebutton.target
|