#Seafile for mac software

#Seafile for mac software

This is absolutely crucial when you’re talking about software for sharing files with multiple people.Īs people who have collaborated on projects before well know, if even one key person can’t use the software, the whole group of collaborators need to find a different product. Looking at the downloads page, you can see that they really care about compatibility with as many devices and operating systems as possible, even if you’re using older hardware. My first impression of Seafile was that they were a well-organised bunch of people who have built a great product. And as you will soon see, they are really flexible.

It’s absolutely ideal for small business purposes, as you have the flexibility of group sharing and multiple projects, without necessarily using a public server like you do with the big cloud storag e companies. Seafile have created a completely open-source private cloud-sharing system designed for use by groups collaborating on projects. With Seafile, you can run your own private server to share documents with groups of colleagues or friends. SEAFILE_SERVER_HOSTNAME= you have tried online cloud storage solutions before and found that you’d prefer a self-hosted file sharing solution, it’s time to check out Seafile. home/user/seafile-docker/data/data:/shared home/user/seafile-docker/data/db:/var/lib/mysql '/var/run/docker.sock:/var/run/docker.sock:ro'Īnd this is my docker-file for Seafile, that I can only use if I don't use nginx-proxy or any other service that would use 80 and 443 ports: version: '2.0' '/home/user/nginx-docker/data/var/docker/nginx/acme:/etc/acme.sh' Image: 'jrcs/letsencrypt-nginx-proxy-companion:latest'

'/var/run/docker.sock:/tmp/docker.sock:ro' '/home/user/nginx-docker/data/conf:/etc/nginx/conf.d' '/home/user/nginx-docker/data/var/docker/nginx/certs:/etc/nginx/certs' '/home/user/nginx-docker/data/var/docker/nginx/vhost:/etc/nginx/vhost.d' I even tried having the Seafile service to use its own built-in SSL capabilities using custom ports ( - '8000:80' and - 8443:443), but it jsut don't work (it only works using the 80 and 433 ports directly, but that unables me to use nginx-proxy for other docker services in the same machine.Ĭurrently I'm using this docker-compose for nginx-proxy: version: '3.7' I even tested the nginx-proxy service using the nginx-dummy container with exactly the same configuration and it just works ( docker run -rm -name nginx-dummy -e VIRTUAL_HOST= -e LETSENCRYPT_HOST= -e VIRTUAL_PORT=443 -network net -d nginx:latest). In the docker logs for nginx-proxy it gives me an upstream connection error to the Seafile service. In theory if I comment out the ports section in the Seafile docker-compose file and add the VIRTUAL_PORT=433 and VIRTUAL_HOST= environment variables, and have both nginx-proxy and Seafile services connected to the same external network in docker, this should work, but it doesn't.

I'm trying to deploy a Seafile service in my home server using docker-compose and have its secure connection managed by a nginx-proxy service by another docker-compose file.