Options
The Hosting settings allow you to use Forestry to handle deployment of your static site. Forestry can build your site and then deploy the static files to a hosting provider of your choice.
Guides
Forestry has a selection of built-in hosting options that make hosting your static site easy.
Commit to source repo only
Enabling “commit to source repo only” will enable Forestry to only commit changes made in the CMS back to the branch and repository your site was imported from.
Continuous Integration
Looking to deploy your site using a CI/CD tool like GitLab CI or BitBucket Pipelines? Use Commit to source repo only. This will trigger any CI/CD tool when a change is saved or published in Forestry.
GitHub Pages
Forestry can build your site and deploy the generated static files to a branch of a GitHub repository for use with GitHub Pages.
Amazon S3
Forestry can build your site and deploy the generated static files to an S3 bucket of your choosing.
There are two ways to host a static website with Amazon S3. S3 can be configured to host a website itself, or it can be used as an origin for AWS’ CloudFront CDN. Using S3 on its own is the simpler option, but using CloudFront is highly recommended.
If you’d like to know more about why you should use CloudFront with your S3 Bucket, check out this blog post from AWS.
Guides:
Setup an S3 + CloudFront Stack (Recommended)
Setup an S3 Bucket for Webhosting
Resources:
Amazon S3 + Amazon CloudFront: A Match Made in the Cloud (aws.amazon.com)
FTP/SFTP
Forestry can build your site and deploy the generated static files to any FTP/SFTP enabled web-server of your choosing.
Other Options
In addition to the built-in hosting provider options provided by Forestry, we provide tutorials for using third-party services with Forestry.
GitHub Pages Jekyll Integration
If you are using Jekyll as your static site generator, GitHub pages can handle building your static site without the support of Forestry or a CI tool.
Resources
GitLab Pages & GitLab CI
GitLab provides a free CI tool for triggering build and deployment scripts when commits are made to your repository, and has example projects for both Hugo and Jekyll.
Resources
- GitLab Pages
- GoHugo.io: Host on GitLab
- GitLab.com: Hugo Example Project
- GitLab.com: Jekyll Example Project
BitBucket Pipelines
BitBucket provides a CI tool for triggering build and deployment scripts when commits are made to your repository.
Resources
- BitBucket Pipelines Documentation
- Bitquobit.com: Automating Hugo Deployments with BitBucket Pipelines
Webhooks
Forestry has outgoing webhooks that can be used to trigger custom build scripts.
GitHub, BitBucket, and GitLab also provide support for outgoing webhooks to trigger a custom build script.
Caught a mistake or want to contribute to the docs? Edit this page on Github!