WIP: pending changes — docs, webhook, nav/footer (committed per Sami request, not yet reviewed)

This commit is contained in:
Krystie
2026-06-13 21:29:36 -07:00
parent 69c2179a43
commit 3b2023e97a
19 changed files with 7584 additions and 7717 deletions
+53
View File
@@ -0,0 +1,53 @@
import Navbar from '@/components/Navbar';
import Footer from '@/components/Footer';
import DocsLayout from '@/components/docs/DocsLayout';
export default function DocsInstallationPage() {
return (
<div className="flex min-h-screen flex-col bg-surface-950 text-surface-50">
<Navbar />
<DocsLayout
title="Installation Guide"
intro="DashCaddy supports both guided installation and manual operator-controlled setup. This guide covers the dependencies and the two practical setup paths."
>
<h2>Prerequisites</h2>
<ul>
<li>Docker and Docker Compose</li>
<li>Caddy with Admin API access</li>
<li>Node.js 18+ for the API server</li>
<li>Technitium DNS if you want DNS automation</li>
</ul>
<h2>Installer-based setup</h2>
<p>
DashCaddy includes a dedicated installer intended to walk users through dependency checks, file deployment,
configuration generation, and first launch.
</p>
<h2>Manual setup</h2>
<p>
Manual setup is best when you want direct control over paths, services, Caddy, DNS integration, and deployment layout.
</p>
<ol>
<li>Clone the software repo.</li>
<li>Install the API dependencies.</li>
<li>Prepare Caddy and confirm the Admin API is reachable.</li>
<li>Prepare Technitium DNS if using automatic DNS changes.</li>
<li>Configure environment and state paths.</li>
<li>Start the DashCaddy API.</li>
<li>Serve the dashboard through Caddy.</li>
</ol>
<h2>Post-install checks</h2>
<ul>
<li>Dashboard loads in browser</li>
<li>API responds correctly</li>
<li>Caddy Admin API is reachable</li>
<li>Service management UI loads</li>
<li>DNS/certificate integration is healthy if configured</li>
</ul>
</DocsLayout>
<Footer />
</div>
);
}