Sites
Configure builds
Choose a supported static build preset, output directory, and environment values for a Site.
Build configuration tells Qwibik Sites how to produce static files from a supported repository. Cloud validates the framework preset, root directory, output directory, and package script names.
Configure a build
- Open the Site and choose its source or build settings.
- Select the framework preset that matches the project: Vite, Astro static, Next.js static export, or Custom Node static build.
- Confirm the project root and static output directory.
- Select the package manager and build script offered by Cloud.
- Save and run a deployment.
Environment variables and secrets
Add environment variables and secrets only when your static build needs them. Keep sensitive values out of repository files and browser-exposed output. A static website can expose any value that is compiled into its public files.
Qwibik blocks publication when generated static files contain an exact configured build secret. This is a safety check, not a reason to place secrets in client-side code.
When a build fails
Review the failure message and sanitized build details in the deployment. Common issues include a missing lockfile, a failing build script, a missing output directory, invalid static output, a build timeout, or an unsupported dynamic feature.