If you use an org-mode task management app like beOrg, you can sync your tasks using Nextcloud+webDAV as the backend.Īt the moment, if you want cloud sync to work, you will have to save your logseq graph directly to iCloud Drive and use the iOS file picker to open the folder. Personally I use logseq as mostly a desktop app and the only logseq file I open on my phone is an org-mode file that I use for task management. I’m not trying to dissuade cloud sync here, but raise how it can be a challenging choice.Īpologies for the misunderstanding! I went back and double checked my setup and it looks like the Nextcloud iOS app doesn’t support opening a folder from the native files app. For the long term view are those generic fileshare options the right ones? What if you want to do pub/sub for notifications? What if you want to do automations on schedules without needing LogSeq running somewhere? They then migrated to Firebase due to issues in doing what they needed to do. Another app, Moo.do (renamed to LegendApp) started by utilising Google Drive as their backend storage.

If LogSeq is to provide a cloud sync, I think it should be their own, rather than a particular existing one. Why is the existing local folders which can then be synced by the OndDrive, Dropbox, Syncthing, clients not good enough? How can that be improved? Perhaps to get more at the root of the problem. Additionally, there is no native iOS client (I’m not an iOS user), due to iOS limited capability to share Syncthing files to another app that isn’t the Files app. Personally, I use Syncthing, which works great for me, but is a bit more complex than the more common options. To support just 1 will only serve a subset.

To support them all will be a mammoth task.

Some in this thread mention OneDrive, I generally use Google Drive, and many others will use Dropbox, etc. A challenge of which cloud provider to use will come up.

Onedrive vs google drive ipad