New /docs/desktop-app: download table with per-platform filenames, SHA256
verification vs published SHA256SUMS.txt (end-anchored grep, tested against
the real manifest format), honest unsigned-app framing (limited same-origin
integrity check, NOT a safety guarantee), SmartScreen/Gatekeeper explained as
identity+notarization+reputation signals, full macOS Open Anyway flow,
troubleshooting table. Registered in DocsLayout sidebar + /docs index.
2026-09-23 01:09:01 -07:00
5 changed files with 255 additions and 4 deletions
intro="DashCaddy also ships as a native desktop app — the same dashboard you know from the browser, running in its own window with its own taskbar icon. This guide covers downloading and installing it on Windows and macOS, including the one-time security prompts both operating systems show for new software."
# compare the hash to the matching line in SHA256SUMS.txt`}</code></pre>
<p>
If a hash doesn't match, don't run the file — re-download it first, and if it still mismatches,
don't assume your machine is at fault: the published manifest itself could be stale or wrong. Report it
instead.
</p>
<h2>Install on Windows</h2>
<ol>
<li>Download <code>dashcaddy-installer-win-x64.exe</code> and run it.</li>
<li>
If Windows shows <strong>“Windows protected your PC”</strong> (blue SmartScreen), click{''}
<strong>More info</strong>, then <strong>Run anyway</strong>. See{''}
<a href="#unsigned" className="text-brand-400 hover:text-brand-300 underline">Why the security warning?</a>{''}
below.
</li>
<li>Follow the setup wizard (choose install location — defaults are fine).</li>
<li>Launch DashCaddy from the Start Menu or desktop shortcut.</li>
</ol>
<h2>Install on macOS</h2>
<h3>From the DMG (recommended, Apple Silicon)</h3>
<ol>
<li>Download <code>dashcaddy-installer-mac.dmg</code> and double-click to mount it.</li>
<li>Drag <strong>DashCaddy Installer</strong> into the <strong>Applications</strong> folder shortcut.</li>
<li>Eject the disk image, then launch DashCaddy from Applications.</li>
</ol>
<h3>From the ZIP (any Mac)</h3>
<ol>
<li>Download and unzip the file for your Mac (<code>-arm64.zip</code> for Apple Silicon,{''}
<code>-x64.zip</code> for Intel).</li>
<li>Drag <strong>DashCaddy Installer.app</strong> into your Applications folder.</li>
<li>Launch it from Applications.</li>
</ol>
<h3 id="first-launch-mac">First launch on macOS</h3>
<p>
Because the app isn't notarized yet, macOS Gatekeeper will stop it the first time. That's a
one-time step — macOS remembers your choice:
</p>
<ol>
<li>Try to open the app. You'll see a dialog saying the app can't be verified — click <strong>Cancel</strong> (don't drag it to Trash).</li>
<li>
<strong>Right-click</strong> (or Control-click) the app in Applications and choose <strong>Open</strong>,
then click <strong>Open</strong> again in the confirmation dialog. macOS now allows the app and opens it
normally from now on.
</li>
</ol>
<p>
On newer macOS versions the right-click route may be hidden. Instead:{''}
<strong>System Settings → Privacy & Security</strong>, scroll to the <strong>Security</strong> section,
find the message saying <em>“DashCaddy Installer was blocked”</em>, click{''}
<strong>Open Anyway</strong>, authenticate with your password or Touch ID, then click <strong>Open</strong> in
the final confirmation dialog.
</p>
<h2 id="unsigned">Why the security warning?</h2>
<p>
Windows SmartScreen and macOS Gatekeeper aren't a single check — they combine developer-identity
requirements (on Windows, a paid code-signing certificate; on macOS, Developer ID signing{''}
<em>plus</em> Apple's notarization scan — the ticket Apple attaches isn't itself a signature,
it's Apple's verdict that the signed app passed a malware check) with reputation and other
security signals. DashCaddy currently has none of these, so the OS treats it as <em>unverified</em>.
</p>
<p>
<strong>Unverified is not the same as malicious</strong> — plenty of legitimate open-source software ships
unsigned — but it does mean the OS's automated vetting doesn't apply to it.
</p>
<p>
Verifying the SHA256 checksum against the published manifest gives you a <strong>limited integrity
check</strong>: it confirms the file you downloaded matches, byte for byte, what the release server published
— so it detects a truncated or corrupted download, or tampering in transit. It does <strong>not</strong>{''}
prove the software itself is safe: the manifest lives on the same server as the binaries, so a compromised
server could replace both. Checksum comparison is a useful habit, not a substitute for code signing — and
signing/notarization is exactly what's on the roadmap to close that gap. In the meantime:
</p>
<ol>
<li>
<strong>Download only from <code>get.dashcaddy.net</code></strong> (HTTPS) — not from mirrors, chat links,
or third-party sites.
</li>
<li>
<strong>Verify the SHA256 checksum</strong> using the steps above, and treat a mismatch as a file you
should never run. Note that a persistent mismatch across fresh downloads can also mean the published
manifest itself is stale or wrong — either way, don't run the file; report it instead.
</li>
</ol>
<p>
What fixes the warnings takes more than a certificate, and differs by platform: on <strong>macOS</strong>,
Developer ID signing <em>plus</em> notarization makes Gatekeeper open the app normally. On{''}
<strong>Windows</strong>, code signing removes the unidentified-publisher state, but SmartScreen can still
warn until the binary builds up download reputation over time. Both are on the roadmap.
</p>
<h2>Connect the app to your server</h2>
<ol>
<li>
When the app opens, enter your DashCaddy URL — the same address you use in the browser (for example{''}
<code>https://dashcaddy.example.com</code>).
</li>
<li>Log in with your usual credentials and TOTP code.</li>
<li>
You're in — the app renders the identical dashboard, and your session stays signed in between launches.
</li>
</ol>
<p>
The app needs to reach the same hostname as your browser. If you use a custom TLD (like{''}
<code>dashcaddy.home</code>), make sure the machine running the desktop app also has DashCaddy's root
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.