Skip to main content

Deploy a Static Site

QuikDB Compute supports plain HTML, CSS and browser-side JavaScript sites without requiring a Node.js server or build command. You can deploy a static site from a connected GitHub repository, a .tar.gz archive or a .zip archive.

Prepare the source​

Place index.html at the selected source root. Keep CSS, JavaScript, images and other pages in normal relative directories, for example:

index.html
styles.css
assets/
  logo.svg
pages/
  about.html

Do not include credentials, .env files, database exports, private keys or server source that should not be public. Static files are delivered to site visitors.

Deploy from GitHub​

  1. Open QuikDB Compute and connect GitHub.
  2. Select the repository, branch and optional service directory containing index.html.
  3. Choose Static Site when reviewing the detected configuration.
  4. Review route behaviour, then deploy.

GitHub connection state is durable across QuikDB API replicas. Authorize only the repositories that QuikDB should read.

Deploy an archive​

  1. Choose Deploy an application archive in Compute.
  2. Select a .tar.gz or .zip file no larger than 64 MiB.
  3. Choose Static Site, review route behaviour, then deploy.

The filename and archive signature must agree. QuikDB rejects malformed archives, path traversal, absolute paths, links, special files, duplicate or conflicting paths, excessive entry counts, oversized content and expansion bombs. Do not rename another file type to .zip or .tar.gz.

Choose route behaviour​

Static sites are multi-page by default. A missing path returns HTTP 404.

Enable Single-page app route fallback only for a browser-routed SPA that should receive index.html for otherwise missing paths. Leave it disabled for ordinary multi-page sites so broken links remain visible.

Runtime behaviour​

QuikDB serves the selected files with a managed non-root nginx runtime on port 8080. It preserves common content types, applies separate HTML and asset cache behaviour, disables directory listing and blocks sensitive configuration and server-source paths. Managed static mode does not accept a custom nginx configuration; use an application-owned Dockerfile when you need a custom server.

After deployment reaches live, open the QuikDB URL and verify the page, styles, assets and any client-side routes. Deleting the final deployment that uses an uploaded archive also releases that owner-bound upload; an archive still used by another deployment is retained.

For deployment states and troubleshooting, read Deploying Your App.