charleschiugit / logseq-git-sync-101 Goto Github PK

I have done the step from this https://github.com/CharlesChiuGit/Logseq-Git-Sync-101/wiki/For-Windows-users

but I don't konw what the tips said , I search on web , but can't fix it

Hi
I followed you guide which is great and connection with pull and commit work fine.
But soon as i turn on version control in Logseq i get errors.

I am a very new to Github and Linux so if you knwp why please could you explain what the issue is?

https://github.com/clstb/logsync

I get this weird message on Windows if and only if I modified the graph on my iPhone. Although this message box appears, everything looks fine, the modifications are visible. Still, very annoying. If I manually run fetch or pull from Git bash, there is no such issue.

The ssh-add command is not found in a-Shell. Where does it come from in this documentation? Per the a-Shell repo, it doesn't exist either: holzschu/a-shell#560

Thanks.

thank u for provide these methods。
I have a problem。
I have already done the first 6 steps。
I have configured the key。（.ssh）
but when i git clone。
it still needs me to input password

In the guide here https://github.com/CharlesChiuGit/Logseq-Git-Sync-101#why-use-git--github-to-sync-logseq-graph it mentions that syncthing is not available on iOS, but that is not true - I've been using https://www.mobiussync.com/ to sync iOS and PC, and I'm pretty happy with it.

For iOS, there are several advantages over Working Copy:

• cheaper price: €6 vs €25 for Working Copy
• simpler sync: Möbius Sync syncs by default in the background (which is limited in iOS to be fair), so if I need an explicit sync, I just open the app and that's it. On Working Copy I need several taps to pull commits
• simpler setup: pretty straightforward, create & share a folder on one device, accept on iOS
  • also don't need to worry about git commits changing files. I've had an issue between Linux / Windows machines where newlines would be changes every time

Disadvantages of Möbius Sync:

• both devices need to be on to sync, so can't sync on the go if the PC is not turned on at home

Setup on iOS:

• syncing Logseq with Möbius Sync is the same as any other folder, really. https://www.mobiussync.com/faq/ -> Initial setup recommends setting up & sharing folder on the PC first.
  • then, you accept that folder on iOS.
  • however, because Logseq is not a regular folder on iOS but an "app sandbox", you'll need to sync a folder not in Möbius Sync's folder but go up a level, and select a folder for your graph within Logseq's "app" folder (see MobiusSync/MobiusSync#102 (comment) & https://www.mobiussync.com/faq/ > Syncing files in other apps' sandboxes (see video below)

Overall I'm happy with syncthing, I've been using this setup with no issues for several months. Möbius Sync keeps backups of the synced files as well, so even if there's file conflicts, you can recover easily

After reading your document about logseq sync . Can l summarize the whole process into pushing your local to a github repo (public or private ? l don't know, l prefer private but l don't know whether it is supported) and clone it on your iPhone (l use iPhone so l only talk about iPhone here) ? Is that right? Besides , it seems that the working copy needs the pro version to do it. That's not user friendly.

The README image uses the word "iCloud" in place of Syncthing under "Syncthing Warnings"

You should also add that unlike a centralized git setup or iCloud, Syncthing is P2P. Which is nice from a privacy perspective and generally means a faster sync (especially with PDFs and images). But it also means both devices must be online at the same time for a sync to occur unless the user adds a server.

I follow the doc

open logseq and selected the directory, but it throw error:

Just wanted to say the Linux Instructions totally cracked me up, thanks for the chuckle!

a-shell is a free terminal app on ios/ipados, which is nice if u really don't have the money to pay for working copy.
ref

Hi there,

maybe I miss something trivial and you have an idea for me..

Obviously I want to sync mit logseq folder with git, its my own gitea Server in my local network.

I got a ssh-key and it works perfectly fine with Openssh in Windows. No problems to access my git repository with powershell and git bash, VS Code works fine too.

But if I want to use logseq, there is a error:

Do i need to define, which ssh-key logseq should use?

Regards Sam

