Easy automatic backups from logseq to github (or any git host) #5874

phoenixeliot · 2022-06-29T07:03:34Z

phoenixeliot
Jun 29, 2022

If you turn on git commits, you can add a git hook to the repo that automatically pushes to your git remote host every time it commits!

The setup:

Turn on Settings > Version Control > Enable Git auto commit
Restart logseq
Create a private repository on github or your git host of choice
cd into the folder that stores your logseq data
ls -al .git should list a .git file as existing by now
git remote add origin <ssh path to your github repo>
cat .git which should print something like this (this is for iCloud, path will vary): gitdir: /Users/phoenix/.logseq/git/_Users_phoenix_Library_Mobile Documents_iCloud~com~logseq~logseq_Documents/.git
git config core.hooksPath <path from prev command>/hooks to set the hooks path for the repo (may not be necessary on all machines, but was necessary on mine because I have a different global hooksPath)
cd into the directory that was in the .git file. Make sure to wrap the path in double quotes if it has spaces in it.
git config init.defaultBranch to see the default branch name
nano hooks/post-commit to edit the post-commit hook
Paste this:
```
#!/bin/bash
echo "post-commit hook"
git push origin +main
```
If your default branch name was master, replace main with master
ctrl-x then Y, then enter to save and quit nano
chmod +x hooks/post-commit to make the file executable

That should be all! Now every time logseq does an auto-commit, it should automatically get pushed to your github repo.

arjunattam · 2023-01-15T11:24:14Z

arjunattam
Jan 15, 2023

Since I was stuck on this for a bit: just want to highlight that it's critical to use the SSH url when adding the remote (HTTPS does not work)

2 replies

rien7 Mar 10, 2023

kemayo/sublime-text-git#176 (comment)

You can use git config remote.origin.url "https://{token}@github.com/username/project.git

Openuser87 Aug 10, 2025

Works like that with Gitea also. See API Usage doc for token creation and scope it accordingly (this should be a suitable reference; probably write:repository is needed, haven't figured it out exactly yet). Use the value of sha1 in the output for {token}.

alexboutros · 2024-09-12T02:37:06Z

alexboutros
Sep 12, 2024

Is this still working? I'm doing this on windows and my post-commit hook works if I manually commit, but Logseq seems to be bypassing hooks when it auto commits.

3 replies

amithm7 Dec 26, 2024

Run in the loqseq graph directory:

git config core.hooksPath '/Users/phoenix/.logseq/git/_Users_phoenix_Library_Mobile Documents_iCloud~com~logseq~logseq_Documents/.git/hooks'

but do use your gitdir path.

For me, this hook only runs on time based logsq auto commits, not when closing the window.

JaredStemper Feb 16, 2025

@alexboutros in case you or other weary travelers run into this issue on an Ubuntu machine, this was due to Snap confinement for me. Here's a more detailed breakdown/fix.

Openuser87 Aug 10, 2025

To add to this: in my case, it was a certificate issue (self-signed cert). Seems that the Flatpak-sandboxed Logseq does not access the system's "ca-trust" DB (e.g. /etc/pki/ca-trust on Fedora), where I had the cert already (Firefox has no problem with Gitea's SSL, neither does Git in CLI).

Ended up adding the cert manually into /var/lib/flatpak/app/com.logseq.Logseq/current/<long-id>/files/logseq/resources/app/node_modules/dugite/git/ssl/cacert.pem (it's a text file containing multiple certs). That fixed the Git's SSL certificate error message.

queeup · 2024-09-12T08:26:44Z

queeup
Sep 12, 2024

I asked same question in the forum. https://discuss.logseq.com/t/post-commit-git-hook-is-not-triggered-by-logseq/28097/

0 replies

Lockszmith-GH · 2024-09-12T19:31:44Z

Lockszmith-GH
Sep 12, 2024

I've been using logseq-plugin-git with mostly success, it's simpler to setup, and when things break, there is less troubleshooting involved (at least for me)

2 replies

Openuser87 Aug 10, 2025

General hint for those troubleshooting hooks: what helped me a lot was using something like

LOG_FILE=~/logseq-git-hook.log
exec > "$LOG_FILE" 2>&1

in the post-commit hook. This should redirect the output of all following commands till the end of the script to the defined log file.

After this, add your push command and any other useful output commands, e.g. env to see the environment (like what GIT_* variables are set -> where Git looks for SSL certificates and so on). This way you will get all the output into the log file, which makes the errors much clearer.

JaredStemper Aug 10, 2025

yep, i had shared this forum post i made on troubleshooting and fixing this issue for ubuntu snap packages in another thread that details this here as well

Uh oh!

Easy automatic backups from logseq to github (or any git host) #5874

Uh oh!

Uh oh!

Replies: 4 comments · 7 replies

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Replies: 4 comments 7 replies