Hexo, Travis, S3 - Introduction
This series will guide you through all the steps needed from setting up your Hexo website to continuously deploying it on Amazon S3 using Travis CI.
- Part #1: Hexo Basics
- Part #2: Deploying to AWS
- Part #3: Deploying via Travis CI
- Part #4: Improve Performance
You might have heard of static site generators such as Jekyll or Middleman.
After fiddling around with some of them, I finally settled with Hexo which is build on Node.js.
EJS, and so on.
If you haven’t heard of Travis CI or Jenkins, you maybe never heard of continuous integration. Travis CI is a cloud based service which detects commits and pull requests on your GitHub based repository and performs predefined actions like building, testing and deploying your repository.
And guess what: It’s totally free for your open source projects hosted at GitHub!
Amazon S3 is a storage service for hosting static files. Since we use a static site generator for our website and don’t need any expensive computing power but only a service to serve our files, this is the AWS service we’re looking for.
Though, there are some downsides of using a static site generator over a CMS for blogging (e.g. there is no easy way to schedule posts) there are a lot of benefits:
- Speed: All your files are pre-rendered and only wait to be served.
- Cost: Since your files are pre-rendered, there is no expensive computing power needed to process requests.
- Security: There is no admin interface to hack - which is a pita on WordPress.
In the first part of this series, we’re going to set up our first Hexo website, get to know the basics and install a theme.