-
Notifications
You must be signed in to change notification settings - Fork 42
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
Using the extension with NextCloud #83
Comments
Same for me, I can add a new archive in plugin firefox but after closing the browser, the archive disappeared from the extension... |
Hey guys! Seems there might still be some issues with Nextcloud in the extension. As I don't have a Nextcloud installation right now, any PRs would be very welcome! I don't currently have so much time to devote to the extension until the mobile app goes live.
|
Anyone want to do this PR ? I don't have time to do it but I can provide a NextCloud installation/account to anyone working on this PR. |
Any progress on this? Lack of NextCloud in the Browser app is really the only thing stopping me from using Buttercup, |
We're currently reworking the browser extension, and it's going well. Hopefully it should be ready some time in January. As for Nextcloud support, that depends largely on nextcloud/server#3131. I have a feeling that we won't be able to get it working from within the browser straight away due to their issues with CORS. If there was a clean way to access Nextcloud WebDAV endpoints from within the browser (Chrome extension), we'd have integrated it a while back. |
If this is not immediately possible, it may require proxying requests through the desktop application. Using a Node application as a proxy would solve the CORS issues with Nextcloud. |
Currently there are a number of open issues on the Nextcloud server repo: nextcloud/server#7365 nextcloud/server#3131 - Along with many more WebDAV related issues. At this current stage, we are considering a more drastic option of removing official support for Nextcloud. If we are unable to get the help we need to connect to Nextcloud services from the browser, we won't be able to get a browser extension integration working. If we only support Nextcloud on most of our services, it reflects badly on our product in terms of completeness. We've made some more requests (via Twitter, Spectrum and Github) to Nextcloud and the community for help. |
I wanted to post here that this works consistently for me, I just can't browse to the archive when trying to set it up. I have to type the path manually. Afterward the archive stays and works fine between browser sessions. |
Can I add that I would actually prefer the extension to be proxied through the application anyway? My .bcup archive is synced locally on the machine to my nextcloud sync folder anyway, and it just makes sense to not have that added network lag and separate setup process to sync the extension anyway. This is the way other software such as enpass handles it. |
@crankycaleb Good point sir. It's a good idea, and would end up solving a lot of issues. I do prefer using my archives through the browser, however, but some users may want to install the desktop app and be done with the setup process. Having the ability to connect to archives in the desktop application rather than adding them in the browser would definitely be a cool/powerful feature. I've added a separate issue for that here: #91 |
Thanks for the reply. It would be a shame to lose NextCloud functionality entirely, and being able to connect to the Desktop application is something which would be useful on its own, and also helpful is circumventing this issue. |
Is there a place we can add our support for nextcloud help in getting this sorted? |
@mannp Nextcloud is currently working in the remaster (soon to be version 1.0). The eta for this is January, but there's no solid date just yet. |
Hello,
I have some issues to use my *.bcup store on my nextcloud (www.dummyurl.be/nextcloud). How can I achieve that ?
I tried to use WebDAV but I didn't succeed. Can anyone help me ?
Thanks in advance.
The text was updated successfully, but these errors were encountered: