New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
All: sync with owncloud infinite scale - WIP #7400
Conversation
|
I don't think we'll add this. It's just webdav isn't it? So the user can just use the generic webdav sync target |
|
@laurent22 I was just playing around on Friday to see if that could be done and then pushed this code as WIP to have a "backup". Maybe I should not have made a PR yet before discussing it, sorry for that. I've updated the description to say why I think this change would be good addition for joplin. Basically I want to move my cloud storage to ocis, but not use basic-auth for the reasons described above. There is still a lot of work to be done in this PR and I'm just learning about the joplin dev environment
so if you would reconsider your decision about the change I would be very happy to keep on working on it. |
|
I'm not very keen to add this unfortunately - the bar to add a new sync target should be quite high, for example if many people ask for it or it's a particularly good service, but it seems to be one cloud storage among many. Yet it's going to be a lot of work to add it, and more so to maintain it. I would much prefer a plugin way of adding sync targets so I don't have to deal with it, but we don't have that in place yet. |
|
@laurent22 I see your point and yes a way of creating an independent plugin would be great. |
|
@individual-it a bit off topic but does ocis fully implement WebDAV spec? |
I don't think that would help, as if it was a feature that people want we would already know by now. For example, many people ask for Google Drive or MEGA so supporting this would make sense. This OCIS support in comparison didn't come up much (in fact I've never heard about it before). |
Some locking tests are still failing, but it's worked on owncloud/ocis#4999 |
The reason might be that's relatively new. |
|
One thing I find promising about ocis is that supposedly it's possible to create "apps" for it in any language. |
I think you should be able to create a Joplin webapp for ocis only with JS accessing the backend files/folders |
|
I will close this for now and hope some other solution will come up e.g. owncloud/ocis#197 could be implemented and would solve the problem If s.o. gets interested to take this forward, ping me on GitHub, this PR is far away from being nice or ready, more a PoC, but I'm still interested to work on it, if there is a chance it would be taken |
|
In case someone stumbles over this, the easiest solution to use ocis with joplin is currently the "Share via link" function, the endpoint provides WebDAV with basic auth enabled. For details see: https://dev.to/jankaritech/configure-joplin-to-work-with-owncloud-infinite-scale-ocis-19ih |
This is a wrapper around WebDAV sync to allow owncloud infinity scale(ocis) to sync with joplin.
Why this wrapper is needed:
1. authentication via openid connect:
ocis supports WebDAV as file transfer protocol, but basic auth is only supported as a fallback option for testing & development and its very discouraged to be used on production systems, see: https://doc.owncloud.com/ocis/next/deployment/services/s-list/proxy.html#authentication
The default auth mechanism is openid connect
2. performance
Besides security implications the issue is that basic-auth in ocis is pretty slow, using openid connect will make sync with ocis much faster.
3. use of spaces
ocis introduced the concept of spaces. If a user would like to sync their joplin files with a particular space it would be a pain to select the correct webdav path because its not obvious and contains long UUIDs. So a future PR could add some way of selecting a space and generating the correct webdav path out of it