Which Approach Should I Take for Integrating Kasm Workspaces with Linuxserver.io SWAG Container?

General
1

I’m trying to set up a reverse proxy for Kasm Workspaces using the Linuxserver.io SWAG container, and I’m not sure whether to create a new configuration file in the proxy-confs folder or use the site-confs folder. Additionally, I need some guidance on converting the provided Kasm Nginx configuration into a compatible Linuxserver.io SWAG configuration. If you have experience with integrating Kasm Workspaces and the SWAG container, I’d appreciate your input on the best approach to take and any tips on the conversion process. Your insights will help me seamlessly integrate my Kasm Workspaces service with the SWAG container.

server {
listen 443 ssl;
ssl_certificate /etc/nginx/ssl/nginx.crt;
ssl_certificate_key /etc/nginx/ssl/nginx.key;

 location / {
     # The following configurations must be configured when proxying to Kasm Workspaces

     # WebSocket Support
     proxy_set_header        Upgrade $http_upgrade;
     proxy_set_header        Connection "upgrade";

     # Host and X headers
     proxy_set_header        Host $host;
     proxy_set_header        X-Real-IP $remote_addr;
     proxy_set_header        X-Forwarded-For $proxy_add_x_forwarded_for;
     proxy_set_header        X-Forwarded-Proto $scheme;

     # Connectivity Options
     proxy_http_version      1.1;
     proxy_read_timeout      1800s;
     proxy_send_timeout      1800s;
     proxy_connect_timeout   1800s;
     proxy_buffering         off;

     # Allow large requests to support file uploads to sessions
     client_max_body_size 10M;

     # Proxy to Kasm Workspaces running locally on 8443 using ssl
     proxy_pass https://127.0.0.1:8443 ;
 }

}