@crazybrad interesting comments
The packaging work for PRO might not actually be much higher, the blocker is that Seafile require the end-user to register for access to it, if I or Cloudron register, then share that file/link out, it's a breach of Seafile licence. So we have to rely on packaging CE and documenting how to upgrade. Still working on that because I used to have PRO but reverted to CE for simplicity and didn't suffer much loss.
About S3, I like it but I prefer a layered approach, local working, remote #1 in format #1, remote #2 in format #2, even a periodic sync to a 2Tb external drive.
One thing I like about Seafile is that native files are usually synced locally, so if Seafile server or VPS goes down, it's not that difficult (just time) to repopulate a new one. The only issue is Seafile libraries which are "cold", not synced by anyone. But my new SeaClone app gets around that by downloading all libraries as native files.
I am looking into making SeaClone back up Seafile libraries into a S3 destination also, which can then handle the live vs cold vs glacier issue. And maybe different zones. But I want to get the other functions proven out first, including transferring 300Gb of non-cloudron-seafile docs into the cloudron Seafile app.
With SeaClone, a full text search based on Meilisearch and extending SeaClone to handle S3, I am not sure Seafile PRO will be necessary. But will also get around to documenting how a user can upgrade their cloudron Seafile CE to cloudron Seafile PRO.
