BETA — Static Site Hosting
With Kinsta’s Static Site Hosting, you can deploy static sites composed of non-dynamic files such as HTML, CSS, and JavaScript. Your repository can contain the pre-built files or the source code to generate your static site.
Git Service Providers
The first time you add a static site, you’ll need to select a Git service provider and repository from your account. You can choose from any (or all) of the following:
Once you’ve connected your GitHub account, you’ll be returned to MyKinsta to continue with the rest of the Add static site steps.
Limits
Static Site Hosting includes:
- 1 concurrent build per static site. If you initiate a build, you cannot initiate a new one until the previous one is complete.
- 100 static sites per company. Once you reach 100 static sites, you cannot create a new one unless you delete an existing site.
MyKinsta User Roles and Access for Static Sites
The following MyKinsta user roles can add, access, and manage static sites:
Important Notes and Troubleshooting
If you’re having any trouble deploying your static site, check out our troubleshooting guide. Here are some important things to keep in mind:
- Kinsta’s Static Site Hosting is for pre-built static sites or sites built with modern static site generator frameworks that use Node.js. If your site meets any of the following conditions, it will be better suited for our Application Hosting:
- It uses a language other than Node.js to build the site (e.g. PHP).
- It requires server-rendering to serve some or all of the site.
- It requires a database connection.
- It serves dynamic content.
- It requires sessions or authentication managed on the server-side.
- You’ll be asked to specify a Build command and Publish directory during the setup process. The Build command tells our system how to assemble your site, and the Publish directory is the subdirectory where the finished site files live, relative to the root of your repository. It’s crucial to fill out these fields correctly if your site depends on a build step. This will ensure your site is built and served as you intend. If the Build command is left blank, the system may indicate the deployment is complete, but it will only upload the unbuilt contents of your repository.
- If you’re deploying a pre-built site and your files are in a subdirectory of your repository, be sure you’ve entered the path to that subdirectory (where your HTML files and assets are stored) in the Publish directory field, relative to the root of your repository.
- The Build and rollout process log for each deployment can be viewed on the Deployment details page.
- If a site is deleted, depending on the caching headers sent by the site and the user’s browsers settings, the deleted site may still appear to be available for a few minutes or hours due to caching.
- A static site’s Display name must be unique; it cannot be the same as another static site, application, or WordPress site.