-
|
First of all @ggogel : awesome! I've been running seafile with docker for quite some time and your solution made me rethink my entire approach of handling official images vs. what I wanted. In the end I decided your solution fit my needs and I didn't look into rolling my own anymore. The work you put in is amazing. So: thank you! Also, I will need a Pro deployment soon. Has anyone used seafile-containerized as a base for that? Or even migrated an existing deployment to pro? Deploying pro could be as simple as replacing wget-calls in the Dockerfiles to the pro downloads and making sure paths are what the scripts expect after decompressing. I'm not sure how well the Pro version handles the changes that the scripts make, though. And I'm also not sure how well seafile pro will take paths changing. Has someone tried this yet? Thinking about this some more, this approach would probably break the update script processes etc. I'll look into scripts and official pro version file structure closer. As for migration: I'm thinking along the lines of: add poppler-utils to seafile-server image, add an elastic search container to seafile-net, download pro tar.gz and run migration scripts and hope for the best? Then use a "pro-version-patched" fork of seafile-containerized to keep everything up to date? I wanted to ask here before going down that road, just in case it's been done before. Thanks again for this repo! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Hi @sdsys-ch thank you for the kind words! There is a feature request issue about the pro edition, but it went stale and automatically closed #80. I never looked into using this with the pro version due to lack of time. If you can make it work, a pull request would be highly appreciated. As I wrote somewhere else, I would only provide the Dockerfiles for the pro edition, not the images, as this might be a violation of the license agreement. As for your steps, the pro version might also require additional dependencies. Further, it might be easier to start with a fresh deployment of the pro version for development. Get it working and then try to find a migration method. |
Beta Was this translation helpful? Give feedback.
Hi @sdsys-ch thank you for the kind words!
There is a feature request issue about the pro edition, but it went stale and automatically closed #80.
I never looked into using this with the pro version due to lack of time. If you can make it work, a pull request would be highly appreciated. As I wrote somewhere else, I would only provide the Dockerfiles for the pro edition, not the images, as this might be a violation of the license agreement.
As for your steps, the pro version might also require additional dependencies. Further, it might be easier to start with a fresh deployment of the pro version for development. Get it working and then try to find a migration method.