Owning your music (collection)...

...without losing your mind, part 2

(part 1 here)

Now that we have a way to get our music and our player(s) picked out, let’s come up with an easy to use workflow and an organisatonial structure that works for us. It’s going to be a lengthy one, so let’s just get started.

Here’s the gist of the workflow:

flowchart TD


cd((CDs))
cd-- dBPoweramp CD Ripper -->flac

bandcamp@{ shape: cloud }
bandcamp-->flac

subgraph TrueNas
  direction TD
  flac@{ shape: documents, label: "/flac_music" }
  opus@{ shape: documents, label: "/opus_music" }
  mp3@{ shape: documents, label: "/mp3_music" }
  plex@{ shape: "lin-rect", label: "PLEX server" }
  flac-. lossifier-opus .->opus
  flac-. lossifier-mp3 .->mp3
  flac===plex
end

rb@{ shape: card, label: "rockbox DAP"}
android@{ shape: card, label: "Android DAP"}
snow@{ shape: card, label: "snowsky DAP"}
laptop@{ shape: card, label: "laptop"}

opus-- rclone -->rb
mp3-- rclone -->snow
opus-. autosync .->android
plex-->laptop
plex-->android

flowchart TD

subgraph legend [Legend]
  direction TD
  style legend fill:none
  smb@{ shape: documents, label: "SMB share" }
  docker@{ shape: "lin-rect", label: "docker service" }
  dap@{ shape: card, label: "player hardware"}
  Com@{ shape: braces, label: "dotted arrows run\n on a schedule" }
end

As you can see

read more

---

Srcery cheat sheet

This should already be up somewhere

Srcery color scheme is awesome, but it’s not nearly as popular as some of the other ones. So if you adopted it as your main color scheme, you sometimes gotta do some legwork to make your devenv consistent.

So since I’m adopting Zellij, I sort of had to make this cheat sheet:

type	name	full name	color
primary	black	srcery-palette-primary-black
primary	red	srcery-palette-primary-red
primary	green	srcery-palette-primary-green
primary	yellow	srcery-palette-primary-yellow
primary	blue	srcery-palette-primary-blue
primary	magenta	srcery-palette-primary-magenta
primary	cyan	srcery-palette-primary-cyan
primary	white	srcery-palette-primary-white
primary	bright-black	srcery-palette-primary-bright-black
primary	bright-red	srcery-palette-primary-bright-red
primary	bright-green	srcery-palette-primary-bright-green
primary	bright-yellow	srcery-palette-primary-bright-yellow
primary	bright-blue	srcery-palette-primary-bright-blue
primary	bright-magenta	srcery-palette-primary-bright-magenta
primary	bright-cyan	srcery-palette-primary-bright-cyan
primary	bright-white	srcery-palette-primary-bright-white
secondary	orange	srcery-palette-secondary-orange
secondary	bright-orange	srcery-palette-secondary-bright-orange
secondary	hard-black	srcery-palette-secondary-hard-black
secondary	teal	srcery-palette-secondary-teal
secondary	xgray1	srcery-palette-secondary-xgray1
secondary	xgray2	srcery-palette-secondary-xgray2
secondary	xgray3	srcery-palette-secondary-xgray3
secondary	xgray4	srcery-palette-secondary-xgray4
secondary	xgray5	srcery-palette-secondary-xgray5
secondary	xgray6	srcery-palette-secondary-xgray6
secondary	xgray7	srcery-palette-secondary-xgray7
secondary	xgray8	srcery-palette-secondary-xgray8
secondary	xgray9	srcery-palette-secondary-xgray9
secondary	xgray10	srcery-palette-secondary-xgray10
secondary	xgray11	srcery-palette-secondary-xgray11
secondary	xgray12	srcery-palette-secondary-xgray12

---

Fixing Cloudflare 523 errors

(when using Cloudflare Tunnels)

For some context: Recently I’ve been sharpening my Kubernetes skills by setting up a small 6 node k3s cluster at home. The place I currently live doesn’t have a public IP address, so I chose to set up a Cloudflare Tunnel to expose services to the internet.

I chose to have the cloudflared daemon running on the host machines and the overall setup quick and pain-free. The whole thing seemed to work well, but I noticed that over time (within hours) the tunneled services would start responding more slowly and eventually Cloudflare would display 523 errors.

read more

---

• Older Posts →