2020-10-09 09:22:06 +00:00
|
|
|
# [gitdeploy](https://git.rootprojects.org/root/gitdeploy)
|
2020-09-09 04:30:07 +00:00
|
|
|
|
2020-10-20 23:05:01 +00:00
|
|
|
**gitdeploy** is an app for continuous deployment of static websites.
|
|
|
|
|
|
|
|
## Features
|
|
|
|
|
|
|
|
**gitdeploy** is intended for use with static websites that are generated after
|
|
|
|
changes are pushed to a Git repository. This works with sites that are being
|
|
|
|
edited in code and tracked in Git. Sites that have their content managed with a
|
|
|
|
headless CMS that pushes to Git are also very well-suited.
|
|
|
|
|
|
|
|
**gitdeploy** supports verified webhooks from Github, Bitbucket, and Gitea.
|
|
|
|
|
|
|
|
**gitdeploy** is written in Go. This means that it's a standalone binary
|
|
|
|
available on all major operating systems and architectures. It provides an API
|
|
|
|
with endpoints that handle webhooks, allow for initiation of builds, and getting
|
|
|
|
the status of builds and build jobs.
|
|
|
|
|
|
|
|
**gitdeploy** comes with a simple interface. The interface be disabled if you
|
|
|
|
don't want to use it.
|
2020-09-17 18:50:23 +00:00
|
|
|
|
2020-09-29 03:15:30 +00:00
|
|
|
## Usage
|
|
|
|
|
|
|
|
```bash
|
2020-10-21 05:54:33 +00:00
|
|
|
gitdeploy init
|
|
|
|
gitdeploy run --listen :3000 --scripts ./scripts/
|
|
|
|
```
|
|
|
|
|
|
|
|
```txt
|
|
|
|
Usage of gitdeploy run:
|
|
|
|
-listen string
|
|
|
|
the address and port on which to listen (default :4483)
|
|
|
|
-github-secret string
|
|
|
|
secret for github webhooks (same as GITHUB_SECRET=)
|
|
|
|
-bitbucket-secret string
|
|
|
|
secret for bitbucket webhooks (same as BITBUCKET_SECRET=)
|
|
|
|
-gitea-secret string
|
|
|
|
secret for gitea webhooks (same as GITEA_SECRET=)
|
|
|
|
-scripts string
|
|
|
|
path to ./scripts/{deploy.sh,promote.sh,etc}
|
|
|
|
-trust-repos string
|
|
|
|
list of repos (ex: 'github.com/org/repo', or '*' for all) for which to run '.gitdeploy/deploy.sh'
|
|
|
|
-compress
|
|
|
|
enable compression for text,html,js,css,etc (default true)
|
|
|
|
-promotions string
|
|
|
|
a list of promotable branches in descending order (default 'production,staging,master')
|
|
|
|
-serve-path string
|
|
|
|
path to serve, falls back to built-in web app
|
|
|
|
-trust-proxy
|
|
|
|
trust X-Forwarded-For header
|
2020-09-29 03:15:30 +00:00
|
|
|
```
|
|
|
|
|
2020-10-20 23:05:01 +00:00
|
|
|
## Install
|
|
|
|
|
|
|
|
You can download `gitdeploy` from the Github Releases API and place it in your PATH,
|
2020-10-21 06:00:02 +00:00
|
|
|
or install it with [Webi](https://webinstall.dev) ([webinstall.dev](https://webinstall.dev)):
|
2020-10-20 23:05:01 +00:00
|
|
|
|
|
|
|
**Mac**, **Linux**:
|
|
|
|
|
|
|
|
```bash
|
|
|
|
curl -sS https://webinstall.dev/gitdeploy | bash
|
|
|
|
```
|
2020-10-19 20:11:14 +00:00
|
|
|
|
2020-10-20 23:05:01 +00:00
|
|
|
**Windows 10**:
|
2020-09-29 03:15:30 +00:00
|
|
|
|
2020-10-20 23:05:01 +00:00
|
|
|
```bash
|
2020-10-20 23:17:19 +00:00
|
|
|
curl -A MS https://webinstall.dev/gitdeploy | powershell
|
2020-10-20 23:05:01 +00:00
|
|
|
```
|
2020-09-29 03:15:30 +00:00
|
|
|
|
2020-10-20 23:05:01 +00:00
|
|
|
## Setup with Deploy Scripts
|
2020-09-29 03:15:30 +00:00
|
|
|
|
2020-10-20 23:05:01 +00:00
|
|
|
Start by copying from `examples/` to `scripts/`.
|
|
|
|
|
|
|
|
```bash
|
|
|
|
rsync -av examples/ scripts/
|
|
|
|
```
|
|
|
|
|
|
|
|
```txt
|
|
|
|
scripts/
|
|
|
|
├── deploy.sh
|
|
|
|
├── git.example.com/org/go-project/deploy.sh
|
|
|
|
├── git.example.com/org/node-project/deploy.sh
|
|
|
|
├── git.example.com/org/mirror-project/deploy.sh
|
|
|
|
└── promote.sh
|
|
|
|
```
|
|
|
|
|
|
|
|
The default `deploy.sh` is sensible -
|
|
|
|
if another `deploy.sh` exists in a directory with the same repo name
|
|
|
|
as an incoming webhook, it runs it.
|
|
|
|
|
|
|
|
The example deploy scripts are a good start, but you'll probably
|
|
|
|
need to update them to suit your build process for your project.
|
|
|
|
|
2020-10-21 05:54:33 +00:00
|
|
|
### In-repo .gitdeploy scripts
|
|
|
|
|
|
|
|
A repo my have its own `.gitdeploy/deploy.sh` at its root, but by default these are ignored.
|
|
|
|
|
|
|
|
You can set `--trust-repos` (or `TRUST_REPOS`) to allow deploy scripts to be run directly
|
|
|
|
from a repository.
|
|
|
|
|
|
|
|
```bash
|
|
|
|
# trust a few repos to run their own deploy scripts
|
|
|
|
gitdeploy run --listen :3000 --trust-repos 'github.com/org/one,github.com/org/two'
|
|
|
|
|
|
|
|
# trust all repos
|
|
|
|
gitdeploy run --listen :3000 --trust-repos '*'
|
|
|
|
```
|
|
|
|
|
2020-10-20 23:05:01 +00:00
|
|
|
### Git Info
|
|
|
|
|
|
|
|
These ENVs are set before each script is run:
|
2020-09-29 03:15:30 +00:00
|
|
|
|
|
|
|
```bash
|
2020-10-21 03:59:10 +00:00
|
|
|
GIT_REPO_ID=github.com/my-org/my-project
|
|
|
|
|
|
|
|
GIT_CLONE_URL=https://github.com/my-org/my-project.git
|
|
|
|
|
2020-09-29 03:15:30 +00:00
|
|
|
GIT_DEPLOY_JOB_ID=xxxxxx
|
|
|
|
GIT_REF_NAME=master
|
|
|
|
GIT_REF_TYPE=branch
|
2020-10-21 03:59:10 +00:00
|
|
|
GIT_REPO_OWNER=my-org
|
|
|
|
GIT_REPO_NAME=my-project
|
2020-10-21 04:44:31 +00:00
|
|
|
GIT_REPO_TRUSTED=true
|
2020-09-29 03:15:30 +00:00
|
|
|
```
|
|
|
|
|
2020-10-19 19:21:50 +00:00
|
|
|
## API
|
|
|
|
|
|
|
|
```txt
|
|
|
|
GET /api/admin/jobs
|
|
|
|
|
|
|
|
{
|
|
|
|
"success": true,
|
|
|
|
"jobs": [
|
|
|
|
{
|
|
|
|
"job_id": "xxxx",
|
|
|
|
"created_at": "2020-01-01T00:00:00Z",
|
|
|
|
"ref": "0000000",
|
|
|
|
}
|
|
|
|
]
|
|
|
|
}
|
|
|
|
|
|
|
|
POST /api/admin/jobs
|
|
|
|
{ "job_id": "xxxx", "kill": true }
|
|
|
|
|
|
|
|
{ "success": true }
|
|
|
|
|
|
|
|
# note: see --help for how to use --promotions
|
|
|
|
POST /api/admin/promote
|
|
|
|
{ "clone_url": "https://...", "ref_name": "development" }
|
|
|
|
|
|
|
|
{ "success": true, "promote_to": "staging" }
|
|
|
|
|
|
|
|
# note: each webhook is different, but the result is to run a deploy.sh
|
|
|
|
POST /api/admin/webhooks/{github,gitea,bitbucket}
|
|
|
|
```
|
|
|
|
|
2020-09-28 07:26:16 +00:00
|
|
|
## Build
|
|
|
|
|
2020-10-20 23:05:01 +00:00
|
|
|
**Frontend**:
|
|
|
|
|
2020-09-28 07:26:16 +00:00
|
|
|
```bash
|
|
|
|
pushd html/
|
2020-10-19 19:21:50 +00:00
|
|
|
npm ci
|
|
|
|
scripts/build
|
2020-09-28 07:26:16 +00:00
|
|
|
popd
|
|
|
|
```
|
|
|
|
|
2020-10-20 23:05:01 +00:00
|
|
|
**API**:
|
|
|
|
|
|
|
|
With [GoReleaser](https://webinstall.dev/goreleaser):
|
|
|
|
|
2020-09-28 07:26:16 +00:00
|
|
|
```bash
|
2020-10-20 23:05:01 +00:00
|
|
|
goreleaser --snapshot --skip-publish --rm-dist
|
|
|
|
```
|
|
|
|
|
|
|
|
With [Golang](https://webinstall.dev/golang):
|
|
|
|
|
|
|
|
```bash
|
|
|
|
export GOFLAGS="-mod=vendor"
|
|
|
|
|
|
|
|
go run -mod=vendor git.rootprojects.org/root/go-gitver/v2
|
2020-09-28 07:26:16 +00:00
|
|
|
go generate -mod=vendor ./...
|
|
|
|
go build -mod=vendor .
|
|
|
|
```
|
|
|
|
|
2020-09-29 08:10:50 +00:00
|
|
|
You can use build tags to remove providers from the build:
|
|
|
|
|
|
|
|
```bash
|
|
|
|
go build -mod=vendor -tags nobitbucket,nogithub .
|
|
|
|
```
|
|
|
|
|
|
|
|
Supported tags are:
|
|
|
|
|
|
|
|
- nogithub
|
|
|
|
- nobitbucket
|
|
|
|
|
2020-10-09 09:44:56 +00:00
|
|
|
## Run as a System Service
|
|
|
|
|
|
|
|
```bash
|
|
|
|
sudo env PATH="$PATH" \
|
|
|
|
serviceman add --name gitdeploy --system \
|
|
|
|
--username app -path "$PATH" -- \
|
2020-10-21 06:03:21 +00:00
|
|
|
gitdeploy run --scripts ./scripts/
|
2020-10-09 09:44:56 +00:00
|
|
|
```
|
|
|
|
|
2020-09-28 23:39:05 +00:00
|
|
|
## Add Webhooks
|
|
|
|
|
|
|
|
To add a webhook you'll first need a secret
|
|
|
|
|
|
|
|
**with node.js**:
|
|
|
|
|
|
|
|
```js
|
|
|
|
crypto.randomBytes(16).toString("hex");
|
|
|
|
```
|
|
|
|
|
|
|
|
Then you'll need to set up the webhook in your platform of choice.
|
|
|
|
|
|
|
|
### Github
|
|
|
|
|
|
|
|
New Webhook: `https://github.com/YOUR_ORG/YOUR_REPO/settings/hooks/new`
|
|
|
|
|
|
|
|
```txt
|
|
|
|
Payload URL: https://YOUR_DOMAIN/api/webhooks/github
|
|
|
|
Content-Type: application/json
|
|
|
|
Secret: YOUR_SECRET
|
|
|
|
Which events would you like to trigger this webhook?
|
|
|
|
Just the `push` event.
|
|
|
|
Active: ✅
|
|
|
|
```
|
|
|
|
|
2020-09-29 08:08:35 +00:00
|
|
|
### Bitbucket
|
|
|
|
|
|
|
|
Sometimes Bitbucket does not give you the option to specify the (`X-Hub-Signature`) `secret`,
|
|
|
|
so you'll have to append an `access_token` instead. Example:
|
|
|
|
|
|
|
|
```txt
|
2020-10-09 09:22:06 +00:00
|
|
|
Title: gitdeploy
|
2020-09-29 08:08:35 +00:00
|
|
|
URL: https://YOUR_DOMAIN/api/webhooks/bitbucket?access_token=YOUR_SECRET
|
|
|
|
Triggers: Repository push
|
|
|
|
```
|
|
|
|
|
2020-09-28 23:39:05 +00:00
|
|
|
## How to Generate a Base64 Secret
|
|
|
|
|
|
|
|
**in your browser**:
|
|
|
|
|
|
|
|
```js
|
|
|
|
(async function () {
|
|
|
|
var rnd = new Uint8Array(16);
|
|
|
|
await crypto.getRandomValues(rnd);
|
|
|
|
var b64 = [].slice
|
|
|
|
.apply(rnd)
|
|
|
|
.map(function (ch) {
|
|
|
|
return String.fromCharCode(ch);
|
|
|
|
})
|
|
|
|
.join("");
|
|
|
|
var secret = btoa(b64)
|
|
|
|
.replace(/\//g, "_")
|
|
|
|
.replace(/\+/g, "-")
|
|
|
|
.replace(/=/g, "");
|
|
|
|
console.info(secret);
|
|
|
|
})();
|
|
|
|
```
|
|
|
|
|
|
|
|
**with node.js**:
|
|
|
|
|
|
|
|
```js
|
|
|
|
crypto
|
|
|
|
.randomBytes(16)
|
|
|
|
.toString("base64")
|
|
|
|
.replace(/\+/g, "-")
|
|
|
|
.replace(/\//g, "_")
|
|
|
|
.replace(/=/g, "");
|
|
|
|
```
|
|
|
|
|
2020-09-29 03:17:10 +00:00
|
|
|
## License
|
|
|
|
|
2020-10-09 09:22:06 +00:00
|
|
|
Copyright 2020 The gitdeploy Authors
|
2020-09-29 03:15:30 +00:00
|
|
|
|
|
|
|
This Source Code Form is subject to the terms of the Mozilla Public \
|
|
|
|
License, v. 2.0. If a copy of the MPL was not distributed with this \
|
|
|
|
file, You can obtain one at https://mozilla.org/MPL/2.0/.
|