I do have the idea setting up a seafile server (community version) on a thinclient running Debian12 and Docker already for some containers. I am using Portainer and also would like to use that tool for setting up the seafile server.
I found already some How-To documents a bit more detailed for and novice-like comparing the official help files but not for portainer but I think this should be compatible.
Still doubting what is really necessary. I am a private user and sure I would like to access via the internet and therefore see the SSL/Letsencrypt functionality as crucial. Sorry to ask as a novice but what is the Seafile_Server_Hostname is this my DynDNS domain name or just my local IP?
What about Nginx is that really required or just nice to have for a private user?
Can somebody point me to a novice-like help file or link and does maybe someone have a docker-compose.yaml just including the important and necessary functionality what I can use for portainer?
Hey boris099,
it seems that you’re not that familar with linux, docker, networks and stuff. In this case, I would not try to run seafile in a non-standard way with portainer.
What you try to achieve might be quite simple for somebody with a lot of experience, but might be difficult for you. My recommendation: get yourself a cloud-server from Hetzner (starting from 5 € per Month) and follow the instructions, we added here:
You also have a YouTube video, where I explain it step-by-step…
I guarantee you, that you will have no problem to get a working seafile system. In every other case, it might get frustrating…
Hi Cristophdb,
Just to clarify I did setup my debian system, running docker and some containers already e.g. Openhab, Mosquitto, zigbee2mqtt, , I used existing .yamls for portainer and I hope I can do so for seafile as well?
But maybe you can help me answering my main question, Do I realy need reverse proxy for my private needs? For me this sound as the most complex topic and is also see exactly this quite often in error issues and questions in various forums.
Clearly I try to avoid not necessary complexity and additional possible error sources. And clearly I try to avoid additional cost for a server when I do have that little server already runnig 24/7 for my smarthome.
Can you help me with that question?
Thanks a lot
Hey boris,
you don’t need a reverse proxy. The seafile container has a nginx and you can just expose the seafile container with any port and forward it to port 80 internally.
I know the following manual is for SeaTable and not Seafile, but the logic is the same. Please look here:
Steps to do:
Best regards
Christoph