I have no idea if the memcached solution that I am using makes actual sense. Itâs just the only way how I avoid any error messages in the seahub.log.
I got the âinspirationâ from this Forum thread: Error Memcached WSGI
Does the original Seafile Manual work for everyone else and is it just my problem?
Again, I think the Seafile Manual is generally really good, but maybe we/I should update this specific section?
I would be glad if people would share their experience.
I had the same experience with memcached (post fastcgi) and eventually landed on the same solution you found.
Maybe we can get some feedback from @DerDanilo on the status of the Manual, how to update it, and a short critique of this approach vs. the one put forward in the official documentation.
@wthess I am happy to do a pull request and did that before, but I first would like to understand what actually needs / should be changed.
Currently I just did trial and error and eventually came to a solution. I do not fully understand the memcached settings I am using now and the consequences of the differences to the manual.
I donât really want to put that into the manual.
@mercury cheers, and letâs see what @DerDanilo or maybe one of the developers might say. I agree to the âpost fastcgiâ part.
I have to agree. I donât want to increase the noise level around configuration issues at Seafile. That kind of thing does not enhance the project at all. It isnât enough to say âI got it workingâ and then drop the issue. It has to work completely, be reproducible by others and survive upgrades. And to that last point it really has to be vetted by Development.
As for our memcached issue, there have to be pros and cons as to which approach or binding is employed. Iâd like to hear (and learn) from others as to what those issues are. Only after all that story is in can I really consider updating the Manual. Does that sound reasonable?
I have to remove memcached from seahub_settings.py for document changes to be saved and updated from the Onlyoffice document server running inside Seafile CE 6.2.5 (using subdirectory method). That is, other machines do not see the changes but the editor does, even after the document is closed and re-opened. The edited document does show that all changes have been saved.
Iâve got it working with local socket as well. I can add this to the manual once I find some time.
The overall âexcitementâ of the Seafile community is not high enough in my opinion to spend tons of time on the CE manual. Itâs ready when itâs done.