Frameworks
Plain static sites on Stackap
A repository with an index.html at its root and no start script is served as a finished static site with no build step at all.
How Stackap recognizes a plain static site
After the framework tests, Stackap checks for an index.html at the repository root when there is no start script in package.json, or no package.json at all. A match is treated as a site that is already built. This is the path a hand-written site, an export from a design tool or a folder of generated files takes.
What Stackap builds
The generated image copies the whole repository into the web server's folder and then deletes the files that should not be public: the Stackap nginx configuration, the Dockerfile and the .dockerignore. Everything else you committed is served, so do not leave private files in the repository.
There is no build, so there is nothing to wait for and nothing that can fail on a missing dependency. This site is served by a similar nginx container, built from its own Dockerfile, with its pages generated by a script before they are committed.
Pages return real 404 responses, using a 404.html if you provide one.
What a a plain static site project needs
- An
index.htmlin the root of the repository. - No
startscript inpackage.json, or nopackage.json. - Nothing committed that you would not publish, because the whole repository is served.
- Relative or root-absolute links, since there is no router.
Verification status
Tested with a real Docker build of the plain-static image in the platform's tests, and live on the server with a toy project.
Still to verify: very large repositories, or sites with thousands of files.
Early-access scope
- The whole repository is public. A stray
.envor a source file will be served if it is committed. - Nothing runs on the server, so forms need an external service or a separate Node project.
- A
package.jsonwith astartscript sends the project down the Node path instead, even if an index.html exists. - No CDN.
Questions
How do I add a custom 404?
404.html in the root. The server uses it for missing paths.Can I add a build step later?
package.json with a build script and one of the supported tools, and detection will take the static-site path instead.Stackap is in early access. Tell us what you run and we will reply with a straight answer about whether it fits.
Ask for an invitationLast updated .