Hugo file GenDash: Obsidian to Hugo Automated Publishing Guide

This guide outlines the infrastructure and configuration required to sync an Obsidian vault across multiple devices and automate the publishing process to a Hugo website via Cloudflare Pages.

1. Multi-Device Sync (The Git & Web Layer)#

To sync your notes between computers and view them on mobile devices without the overhead of real-time database sync engines:

1.1. Between Computers (Mac Studio & MacBook Pro/Air)#

We use the Obsidian Git plugin to synchronize GenDash vaults directly via GitHub.

Markdown Reference Guide for Obsidian#

1. View Modes (Why you can’t see the code)#

Obsidian has two main ways of displaying notes. If you see the “formatted” version (like a clickable checkbox), you are in Live Preview.

• Toggle Code View: Press Cmd + E to switch between Editing and Reading modes.
• Source Mode: To see the “raw” characters (like - [ ]) all the time, go to the status bar at the bottom right and select Source Mode.
• Temporary Reveal: If you click directly on a formatted item (like a checkbox), Obsidian will temporarily reveal the code for just that line.

1. Headers#

Use # followed by a space. The number of # symbols indicates the header level.

1 Core Obsidian Shortcuts#

These are the most essential keys for building your homelab documentation rapidly.

2 Linking to Headings with Wikilinks Disabled#

Since we switched to Standard Markdown Links, use these to keep the “network” alive.

Homelab: Obsidian to Hugo Automated Publishing Guide#

This guide outlines the infrastructure and configuration required to sync an Obsidian vault across multiple devices and automate the publishing process to a Hugo website via Cloudflare Pages.

1. Multi-Device Sync (The Git & Web Layer)#

To sync your notes between computers and view them on mobile devices without the overhead of real-time database sync engines:

1.1. Between Computers (Mac Studio & MacBook Pro/Air)#

We use the Obsidian Git plugin to synchronize vaults directly via GitHub.

1. Pangolin Pre-Update Requirements#

1.1. Backup Data#

Always backup your data before updating. Copy your config directory to a safe location to allow for a rollback if necessary.

1.2. Version Strategy#

Update incrementally between major versions (e.g., 1.0.0 → 1.1.0 → 1.2.0) rather than skipping major releases.

2. Update Process#

2.1. Stop the Stack#

Stop all running containers:

sudo docker compose down

2.2. Check Latest Versions#

Before editing your configuration, verify the current stable release versions for each component: