Jekyll Cache Saving the Day
December 17, 2024
I was in the midst of publishing a post on announcing that QNX released a non-commercial license which allows hobbyist to fiddle around
but I accidentally deleted my file using the cp
command. This effectively killed my mood as I did not want to rewrite everything
from scratch. I then recall that Jekyll creates a cache to speed up the build process when converting markdown to HTML.
$ ls -ld .?* drwxr-xr-x. 1 zaku zaku 204 Dec 16 23:47 .git -rw-r--r--. 1 zaku zaku 0 Oct 20 19:55 .gitignore drwxr-xr-x. 1 zaku zaku 32 Oct 20 19:56 .jekyll-cache
If we were to traverse into the cache and into Jekyll-Converters--Markdown
, you’ll see a lot of directories labelled what it appears to be in hex:
.jekyll-cache/Jekyll/Cache/Jekyll--Converters--Markdown$ ls 0e 1c 22 24 2e 37 3f 44 47 53 57 5d 62 66 6e 74 7b 84 8d 90 91 9c a7 a9 aa ab b1 b3 b6 c1 c6 cb d4 d5 e1 e2 ea f9 fc
Using my trust tool grep
, I was able to patch up pieces of my work. However, as the purpose of Jekyll-Converters--Markdown
is to
cache markdown files that have been converted to HTML, I obviously had to clean it up a bit but regardless, it was much faster than
to rewrite the entire article.