Middleware for Caddy.
git clones a git repository into the site. This makes it possible to deploy your site with a simple git push.
The git directive starts a service routine that runs during the lifetime of the server. When the service starts, it clones the repository. While the server is still up, it pulls the latest every so often. You can also set up a webhook to pull immediately after a push. In regular git fashion, a pull only includes changes, so it is very efficient.
If a pull fails, the service will retry up to three times. If the pull was not successful by then, it won't try again until the next interval.
Requirements: This directive requires git to be installed. Also, private repositories may only be accessed from Linux or Mac systems. (Contributions are welcome that make private repositories work on Windows.)
git repo [path]
- repo is the URL to the repository; SSH and HTTPS URLs are supported
- path is the path, relative to site root, to clone the repository into; default is site root
This simplified syntax pulls from master every 3600 seconds (1 hour) and only works for public repositories.
For more control or to use a private repository, use the following syntax:
git [repo path] {
repo repo
path path
branch branch
key key
interval interval
clone_args args
pull_args args
hook path secret
hook_type type
then command [args...]
then_long command [args...]
}
- repo is the URL to the repository; SSH and HTTPS URLs are supported.
- path is the path to clone the repository into; default is site root. It can be absolute or relative (to site root).
- branch is the branch or tag to pull; default is master branch.
{latest}
is a placeholder for latest tag which ensures the most recent tag is always pulled. - key is the path to the SSH private key; only required for private repositories.
- interval is the number of seconds between pulls; default is 3600 (1 hour), minimum 5. An interval of -1 disables periodic pull.
- clone_args is the additional cli args to pass to
git clone
e.g.--depth=1
.git clone
is called when the source is being fetched the first time. - pull_args is the additional cli args to pass to
git pull
e.g.-s recursive -X theirs
.git pull
is used when the source is being updated. - path and secret are used to create a webhook which pulls the latest right after a push. This is limited to the supported webhooks. secret is currently supported for GitHub, Gitlab and Travis hooks only.
- type is webhook type to use. The webhook type is auto detected by default but it can be explicitly set to one of the supported webhooks. This is a requirement for generic webhook.
- command is a command to execute after successful pull; followed by args which are any arguments to pass to the command. You can have multiple lines of this for multiple commands. then_long is for long executing commands that should run in background.
Each property in the block is optional. The path and repo may be specified on the first line, as in the first syntax, or they may be specified in the block with other values.
Public repository pulled into site root every hour:
git github.com/user/myproject
Public repository pulled into the "subfolder" directory in the site root:
git github.com/user/myproject subfolder
Private repository pulled into the "subfolder" directory with tag v1.0 once per day:
git {
repo [email protected]:user/myproject
branch v1.0
key /home/user/.ssh/id_rsa
path subfolder
interval 86400
}
Generate a static site with Hugo after each pull:
git github.com/user/site {
path ../
then hugo --destination=/home/user/hugosite/public
}
Part of a Caddyfile for a PHP site that gets changes from a private repo:
git [email protected]:user/myphpsite {
key /home/user/.ssh/id_rsa
}
fastcgi / 127.0.0.1:9000 php
Specifying a webhook:
git [email protected]:user/site {
hook /webhook secret-password
}
You might need quotes "secret-password"
around your secret if it contains any special characters, or you get an error.
Generic webhook payload: <branch>
is branch name e.g. master
.
{
"ref" : "refs/heads/<branch>"
}