DashApps.app Migration

Updated Updated: October 8, 2026

DashApps.app Migration#

Create one Obsidian vault and one Hugo website for all apps. Start with a new DashApps landing page and copies of the GenDash and GPSDash content. Keep both existing websites live throughout the transition.

This is a plan; unchecked tasks have not been completed or verified. Proposed names and paths below can be adjusted before implementation.

1. Confirm the destination and record the starting point#

  • 1.1 Confirm the main domain: dashapps.app.
  • 1.2 Confirm the existing GenDash domain: gendash.app.
  • 1.3 Record the current GenDash and GPSDash setup from the actual systems; the September GPSDash scaffold note may no longer describe everything.
    • 1.3.1 Record each local vault path, current branch, and working-tree status.
    • 1.3.2 Record each vault’s GitHub repository, visibility, and default branch.
    • 1.3.3 Record each HP1Docker site folder and whether it is a Git checkout; record its remote if present.
    • 1.3.4 For each Cloudflare Pages project, record the project name, connected GitHub repository, production branch, build command, and output folder.
    • 1.3.5 For each app, verify the custom domain attached to its Pages project and record the public URL. Record any additional hostname or redirect configuration that affects the site.
    • 1.3.6 Record GenDash’s publishing scripts and schedules on the Mac and HP1Docker, including the times and host timezone.
    • 1.3.7 Record GPSDash’s publishing scripts and schedules on the Mac and HP1Docker; explicitly record when no scheduled job exists.

1.3 Starting-point inventory (checked 2026-10-08)#

Verified from the current local checkouts, publishing scripts, GitHub repository search, and read-only checks on HP1Docker (10.1.2.202):