Proposal
I'd like to add a deployment guide for DeployHQ to src/routes/(2)guides/(1)deployment-options/, mirroring the format of the existing stormkit.mdx, zerops.mdx, and railway.mdx pages.
Why DeployHQ fits this collection
DeployHQ is a Git-based deployment platform that builds your SolidStart app on its build servers and ships the .output/ directory to a server you own over SSH/SFTP/FTP — or to Amazon S3, Azure Blob, or Rackspace Cloud Files. The current entries in deployment-options/ cover managed platforms (Vercel, Netlify, Cloudflare, Firebase, Railway, Stormkit, Zerops) and AWS-via-IaC patterns (Flightcontrol, SST). There isn't currently an entry that walks a reader through "Git-driven deploys to my own VPS", which is a common workflow for agencies and small teams that already run their own infrastructure.
Scope
- One new file:
src/routes/(2)guides/(1)deployment-options/deployhq.mdx
- ~345 words, structured like
stormkit.mdx: short intro, prerequisites, numbered setup steps, link out to the DeployHQ docs
- Build command pattern:
npm install + npm run build (Vinxi/Nitro), Node preset start with node .output/server/index.mjs
- No images, no
solid-start/ sub-routing — the existing deployment-options/ route is shared between Solid and SolidStart, so the new page follows that convention
- No changes to other files (no TOC update needed; the directory is auto-discovered)
Checking first per CONTRIBUTING
The CONTRIBUTING guide notes that unsolicited material may not fit into existing plans, so I wanted to check that this contribution would be welcomed before opening a PR. Happy to scope down, restructure, or move it to a Discussion instead if that's preferred.
I have a draft ready to push as a PR if this is green-lit. Thanks!
Proposal
I'd like to add a deployment guide for DeployHQ to
src/routes/(2)guides/(1)deployment-options/, mirroring the format of the existingstormkit.mdx,zerops.mdx, andrailway.mdxpages.Why DeployHQ fits this collection
DeployHQ is a Git-based deployment platform that builds your SolidStart app on its build servers and ships the
.output/directory to a server you own over SSH/SFTP/FTP — or to Amazon S3, Azure Blob, or Rackspace Cloud Files. The current entries indeployment-options/cover managed platforms (Vercel, Netlify, Cloudflare, Firebase, Railway, Stormkit, Zerops) and AWS-via-IaC patterns (Flightcontrol, SST). There isn't currently an entry that walks a reader through "Git-driven deploys to my own VPS", which is a common workflow for agencies and small teams that already run their own infrastructure.Scope
src/routes/(2)guides/(1)deployment-options/deployhq.mdxstormkit.mdx: short intro, prerequisites, numbered setup steps, link out to the DeployHQ docsnpm install+npm run build(Vinxi/Nitro), Node preset start withnode .output/server/index.mjssolid-start/sub-routing — the existingdeployment-options/route is shared between Solid and SolidStart, so the new page follows that conventionChecking first per CONTRIBUTING
The CONTRIBUTING guide notes that unsolicited material may not fit into existing plans, so I wanted to check that this contribution would be welcomed before opening a PR. Happy to scope down, restructure, or move it to a Discussion instead if that's preferred.
I have a draft ready to push as a PR if this is green-lit. Thanks!