Joplin

643 readers

1 users here now

Official community of Joplin - the secure open-source note-taking app.

Capture your thoughts and securely access them from any device.

Features:

🔗 sync via Joplin Cloud, NextCloud, Dropbox, OneDrive, Syncthing, WebDAV
🌐 web clipper extension
🛡️ end-to-end encryption
✏️ Markdown support
✅ built-in todo manager
📱 runs on every desktop and mobile OS

founded 1 year ago

MODERATORS

[email protected]

I know AWS E3 is beta, but has anyone had any long term success with it? (lemm.ee)

submitted 1 year ago by [email protected] to c/[email protected]

5 comments fedilink hide all child comments

I have configured buckets and synced three joplin instances. One time it lasted a month. Another lasted a day. The most common error is *Got Metadata for Path but could not fetch content. * Anyone have any tips or tricks to getting this to work? I sure like concept, the best place to sync for me. And yes I can see the markdown file in the bucket so.....

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 1 year ago (1 children)

As far as I know, yes, it's reliable and a lot of people are using it. Often they use the open source alternative MinIO which is compatible.

Only issue I would say is in terms of maintenance because unlike other sync targets, which I can usually fix, this one I have no clue about and any fix needs to come from other contributors who may or may not be around.

[–] [email protected] 1 points 1 year ago

I appreciate all your work, I was reading the discussion on adding S3 as a sync option. Reading that made your reply here make a lot more sense, I didn't realize you were commenting as a maintainer of the main branch.

So I guess the best thing I can do is try and discover where this error is occurring. Working with a clean bucket from the desktop (Linux client) appears to be working fine. So was it an IOS app or an Android app that is causing the issues? I made sure to completely purge the data and application on an android device, and will set that up next.

If I can find a specific repeatable cause I will revisit it on github.