We are pleased to announce that Seafile 12.0 is now available for testing. This release features a completely redesigned UI, new functionality, and significant improvements to both our administration manual and deployment architecture.
A key highlight of this release is our new Docker-centric approach to installation and management. Major architectural changes include:
Implementation of Caddy as a dedicated reverse proxy for HTTPS handling
Migration of the notification server to a separate Docker image
Improved network configuration through dedicated reverse proxy, enabling better component isolation and management
Streamlined configuration process using environment variables, eliminating redundant settings across multiple config files
These changes simplify deployment while providing greater flexibility for custom setups. Early testing feedback is welcome as we prepare for the final release.
Could you clarify the difference with 11? From what I can identify, this notificaiton server was extracted from something else and nginx was replaced with caddy. Or do I miss something?
Not trying to undermine the changes, just trying to understand what will be required for an upgrade, whether major things will change. It was somehow hard to get nginx working properly behind another reverse proxy. So if now it is possible to skip caddy and directly use another reverse proxy, it will actually reduce overhead and simplify things.
Are there any instruction to run this without caddy, but instead use and existing dedicated reverse proxy server?
Is it sufficient to uncomment the port in the seafile section of docker-compose.yml and then redirect to this?
I just started doing some testing with this. I have some general questions, and a few notes about the documentation. I will put the documentation notes in a separate post.
Are you committed to the docker change, or is it just something you are considering? I ask because we have automated a lot of our seafile server’s administration with tools like ansible, cron jobs, shell scripts, etc, and that will all be broken by docker. We also have some small adjustments to the web interface (mostly just the css) that will also be harder to implement with docker. Basically docker is trendy, but it brings us no benefit and a lot of extra hassle.
I am not sure I understand that. Are you saying that the new deployment for 12 looks like this:
client/web browser ↔ Reverse proxy with virtual hosts doing TLS (optional) ↔ Caddy reverse proxy (in a docker) ↔ nginx (in the seafile docker) ↔ seahub or seafile component (still inside that docker)
As mentioned above, I have some questions & comments about the documentation. I hope it is clear that I am not trying to be a jerk, just trying to help. I didn’t read the new documents in depth, just jumped around a bit reading some parts.
“You can also configure Seahub to run under WSGI mode behind Nginx or Apache. This is recommended for production setups.”
How? There’s no link to instructions or even a hint where to find them.
“acquisite”. That is an adjective being used like a verb. Maybe you meant acquisition?
Also as pm1234 asked, is there any way to just run without caddy if I already have a reverse proxy? This might be a good place to link to the answer. Especially since most of my testing time so far has been troubleshooting a problem that I think is Caddy breaking OAuth.
“SEAFILE_SERVER_PROTOCOL Seafile server protocol (http or https)” Which should I pick if I’m doing https but with an external reverse proxy?
“then visit http://seafile.example.com to open Seafile Web UI.” That’s a bit unclear. Should that be the IP of the container, or the IP of the host? Should it be https if SEAFILE_SERVER_PROTOCOL is set to https?
This page (especially the diagram) is unclear about what parts are separate docker containers, also about what parts are optional. For example, Seadoc is mentioned, but notification and collabora servers are not.
This is just the fist of a number of pages that seem misplaced. Or maybe this section shouldn’t be named “extensions”. Extensions are optional additional components, but (for example) the webdav component is an optional feature that is built in. There is nothing extra to install.
"From Seafile 12.0, Seafile support integrating CollaboraOnline server on the same host (only support deploying with Docker with sufficient cores and RAM), as you can follow the steps in this manual. "
I don’t understand what this is trying to say. Does it mean “The steps from this guide only cover installing collabora as another container on the same docker host that your seafile docker container is on. If you want to install on another host see the collabora documentation for instructions” ?
