sitesolide Client Pilot Deployment (Onboarding)

sitesolide Client Pilot Deployment (Onboarding)

1. 01

   Confirm the client-owned Debian 13 server and Cloudflare domain are provisioned

   Verify root or sudo access on the Debian 13 host and that the DNS zone is active in Cloudflare before installing anything. Record the server IP and domain in the client's delivery folder so the runbook stays reproducible.

2. 02

   Install the sitesolide single-binary CLI on the server

   Place the binary on the host and confirm it runs. This is the only install step; there is no Docker daemon or container runtime to configure, which keeps the client's patch surface small.

3. 03

   Deploy a static site and one Bun or Node app to validate routing

   Run `sitesolide deploy` in each project folder. Confirm HTTPS terminates correctly through Caddy, each app lands on its own subdomain, and a systemd service was created and is running. Do this before the client sees anything.

4. 04

   Connect company sign-in for the pilot app

   Wire Google Workspace, Microsoft Entra, Okta, or a generic OpenID Connect provider so the client's private dashboard sits behind their own identity provider. Test with a real client account, not a test alias.

5. 05

   Set per-app sharing and scoped team tokens

   Add sharing by email or domain for the specific people who need access, then issue scoped, revocable tokens for each team member who will deploy. Avoid a shared token; revocation is the whole point.

6. 06

   Declare workers and scheduled jobs in sitesolide.json

   If the pilot app needs background workers or cron-style jobs, declare them in sitesolide.json so they survive restarts. Confirm the jobs appear and run after a redeploy.

7. 07

   Verify hourly backups and minute-level monitoring are live

   Trigger a manual backup and restore it to a scratch path to prove the backup is usable. Check the monitoring view reports the app as healthy, then screenshot both for the client handoff pack.

8. 08

   Hand off the runbook and train the client on CLI operations

   Walk the client through `sitesolide deploy`, reading logs, and verifying a backup. Leave them the runbook covering token rotation and the SSO provider config so they are not dependent on your agency for routine deploys.