Hey there, our company has been using Seafile for around two years, while it is a working solution, we would never recommend it to anyone in a business environment. Unlike most paid solutions, the clients are always full of bugs, upgrading the server can sometimes knock out the Seafile on a linux server (We fully admit this could be linux ignorance on our part)
With that said as the username says, the program iswhatitis and we still use it.
We are about to move our Seafile server, which in essence means deleting the entire server and moving to a new server backend.
My thought is can we trust seafile to just delete the server and all its contents, move to the new backend, set the new server up, then connect the local clients and let them recurse back to the server, or will seafile pull some stunt like grabbing the empty directories from the new server and deleting all the local content.
We always back up the local repositories in case something like this would occur.
Please do not mistake my tart comments for not loving this program, I believe if the developers stabilized the program it might someday be production ready, but I have personally watched a department update an entire folder and then 6 hours later, the client still had not updated the server. The way to do this is to shutdown the client completely, then reload and force a resync, this may not sound like an issue, but in those 6 hours another department was waiting for the data to sync so they could use it, and being a “tested” solution we did not babysit it, so no one knew until over 8 hours later that Seafile had not synced a thing, now we babysit every transfer (even though we should not have to!)
Hopefully someone can give me a suggestion on the behavior of the server if we delete the server copy and recurse back to the new one with the local content.