It seems the current instructions only work if you initialize a new graph (as the step states in https://github.com/CharlesChiuGit/Logseq-Git-Sync-101/wiki/For-Windows-users). How can I adapt these instructions on already existing graph(s)?

Android version: 11
Phone brand: Sharp

My Termux install things under ~/../usr/bin instead of ~/bin/
So instead of source ~/bin/source-ssh-agent, I'll need to use source ~/../usr/bin/source-ssh-agent/ for the ssh-agent to work.
But I'm not a professional android dev, not sure if this is a general case for android 11, or it only happens on my brand.

Also, I'll need to add eval $(ssh-agent) before source command so that the script won't ask me to enter pass phrase.

In sum, my pull-graph file now looks like this:

#!/usr/bin/bash
eval $(ssh-agent)  # extra line
source ~/../usr/bin/source-ssh-agent/ # path modified
cd {your repo location} 
git pull

There are good safe checks might be helpful for the git-hooks.
https://github.com/logseq/git-auto
https://github.com/Bad3r/git-auto

Hey, first of all, this is an awesome repo. This is a huge game changer for me and my Logseq experience. I appreciate you putting this together. I don’t have an issue with your repo, but I would appreciate any help you’re willing to offer with a small sync issue I’m having.

I’m running in to a small issue where my phone has gotten out of sync following a phone upgrade. I’m unable to get working copy to recognize and track changes made via logseq on my phone. I don’t think working copy is properly linked to the local repo on my phone.

When I long-press the repo in working copy, hit “Share”, and then hit “Link Repository to Folder”, I get an error message that says “Filename already in use. Pick some other name.”

In order to fix this, I’ve picked some other folder, then tried the same process to link it to the folder of interest. I receive the same error. I’ve also tried deleting the repository and re-cloning. I’ve also tried deleting working copy from my phone and following the whole setup procedure again.

I still cannot get local changes in logseq to be tracked in working copy, and therefore, I cannot get what I write in my phone to sync with the remote repository and other devices.

Step 4 explains:

4. When download is done, long-press on the repo > Share > Link Repository to Folder > My iPhone/iPad (I would suggest don't choose iCloud) > Logseq-icon folder > create a new sub-folder under the Logseq-icon one (I would suggest don't name the folder with the same name as your repo.) > click Done

However it seems the option to Link Repository to Folder is missing for me (see screenshot). My guess is that Working Copy has changed this in an update. My question is, what should I be clicking on instead?

Recommendation: update the documentation to reflect these changes

Hi! Great collection here for Logseq sync via Git!

I setup my private Gitea instance on a webhosting server and for my Windows PC I use my work PC and a corporate firewall. Via our proxy I could make it work with VS Code, but not with the auto-commit feature of Logseq. I deactivated the TLS and both VS Code and Logseq show this warning, but it seems that Logseq Git is not commiting.

Should I add something to the Git Hooks?

Hi, given that I'm not very technical, are there any known problems with updating the scripts in this project for a logseq-git sync that's already setup and working (with older version of project)?

I followed the MacOS guide for Linux case but the step 8 show me that message in the terminal

It's now available for paid users, so I feel it'd be worth adding it + tips + issues to the diagram.

Tips probably still include working on one device at a time. Issues can include file overwriting.

Running on Ubuntu 20.04 I get the below error message every time logseq attempts to commit. The script runs fine with bash, but errors out every time it is included in the git process.

10:01:01.880 › [Git] .git/hooks/pre-commit: 11: [[: not found
Already up to date.

Hi
I have tried following your instructions but GitHub will not allow connection

You say do not use SSH but github help says to avoid this error use ssh ?????

As the contents of logseq graphs might be highly private, I am syncing my graphs with git-remote-gcrypt on a private repo on GitHub. I wonder if you're interested in also adding encryption in your 101. It should be straightforward as git-remote-gcrypt only encrypts when pushing and decrypts when pulling. However, encryption comes with exchanging gpg keys between machines and needs some understanding of gpg.

If you think this might be a good idea, I'd be happy to help.