Deploy Gogs to BOSH

One of the fastest ways to get gogs running on any infrastructure is to deploy this bosh release.

• Concourse CI
• Pull requests will be automatically tested against a bosh-lite (see testflight-pr job)
• New versions of gogs will be automatically added as the latest blob
• Discussions and CI notifications at #gogs-boshrelease channel on https://slack.cloudfoundry.org

Usage

To upload and deploy this BOSH release, run bosh deploy manifests/gogs.yml and include some optional operator files.

For example, if you are running cfdev you can target it and deploy gogs:

cf dev start
source <(cf dev bosh env)

git clone https://github.com/cloudfoundry-community/gogs-boshrelease.git
bosh -d gogs deploy gogs-boshrelease/manifests/gogs.yml \
  -o gogs-boshrelease/manifests/operators/routing.yml \
  -v routing-nats-deployment=cf \
  -v gogs-uri=gogs.v3.pcfdev.io \
  --vars-store creds.yml

open https://gogs.v3.pcfdev.io/user/sign_up

Note: --vars-store creds.yml is not required if your BOSH environment is configured with Credhub.

Post Deploy Errand

To create an admin user after deploying GOGS, run the following errand.

This was moved from the gogs_ctl script to this errand as it was never executed previously

bosh -d gogs run-errand gogs-admin

Deploy with Authentication Backends

You can deploy gogs with alternative authentication backends.

The supported backend types are available on the gogs website with examples of the configuration options each have here.

Using the configuration options examples, and the operator files in manifests/operators in this repository, you can craft different backends to use.

Deploy example with operator file:

bosh -d gogs deploy gogs-boshrelease/manifests/gogs.yml \
  -o gogs-boshrelease/manifests/operators/ldap-auth.yml \
  -v gogs-uri=gogs.v3.pcf.dev.io \
  --vars-store creds.yml

It is possible to specify multiple backends of the same type, see manifests/operators/ldap-auth-multiple.yml for an example.