update synclounge confs for v3+

This commit is contained in:
aptalca 2020-10-28 12:25:56 -04:00
commit 4d31dcee2b
2 changed files with 22 additions and 69 deletions

View file

@ -1,4 +1,5 @@
# Use this if you are using the `latest` or `alpine` tags for the container, which contains both the web client and server applications.
# Use this with SyncLounge v3 and up.
# Make sure that you do not have HSTS enabled, otherwise http access won't work
# Make sure that your dns has a cname set for synclounge
server {
@ -12,8 +13,6 @@ server {
include /config/nginx/ssl.conf;
client_max_body_size 0;
proxy_redirect off;
proxy_buffering off;
# enable for ldap auth, fill in ldap details in ldap.conf
#include /config/nginx/ldap.conf;
@ -40,31 +39,14 @@ server {
set $upstream_proto http;
proxy_pass $upstream_proto://$upstream_app:$upstream_port;
}
###
# Server
###
# Change `/slserver` to what you set your server root to, if you change it.
location /slserver {
include /config/nginx/proxy.conf;
resolver 127.0.0.11 valid=30s;
set $upstream_app synclounge;
set $upstream_port 8089;
set $upstream_proto http;
proxy_pass $upstream_proto://$upstream_app:$upstream_port;
proxy_redirect off;
proxy_buffering off;
proxy_socket_keepalive on;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Sec-WebSocket-Extensions $http_sec_websocket_extensions;
proxy_set_header Sec-WebSocket-Key $http_sec_websocket_key;
proxy_set_header Sec-WebSocket-Version $http_sec_websocket_version;
}
# Due to a bug in SyncLounge, some websockets calls don't respect the base url (server root) setting
# TODO: Update when fixed
location /socket.io {
resolver 127.0.0.11 valid=30s;
set $upstream_app synclounge;
set $upstream_port 8089;
set $upstream_proto http;
proxy_pass $upstream_proto://$upstream_app:$upstream_port/slserver/socket.io/;
}
}