An evolving set of tools to synchronize data to and from [[Logseq]] with various other platforms. This is all POCs and ugly and misses tests. It's provided as inspiration, not plug-and-off-you-go stuff.

Git repository: https://protocultura.cl/gitea/marijn/logseq-sync

Signal to Logseq

Script: https://protocultura.cl/gitea/marijn/logseq-sync/src/branch/main/src/signal_to_logseq.py

Takes messages from [[Signal]] and appends them as blocks to the right logseq journal page. I use it to send messages to myself. All messages to self are send to logseq. If a message as attachments they are added to the assets directory and linked in the block. Eg: images will show up, audio and PDFs will be available.

Special syntax. a message starting with a !, X or L and a space will be inserted as TODO, DONE or LATER. That way adding tasks is quick.

You can add the script to your Crontab to run it once in a while to check if there are new messages to be added. If Logseq isn't running or the API is not available, nothing is changed.

Dependencies:

  • A signal account (duh)
  • A docker instance that will allow you to easily access signal via a Rest API. https://github.com/bbernhard/signal-cli-rest-api
  • Logseq with the API enabled. The access token needs to be put into the configuration file.

Warnings:

  • The Signal Rest API will access and pull all of your Signal messages to the machine running the both the docker and this tool. Think about your exposure before doing this. Which is always a good idea.

Logseq to Grav website

Makes any page marked as public to be published to a [[Grav]] website.

To publish a page simply put a page property of public:: true. Notice, property has to be in the first block, so it's a page property rather than a block property.

The script will update a git repository with the Grav site and push the changes. This allows the CI/CD to start updating the site.