1
0
Fork
You've already forked logseq-sync
0
Docker container for logseq sync server
  • Dockerfile 100%
2026年04月24日 12:58:02 -04:00
.gitignore ignore data dir 2026年03月13日 21:48:14 -04:00
docker-compose.yaml add directions from 4shutosh.com 2026年04月13日 09:39:57 -04:00
Dockerfile rebuild with update alpine and pnpm 2026年04月24日 12:58:02 -04:00
nginx.conf add upstream setting instead 2026年04月18日 19:45:32 -04:00
README.md umm, sync, not watch 2026年03月13日 21:49:09 -04:00

logseq-sync

First: I don't know anything about clojure or too much about node. As long as I can continue to get builds to work, I'll keep this updated. But if it gets complicated, I'm out :)

This is a docker container that provides the db-sync for self-hosted logseq sync. I built it following the instructions at https://4shutosh.com/selfhost-logseq except instead of "VPS Deployement" I did a "Docker Deployment".

Usage

!!As of 2026年03月13日, this has only been tested locally on port 8787, so currently is extremely limited!!. Eventually this will be put it behind an NGINX reverse proxy with a dedicated name, that I have physically set up on my server. The docker-compose file could be extended to support that in docker, but I am probably not going to be testing it that way myself.

Make sure you define a data directory that persists. If you don't, your sync data will be lost when the container restarts. The example docker-compose file is using a bind mount, you could use a named mount instead if you prefer. The docker-compose example has commented out lines that show that.

This is very much a work in progress