docs: add DeployHQ to third-party deployment providers (#9991) · jekyll/jekyll@7697d24
facundofaria
·
2026-06-23
·
via Recent Commits to jekyll:master
| Original file line number | Diff line number | Diff line change |
|---|
@@ -16,6 +16,12 @@ Read this [step-by-step guide](https://medium.com/@jameshamann/deploy-your-jekyl
|
16 | 16 | and update Jekyll websites. Take advantage of our global CDN, automated SSL, |
17 | 17 | continuous deployment and [more](https://cloudcannon.com/features/). |
18 | 18 | |
| 19 | +## DeployHQ |
| 20 | + |
| 21 | +[DeployHQ](https://www.deployhq.com) is a Git-based deployment service that builds your Jekyll site on its own infrastructure and transfers the rendered `_site/` directory to your own server over SSH, SFTP, FTP, or to cloud storage such as Amazon S3, Azure Blob Storage, or Rackspace Cloud Files. You connect a GitHub, GitLab, or Bitbucket repository, point each environment at a branch, and every push triggers a build. |
| 22 | + |
| 23 | +Build pipelines can run any shell command, so a typical Jekyll project runs `bundle install` followed by `bundle exec jekyll build` and ships the contents of `_site/` to your webroot. Each release is atomic, with one-click rollback, deploy hooks, and per-environment config-file injection — useful for keeping `_config.yml` overrides or `.env` values out of your repository. Multiple environments per project (for example staging and production mapped to different branches) are supported, and there is a free tier available at [deployhq.com/signup](https://www.deployhq.com/signup). |
| 24 | + |
19 | 25 | ## GitHub Pages |
20 | 26 | |
21 | 27 | 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](/docs/github-pages/). |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理,仅供阅读参考。 原文来自 — 版权归原作者所有。