Jekyll App Engine (jekyll-app-engine
) makes it easy to deploy your Jekyll static site to Google App Engine by generating your app.yaml
handlers.
Hosting your static site on Google App Engine gives you greater flexibility than using Github Pages and may potentially be cheaper and more configurable than Amazon AWS. Using Google App Engine allows:
Link: "</assets/style.css>; rel=preload; as=style,"
, andjekyll-assets
Using Google App Engine has some challenges:
These instructions assume you already have a Google App Engine account.
Add gem jekyll-app-engine
to your Gemfile
.
source 'https://rubygems.org'
gem 'github-pages'
gem 'jekyll-app-engine'
Add to your config.yml
.
gems:
- jekyll-app-engine
Specify a basic configuration in the file _app.yaml
or using the app_engine
option configurations to your Jekyll _config.yml
.
app_engine:
# Insert your configuration here or within _app.yaml
# You need to specify a runtime for App Engine
runtime: go
api_version: go1
default_expiration: 300s
App Engine expects all apps to have some sort of application.
Create a file called init.go
.
// Included to enable deployment to Google App Engine
package hello
import (
)
func init() {
}
You can put this anywhere, for example in a folder _app/init.go
to keep your root tidy.
Build your jekyll site, and you should notice the file app.yaml
in the output directory.
Before deploying you will need to move this file to the projects root directory, where your config.yml
file is located.
Automatic deployment using Travis: https://docs.travis-ci.com/user/deployment/google-app-engine
Manual deployment using the Google App Engine tools: todo
jekyll-app-engine can be configured by creating a file _app.yaml
in the source directory or by providing the configuration in the Jekyll config _config.yml
.
The handlers
option allows you to specify custom http headers and other feature supported by Google App Engine by Jekyll content type. The supported content types are:
posts
pages
collections
static
If you provide an Array or a url
option, the configuration for the content type will be inserted directly as a handler, instead of generating a handler per item within the content type.
Each document can specify overrides within the document's YAML frontmatter.