Seafile Pro Docker Behind NGINX (Swag) container

Seafile Server
4

Huuum I’m not sure to understand how your containers communicate. Looks like your SWAG instance is in host network mode, is it?

If so, then I think the most straighforward way is:

  • Using the internal nginx with a different port mappping (8080:80 something like that)
  • Forward all traffic from the SWAG reverse-proxy:
server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name seafile.*;

    include /config/nginx/ssl.conf;

    location / {
        resolver 127.0.0.1 valid=30s;
        proxy_pass http://seafile.domain.com/;
        include /config/nginx/proxy.conf;
    }
}

This prevents annoying stuff too, like having to map shared volumes between your containers…