Deploy a Jekyll Site for Free with GitHub Actions and Static Site Hosting from Kinsta
Posted: Mon Feb 10, 2025 10:45 am
here are different ways to deploy your Jekyll website at Kinsta, for example:
You use application hosting from Kinsta .
You use Kinsta's static site hosting via any of these methods:
A. Building your website with Continuous Integration and Continuous Deployment (CI/CD) before deploying it to Kinsta.
B. Serving only your static files .
In this article, we'll walk you through both methods of deploying Jekyll with Kinsta's static site hosting.
A. Build Your Website with GitHub Actions Before Deploying on Kinsta
This method uses a GitHub Actions (GHA) workflow to build your website on a specific branch ( deploy) and use this branch to deploy the generated static files to Kinsta.
To use this method, since we're using GitHub Actions, your codebase brazil whatsapp number data must be hosted in a GitHub repository (public or private). But you can use other CI/CD tools to achieve the same result.
The most significant advantages of this method are
You can implement further Continuous Integration (CI) processes for your site, for example a phase testand/or a phase lintto check your code.
Your site is automatically built on every push to your repository. You don't need to build it before pushing it.
Ensures that your website is only updated if the CI/CD pipeline completes successfully.
Steps:
Open your terminal in the root of your Jekyll site repository.
Create a new orphan (empty) branch ( deploy) and push it to your repository:
git switch --orphan deploy
git commit --allow-empty -m "Initial commit on deploy branch"
git push -u origin deploy
Do not add any files to this branch. It will be automatically populated by the GitHub Actions workflow with the contents of the generated Jekyll _site folder.
Check the branch main:
git checkout main
Create a .github/workflows directory in main.
To configure GHA, create a new gh-actions.yml file in .github/workflows with the following content:
You use application hosting from Kinsta .
You use Kinsta's static site hosting via any of these methods:
A. Building your website with Continuous Integration and Continuous Deployment (CI/CD) before deploying it to Kinsta.
B. Serving only your static files .
In this article, we'll walk you through both methods of deploying Jekyll with Kinsta's static site hosting.
A. Build Your Website with GitHub Actions Before Deploying on Kinsta
This method uses a GitHub Actions (GHA) workflow to build your website on a specific branch ( deploy) and use this branch to deploy the generated static files to Kinsta.
To use this method, since we're using GitHub Actions, your codebase brazil whatsapp number data must be hosted in a GitHub repository (public or private). But you can use other CI/CD tools to achieve the same result.
The most significant advantages of this method are
You can implement further Continuous Integration (CI) processes for your site, for example a phase testand/or a phase lintto check your code.
Your site is automatically built on every push to your repository. You don't need to build it before pushing it.
Ensures that your website is only updated if the CI/CD pipeline completes successfully.
Steps:
Open your terminal in the root of your Jekyll site repository.
Create a new orphan (empty) branch ( deploy) and push it to your repository:
git switch --orphan deploy
git commit --allow-empty -m "Initial commit on deploy branch"
git push -u origin deploy
Do not add any files to this branch. It will be automatically populated by the GitHub Actions workflow with the contents of the generated Jekyll _site folder.
Check the branch main:
git checkout main
Create a .github/workflows directory in main.
To configure GHA, create a new gh-actions.yml file in .github/workflows with the following content: