4fbbefeb7e
* spelling: always Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: apostrophe Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: articles Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: bajillion Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: bandwidth Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: compatibilize Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: congratulations Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: consistent Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: containing Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: correspondents Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: debuggability Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: definitions Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: engine Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: expectations Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: framework Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: gallery Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: github Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: gitlab Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: hesitant Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: hesitate Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: highlighter Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: installation Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: internal Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: kramdown Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: link Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: markdown Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: markdownify Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: metadata Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: multiple Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: object Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: overridden Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: paths Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: positions Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: powershell Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: proceeding Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: pygments settings Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: referencing Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: retrieve Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: separating Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: several Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: specific Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: suppress Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: upgrading Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: variable Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: variables Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: whitespace Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: with Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> Co-authored-by: Josh Soref <jsoref@users.noreply.github.com>
4.9 KiB
title, permalink
| title | permalink |
|---|---|
| 3rd Party | /docs/deployment/third-party/ |
Aerobatic
Aerobatic has custom domains, global CDN distribution, basic auth, CORS proxying, and a growing list of plugins all included.
Automating the deployment of a Jekyll site is simple. See their Jekyll docs for more details. Your built _site folder is deployed to their highly-available, globally distributed hosting service.
AWS Amplify
The AWS Amplify Console provides continuous deployment and hosting for modern web apps (single page apps and static site generators). Continuous deployment allows developers to deploy updates to their web app on every code commit to their Git repository. Hosting includes features such as globally available CDNs, 1-click custom domain setup + HTTPS, feature branch deployments, redirects, trailing slashes, and password protection.
Read this step-by-step guide to deploy and host your Jekyll site on AWS Amplify.
Bip
Bip provides zero downtime deployment, a global CDN, SSL, unlimited bandwidth and more for Jekyll websites. Deploy in seconds from the command line. Visit the Bip website for more information - which is also built with Jekyll.
CloudCannon
CloudCannon has everything you need to build, host and update Jekyll websites. Take advantage of our global CDN, automated SSL, continuous deployment and more.
GitHub Pages
Sites on GitHub Pages are powered by Jekyll behind the scenes, so if you’re looking for a zero-hassle, zero-cost solution, GitHub Pages are a great way to host your Jekyll-powered website for free.
GitLab Pages
GitLab Pages offers free hosting with custom domains. Get started with Jekyll and a fully customizable pipeline.
KeyCDN
KeyCDN accelerates Jekyll-powered websites with a wide range of other features such as real time image processing including WebP transformation.
The Jekyll hosting tutorial provides various options to supercharge Jekyll sites with just a few steps. It combines best flexibility and excellent performance.
Kickster
Use Kickster for automated deploys to GitHub Pages when using unsupported plugins on GitHub Pages.
Kickster provides a basic Jekyll project setup packed with web best practises and useful optimization tools increasing your overall project quality. Kickster ships with automated and worry-free deployment scripts for GitHub Pages.
Install the Kickster gem and you are good to go. More documentation can here found here. If you do not want to use the gem or start a new project you can just copy paste the deployment scripts for Travis CI or Circle CI.
Netlify
Netlify provides Global CDN, Continuous Deployment, one click HTTPS and much more, providing developers a robust toolset for modern web projects, without added complexity. Netlify supports custom plugins for Jekyll and has a free plan for open source projects.
Read this Jekyll step-by-step guide to setup your Jekyll site on Netlify.
Render
Render provides zero config continuous deployment for static sites. The service is free under 100GB monthly bandwidth.
Static Publisher
Static Publisher is another automated deployment option with a server listening for webhook posts, though it's not tied to GitHub specifically. It has a one-click deploy to Heroku, it can watch multiple projects from one server, it has an easy to user admin interface and can publish to either S3 or to a git repository (e.g. gh-pages).
Vercel
Vercel provides zero config continuous deployment, HTTPS Custom domains, high performance smart CDN, you get instant static deploy for free.
21YunBox
21YunBox provides blazing fast Chinese CDN, Continuous Deployment, one click HTTPS and much more, providing developers a hassle-free solution to launch their web projects in China.
Read this Jekyll step-by-step guide to deploy your Jekyll site on 21YunBox.