Hello all,
Wonderful message !! We can start running Seafile 13 server! Thank you for that!… But maybe there is an update/migrate script available for Dummies? who has Seafile 11 running behind an NGINX proxy manager in a Docker situation? …. And is it necessary to run Caddy for future updates? or can i just keep NGINX as main proxy manager?
Normally i just only download the newest image of the wanted version and in my Stack YML file i only change the “image: seafileltd/seafile-mc:11.0-latest” to latest new version. (that is way i run Docker)
Is this enough or do i need to do some more …. (i read the update notes and see things like Caddy, SeaDoc etc.)
Hope someone has the solution … regards
Caddy is recommend. Advanced users (who have more knowledge about how proxy work) can use Nginx by following the document Use other reverse proxy - Seafile Admin Manual
The benefits of using Caddy is that:
- It can handle HTTPS more easily
- It is designed to work in Docker network and can be configured in a docker native way.
Hello, and thank you for the answer and recommendations. I ran as recommended the CADDY in Docker for a few weeks but had to turn back to NGINX. Reason memory and cpu consumption tripled in my situation. And clients were complaining slow responses. I am sure it has to do with my situation. but for now I have had to go back to NGINX. that saying I came to another strange thing. which I wil elaborate in a new created topic. Thank you for your help