My Config-Generating Justfile : Random Geekery

Using Yarner to tangle the file that drives the whole process? I should be ashamed of myself. I’m not, but I feel like I should be.

Building everything with Yarner

I let Yarner do its thing. Then I copy my newly generated justfile and dotbot configs to the project root, making sure to back up the current copies. If I screw up, I can always go to the backup. If I screw up bad, I can always go back to Git history. If I screw up real bad, I have another computer.

build:
  yarner
  cp -b code/justfile ./
  cp -b code/install.conf.yaml ./

Installing my configs with dotbot

Invoke dotbot to link with files and directories.

install:
  ./install -v

Publish to my Hugo site

Add the Markdown that Yarner produced to my site config section. There’s some post-processing I want to do as well. We’ll get there.

publish:
  cp -Rv docs/* ~/Sites/rgb-hugo/content/config

Cleaning

Remove the build artifacts if they exist. Better be careful about running this, as it will confuse Dotbot.

clean:
  [ -d code ] && rm -r code
  [ -d docs ] && rm -r docs

Anything else?

I need some kind of test process, but better think about what that would look like before I try.

Backlinks

Config