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?
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.
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:
I know that this topic isnāt new, but anyway someone might be interested. So here are the results of my tests with seafile-server under portainer.
The latest seafile server (Version12 as of this writing) doesnāt use a single docker-compose.yml file. The ā.envā file lists the relevant files in the variable COMPOSE_FILE and during docker compose up, these files are processed.
I couldnāt reproduce that behaviour in portainer, but the following did work for me:
Put the relevant services (seafile-server, caddy and seadoc if need be) in one file, taking care that the network definition appears once. Go to stacks, add stack in portainer and upload your compose file or paste it in the Web editor on that page. Load your customised (and possibly renamed) .env file via the option āLoad variables from .env fileā and deploy
Push the yml-files to a github repo renaming the .env to stack.env. On the portainer page āBuild method: repositoryā you can add all (or a subset of) your yml in the repo and the stack.env will be used via a naming convention.
DidnĀ“t start yet with that seafile setup.
Realizing there is now release 12 but not stable yet, right? I think it would make sense to start with 12 but it looks like this wonĀ“t work with portainer so I could use the standard docker setup procedure instead and here at least I can find some how-to.
I quickly went through the official description (this isnĀ“t a manual:-( ) and not fully understoodā¦
What file (or yaml) will carry my parameters in 12?
I donĀ“t want to use reverse proxy nor NGINX just private use without subdomain just DynDNS means as simple as possible setup. Is that possible with 12 or better use 11 instead?
This github link above from Christoph (for 11) will that deploy NGinx automatically or can I somehow avoid that?
When I now deploy 11 can I later upgrade when 12 is stable or will that be not possible cause changes are massive from 11 to 12?
Thanks for any support and maybe some instructions or links/youtubes.
ā Copy the content and save it as a compose file.
(You can add the contents of the other .yml files to the compose file if you need to).
Download the env file and modify the options for your server.
ā Delete all parts (caddy.yml or others),you donāt need, in the first line.
Add a stack, upload your compose file to portainer and click on the button āLoad variables from .env fileā, select the env file and go for it.
If you want to change something, go into the container (e.g. seafile) and click āDuplicate/Editā. In the advanced container settings you can change the settings. Then click on āDeploy Containerā and Portainer will rebuild it.
In my opinion there is no difference between v11 and v12 for your DynDNS.
Thanks a lot. I was somehow successfully deploying using portainer but now something seems to be wrong, cannot access seafile at all.
Hopefully only a port problem?
I opened a new topic maybe others interested as well