We thought we\u2019d go big this Maker Monday, what with it being the serious business of Back to School and all. Here\u2019s a tutorial from the latest issue of <\/em>Raspberry Pi Official Magazine that shows you how to keep everything in your brain organised and searchable, from notes <\/em><\/strong>to<\/em><\/strong> appointments <\/em><\/strong>and<\/em><\/strong> ideas<\/em><\/strong>.<\/em><\/strong><\/p>\n A while ago, we read the book Building a Second Brain<\/em> by Tiago Forte (Figure 1<\/strong>). It starts with the idea that we are all a little overloaded and bombarded with information, and how overwhelming it can be to not be able to retrieve the information that we need at a later time. The foundation of a Second Brain<\/em> is to increase the capture and cataloguing rate of information, and the book delves into lots of custom systems to tag, organise, prioritise, and retrieve information. This Personal Knowledge Management (PKM) idea feels similar to the ideas of David Allen and the older, but still brilliant, \u2018Getting Things Done\u2019 system.\u00a0<\/p>\n At the heart of these PKM systems is the concept of ubiquitous capture: the idea that, as a start, we need to capture the information of interest. This is also an idea in journalling and is basically being proactive about note-taking. The question then is how to store these bits of information. There are lots of options.\u00a0<\/p>\n There\u2019s nothing wrong with a pile of sticky notes (or index cards, which are the author\u2019s favourite) and a pen; however, you can quickly end up with a huge pile of notes which need to be physically stored and searched. Of course, lots of people have moved to software applications. Many of the popular operating systems for mobile devices will include some form of note-taking application, and there are many that require you to make an account and store your data in the cloud, so it\u2019s a nice challenge to build a system that doesn\u2019t store your information on another person\u2019s\u00a0computer. Finally, the solutions we explore here use open source projects so we can examine the code should we need to maximise our privacy and security.\u00a0<\/p>\n The solution we are going to explore is centred around Logseq, a privacy-focused open source knowledge management system. It\u2019s a really rich piece of software with more features than most people will use, and we\u2019ll only really cover the basics, although the basics are incredibly powerful. Later in the article we\u2019ll use Syncthing, another open source project, to synchronise our second brain created in Logseq across multiple devices. Syncthing is a peer-to-peer continuous file synchronisation tool, which means that it can sync data without passing that data through the cloud\/a company\u2019s server. It also encrypts and decrypts the data in transit, so you are nice and secure whilst the data is moving. It\u2019s totally OK to just install Logseq on one machine and have a play with it to see if it can meet your needs.<\/p>\n We began by installing Logseq on a Raspberry Pi 500 (Figure\u00a02<\/strong>), but note that the procedure outlined below is the same for any Raspberry Pi board; so, for example, we have this system currently set up on the Raspberry Pi 500, a Raspberry Pi Zero, and our Uconsole, which contains the Raspberry Pi Compute Module 4 board.<\/p>\n Currently, the only option to install a build of Logseq is via Snap. So, if working from a fresh Raspberry Pi OS installation, we\u2019ll need to install the Snap package manager. If you already have Snap installed on your system, then you can skip to installing Logseq.\u00a0<\/p>\n To install Snap and then Logseq, open the Terminal application and, at the prompt, enter:\u00a0<\/p>\n We can then install the latest version of Snap using:\u00a0<\/p>\n We then need to reboot Raspberry Pi 500:<\/p>\n Once the machine has rebooted, open the Terminal application; we need to install a Snap package called \u2018snapd\u2019:<\/p>\n With Snap installed and set up, we can then go ahead and install Logseq using:<\/p>\n With Logseq now installed, you will be able to launch it using the desktop applications menu at\u00a0Accessories > Logseq Desktop. On launch, Logseq will open a demo page showing a journal-style entry for the current date (Figure 3<\/strong>). In this entry is a basic tutorial on how Logseq works and some of its functions.\u00a0<\/p>\n In Logseq terminology, when you create a collection of notes and potentially other assets, you insert them into a \u2018graph\u2019. Scrolling on the current demo page, you should find a section where Logseq wants us to specify a folder it can use to contain all our information. You can use an existing folder, but it\u2019s probably better to create a new folder. Click to \u2018add a graph\u2019 and then give your folder the title that you want your second brain system to be called; we went with \u20182nd_Brain\u2019, rather unimaginatively.\u00a0This OG version of Logseq will, in this specified folder, store all the data you input into the system. It essentially creates Markdown files and also stores any uploaded assets (PDFs, pictures, audio, etc.) to an assets subfolder. This means that you could manually copy this entire folder, move it to another machine, and open it in another installation of Logseq.\u00a0<\/p>\n With the file specified and a new graph created, let\u2019s put some basic information into our second brain system. Whenever you open Logseq, it will create an empty journal page for the current day. Each of these journal dates will become a page item in our system. So let\u2019s type something in the currently empty journal page.\u00a0<\/p>\n As an example, we typed a note: \u2018Spotted a book I\u2019d like to read today, called \u201cHow to Build a Second Brain\u201d by Tiago Forte\u2019 (Figure 4<\/strong>). Now imagine we wrote a note about a different book every day. Currently the only way to return to this piece of information in the future is if we remember the date or use the search function. If we\u2019d forgotten the name of the book, however, we could only really search for terms like \u2018book\u2019, which might generate a lot of returned results. What we need is to tag our information. Tagging is the secret sauce of Logseq that makes it incredibly useful.\u00a0<\/p>\n To add a tag to a piece of information, we place the tag term inside two pairs of square brackets. Let\u2019s return to the line we entered earlier and write at the end of the line (though tags can be placed anywhere in text) \u2018[[Books To Read]]\u2019 and then press ENTER<\/strong>. Note that the tag text will become a clickable link (Figure 5<\/strong>). If we click that tag, the link then takes us to a new page, as every tag we add to Logseq becomes a new page. On the new [[Books To Read]]<\/strong> page, we will see the reference to our line, \u2018\u2026\u2009\u201cHow to Build a Second Brain\u201d by Tiago Forte\u2019. If we click the back arrow in the upper toolbar, we can navigate back to our journal. Let\u2019s add a second line, \u2018Another book I\u2019d like to read, \u201cDesign an RP2040 Board with KiCad\u201d by Jo Hinchliffe\u2019. This line will always be listed in the current journal page, but again we can add the [[Books To Read]]<\/strong> tag as we did previously and it will be populated to that tag page. If we write a book title every day into separate journal entries, so long as we use the [[Books To Read]]<\/strong> tag, they will all appear on the tag page (Figure\u00a06<\/strong>). Note that in the image we made a typo in the book title; in a way, this doesn\u2019t matter \u2014 just be sure to spell your tags correctly!\u00a0<\/p>\n However, tags are free and unlimited, so it\u2019s worth tagging information widely with lots of tags, thinking about how you might remember them in the future. As an example, in our second brain Logseq setup, we have some Customs and Excise tariff numbers; these numbers are unique for different types of goods that you sell, and it can be quite hard when faced with a new item to research and identify the correct tariff number as they are quite complex and there are a lot of them. It\u2019s definitely the type of information you want to keep note of rather than have to discover every time. If we consider how we might think about these numbers, it\u2019s pretty clear to tag them as [[Tariff]]<\/strong>, but sometimes we might think [[Customs]]<\/strong> or might want the tariff number for a particular product or project, so we might use the [[Product Name]]<\/strong> as a tag. Adding multiple tags to items of information increases your chances of finding your way back to the info when needed, as the same piece of information will appear regardless of which tag you remember or use in the future.\u00a0<\/p>\n We need to move on to other aspects of the system, but it\u2019s worth noting that you can type \u2018\/Upload an asset\u2019 (or rather start by writing \u2018\/U\u2019, which will autocomplete) to add files of pretty much any type to an entry. You can then tag these in the usual way, and the asset will be copied to the assets folder in your designated directory. This means you don\u2019t have to worry about copying and pasting items, or losing links to items, as they are all stored in the folder. Finally, note that you can embed links and videos, and even highlight and annotate PDFs, in Logseq, tagging the exact part of a PDF to return to later.\u00a0<\/p>\n So we have the basis of our second brain setup, but we\u2019d like it to be accessible on more than one device. Our approach for this will be to install Logseq on another device, and then use Syncthing to synchronise folders so that our second brain folder is on both devices and up to date (Figure 7<\/strong>).\u00a0<\/p>\n To install Syncthing on Raspberry Pi, it\u2019s best to first run:<\/p>\n \u2026to make sure our system is up to date. Then we need to add the \u2018apt-transport-https\u2019 package to the apt service by running:<\/p>\n We then need to store the Syncthing GPG keys on Raspberry Pi in our keyrings<\/strong> directory. In a nutshell, this means that the Syncthing packages we install are legitimate and are sourced from the right place. To do this, run the following command:<\/p>\n We can now add the Syncthing repository with:\u00a0<\/p>\n We can then update the packages once again with:\u00a0<\/p>\n And then finally install Syncthing with:\u00a0<\/p>\n Once it\u2019s installed, you will find two Syncthing items in the applications menu: one is a simple \u2018Start Syncthing\u2019 which sets the service running; the other is \u2018Syncthing Web UI\u2019. First, double-click the \u2018Start Syncthing\u2019 application, then double-click the \u2018Syncthing Web UI\u2019. This should now launch the default web browser and will land on a default Syncthing admin page for the device. From here, we can set up files and directories for\u00a0synchronisation.\u00a0<\/p>\n First, let\u2019s click the \u2018Add Folder\u2019 button. In the \u2018Add Folder\u2019 dialog box (Figure 8<\/strong>), we can add a folder label \u2014 for example, \u2018second_brain_directory\u2019, as we are going to share the directory we made for our Logseq second brain files. Leave the Folder ID with the default generated identifier string, and then in the last input, Folder Path, set the exact folder path to match where the Logseq folder you made is. So for example, if you made your Logseq folder in the default user directory of a Raspberry Pi and you called it \u20182nd_Brain\u2019, you can input the tilde (~) character (which means the same as \/home\/username) and write ~\/2nd_Brain<\/strong>. Clicking Save sets this file to be shared.\u00a0<\/p>\n On another device with Logseq and Syncthing installed (we used our Uconsole), on the same Web UI page you can click on the short name identification\u00a0in the \u2018This Device\u2019 area. Clicking this launches a dialog box with a QR code and a long-form ID string for the device (Figure 9<\/strong>). This is a 56-digit string with dashes. Back on the Raspberry Pi 500, you can click the \u2018Add Remote Device\u2019 button and type in the long device ID; note that you don\u2019t need to add the dashes or spaces, just the long string. If you leave the Device Name section empty, it will populate with the random generated device name on the other device; or you can add a more descriptive name such as \u2018Uconsole\u2019 or \u2018Pi Zero\u2019 here.\u00a0<\/p>\n Quick tip<\/strong><\/p>\n Note that you don\u2019t have to be on the same network for Syncthing to synchronise your files.\u00a0<\/p>\n<\/blockquote>\n Finally, by clicking on the folder we created to share earlier on the Raspberry Pi 500, and then clicking the Edit button, we can move over to the Sharing tab in the dialog box, where we should be able to see the remote device we just added (Figure 10<\/strong>). If we tick the box to share with that device, we can then click Save. Give everything a couple of minutes to work through the networks and then check on the other device; you should see a notification that the other device wants to share a folder with you. Accept the folder and follow the instructions to set up a path to a directory to synchronise that folder to. All that then remains is to open Logseq on the second device and click \u2018add graph\u2019, navigating to the synchronised folder we just made. This means if we add or change anything in Logseq on our first device (Raspberry Pi 500) or our second device (Uconsole), then these changes appear on both devices, keeping our Logseq second brain system up to date. You can of course repeat this process, sharing and synchronising your 2nd_Brain<\/strong> Logseq folder onto as many devices as you want.<\/p>\n Note that synchronising folders is not a backup! If you accidentally delete part or all of your Logseq folder content, this will propagate through Syncthing and delete it everywhere! A solution to this is to, on one or more devices, set up a system that periodically backs up your folder to another folder.\u00a0<\/p>\n To do this, we will create a small Bash script that will copy a target folder to a different folder that we won\u2019t sync. We\u2019ll then use the cron service to make this script run periodically so that we don\u2019t have to think about it. You can do this on any of the Raspberry Pi devices, or indeed more than one; however, it would be most useful on a device which can be left always on. In our system, we have it set up on a Raspberry Pi Zero W which runs headless and is an \u2018always on\u2019 device in our workspace. However, we\u2019ll set this up here on the Raspberry Pi 500, as it\u2019s easy to do by typing commands into the terminal.\u00a0<\/p>\n To begin, launch the Terminal application, and in the root directory of your Raspberry Pi device, launch the nano text editor to write a Bash script:<\/p>\n In nano, type the following small Bash script, replacing Save this file with a name like backup_script.sh<\/strong>.\u00a0<\/p>\n We need to set this file as executable, so in the same working directory as the script, we need to run:<\/p>\n We can now test the backup_script.sh<\/strong> script by, in the same directory, executing it with:<\/p>\n You can then use the File Manager (or the Terminal) to check if the files have been copied to the newly created backup folder.\u00a0Finally, we can automate this script using a cronjob. We can do this by editing a file called crontab<\/strong>. Type:<\/p>\n \u2026in the terminal. If this is the first time you have done this, it might ask which editor you would like to use; select nano from the list. In the now-open crontab<\/strong> file, there is a long section of comments that give a great overview of how the cron system works (Figure 11<\/strong>). At the end of the file, we can add a line that has the following structure: minutes, hour, day of month, month, day of week, followed by the command. You can leave slots empty using an asterisk ( \u2026would execute the backup_script.sh<\/strong> script every Monday at 10.46am. Note that if you wanted to run the script once a day, you\u2019d simply leave the day of week value empty, such as:\u00a0<\/p>\n Of course, you can extend and enhance the system; it would be great to back up the folders to an attached SSD, or you might like to explore how to add monitoring and logging to your cron system. Logseq and Syncthing are available for most desktop distributions, and they are also ported to smartphone operating systems, meaning you can carry your private, secure, and backed-up second brain with you always!<\/p>\n This article appears in\u00a0issue 169\u00a0of\u00a0Raspberry Pi Official Magazine<\/em>, which you can\u00a0access online.\u00a0You can also\u00a0subscribe\u00a0to the print version of our magazine. Not only do we deliver worldwide, but those who sign up to the six- or twelve-month print subscription will receive a FREE\u00a0Raspberry Pi Pico 2 W!<\/p>\n![\"\"](\"https:\/\/www.raspberrypi.com\/app\/uploads\/2026\/09\/logseq_graph_uconsole-Large-1024x768.jpeg\")
The end of sticky notes<\/h2>\n
![\"\"](\"https:\/\/www.raspberrypi.com\/app\/uploads\/2026\/09\/main-800x600.jpg\")
![\"\"](\"https:\/\/www.raspberrypi.com\/app\/uploads\/2026\/09\/pi500_logseq-1024x768.jpg\")
$ sudo apt update<\/code><\/pre>\n$ sudo apt install snapd<\/code><\/pre>\n$ sudo reboot<\/code><\/pre>\n$ sudo snap install snapd<\/code><\/pre>\n$ sudo snap install logseq \u2013channel =og<\/code><\/pre>\n![\"\"](\"https:\/\/www.raspberrypi.com\/app\/uploads\/2026\/09\/logseq_open_first-1024x576.png\")
Filling the brain with information<\/h2>\n
![\"\"](\"https:\/\/www.raspberrypi.com\/app\/uploads\/2026\/09\/untagged_entry-1024x576.png\")
![\"\"](\"https:\/\/www.raspberrypi.com\/app\/uploads\/2026\/09\/tagged_info-1024x576.png\")
![\"\"](\"https:\/\/www.raspberrypi.com\/app\/uploads\/2026\/09\/books_to_read-1024x576.png\")
![\"\"](\"https:\/\/www.raspberrypi.com\/app\/uploads\/2026\/09\/syncthing1-1024x576.png\")
$ sudo apt update\n\n$ sudo apt upgrade<\/code><\/pre>\n$ sudo apt install apt-transport-https<\/code><\/pre>\n$ curl -s | gpg --dearmor | sudo tee \/usr\/share\/keyrings\/syncthing-archive-keyring.gpg >\/dev\/null<\/code><\/pre>\n$ echo \"deb [signed-by=\/usr\/share\/keyrings\/syncthing-archive-keyring.gpg] syncthing stable\" | sudo tee \/etc\/apt\/sources.list.d\/syncthing.list<\/code><\/pre>\n$ sudo apt update<\/code><\/pre>\n$ sudo apt install syncthing<\/code><\/pre>\n![\"\"](\"https:\/\/www.raspberrypi.com\/app\/uploads\/2026\/09\/add_folder-1024x576.png\")
![\"\"](\"https:\/\/www.raspberrypi.com\/app\/uploads\/2026\/09\/add_device-1024x576.png\")
\n
![\"\"](\"https:\/\/www.raspberrypi.com\/app\/uploads\/2026\/09\/edit_folder_share-1024x576.png\")
Careful now!<\/strong><\/h2>\n
$ sudo nano<\/code><\/pre>\nLOGSEQ_Directory_Path<\/code> with the path to your Logseq folder. If your folder is in the home directory, you don\u2019t need any leading edge slashes; so, backing up our \u20182nd_brain\u2019 folder in the home directory to \u2018backup_2nd_brain\u2019 is really straightforward to\u00a0input. \u00a0<\/p>\n#! \/bin\/sh\u00a0\n\nrsync -avh LOGSEQ_Directory_Path\nBackup_Directory_Path<\/code><\/pre>\n$ sudo chmod +x backup_script.sh<\/code><\/pre>\n$.\/backup_script.sh<\/code><\/pre>\n$ crontab -e<\/code><\/pre>\n*<\/code>) so you can construct values for different automated periods. So, for example:\u00a0<\/p>\n46 10 * * 1 \/home\/concretedog\/backup_script.sh<\/code><\/pre>\n30 10 * * * \/home\/concretedog\/backup_script.sh<\/code><\/pre>\n![\"\"](\"https:\/\/www.raspberrypi.com\/app\/uploads\/2026\/09\/crontab_e-1024x576.png\")
Find more Raspberry Pi projects in\u00a0Raspberry Pi Official Magazine<\/em><\/h2>\n
![\"\"](\"https:\/\/www.raspberrypi.com\/app\/uploads\/2026\/08\/RPOM169-grey-flat-Large-1024x1024.jpeg\")
<\/figure>\n<\/div>\n