Nextpertise a journal of interesting technical ideas . . .

Automaticly adding Hugo articles to Obsidian

by Brent Stewart on Monday, Mar 13, 2023

Incorporating blog articles in Obsidian

Most of my writing occurs in two places, but I’d like to consolidate it into my “second brain”.

My blog articles are written in Visual Studio Code, in markdown so that they can be compiled via hugo. I’ve discussed in this blog that Obsidian - also in Markdown - is setup as my “second brain”. My blog posts represent an important part of that “second brain”, so I’d like to make sure they’re included in my vault. Since both are markdown, this should be fairly simple. This should just require that I copy my hugo content directory into my obsidian directory. To test this, I made a quick script.

cp ~/git/nextpertise/content/posts/*.md ~/2nd\ Brain/Nextpertise/
echo " ran"

I also made this file executable.

chmod +x

This works as expected. The markdown files are copied from my hugo git directory into my Obsidian vault under the “Nextpertise” folder. Obsidian actually updates dynamically as soon as the files are present. There are some issues - my website has a directory for graphics that I’m not copying over, for instance, and the internal linking and tagging I expect in Obsidian wouldn’t be present in these files. External links in the posts seem to work as expected though. All I need to do is remember to run this occassionally . . .


So the next step was to have this run as a cron job. On Linux, use crontab -e to setup the job. Below is the way I have this setup and working.

0 0 * * * /home/brent/

It works! The five variables before the job are minute, hour, day, month, and day of the week. So my entry is to run at 00 minutes and 0 hour (midnight) every day. Cron defaults to outputting to system mail, but I use the MAILTO entry and SSMTP to redirect this to a public email address. For more information on how to set this up see my last post.

The received email is on the right, and now it’s clear why the echo command is in the batch file. The echo provides some text - without that text there’s no output from the script and nothing to email.

There are some possible improvements that might make this worth revisiting in the future. The simple script doesn’t indicate if there was an error copying the files. I could also imagine inserting links and tags that are used in my Obsidian vault as a header to the imported files. However, this is a straight-forward process and it’s meeting my immediate need.


Recent articles related to these tags:
markdown linux shell Hugo obsidian
Share this article: