The Co-op Cloud command-line utility belt 🎩🐇
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
KawaiiPunk 536c912113
Fixed typo in abra ac bash output
1 year ago
.gitea docs: add template 2 years ago
cli Fixed typo in abra ac bash output 1 year ago
cmd/abra refactor: drop comment 1 year ago
pkg fix: grand ssh, provisioning, perms refactor 1 year ago
scripts docs: more help for setting up 1 year ago
tests/resources test: ensure .env reading tests work 2 years ago
.drone.yml fix: use more descriptive name for token [ci skip] 2 years ago
.envrc.sample dosc: add gitea token [ci skip] 2 years ago
.gitignore test: increatse client/context.go coverage to 90% 1 year ago
.goreleaser.yml chore: avoid reverts in the change logi [ci skip] 1 year ago
Makefile test: go verbose on testing [ci skip] 1 year ago docs: reinstate install docs on README [ci skip] 1 year ago
go.mod chore: go mod tidy 1 year ago
go.sum chore: go mod tidy 1 year ago
renovate.json chore(deps): add renovate.json 1 year ago


Build Status Go Report Card

The Co-op Cloud utility belt 🎩🐇

abra is a command-line tool for managing your own Co-op Cloud. It can provision new servers, create apps, deploy them, run backup and restore operations and a whole lot of other things. Please see for more extensive documentation.

Quick install

curl | bash

Or using the latest release candidate (extra experimental!):

curl | bash -s -- --rc

Source for this script is in scripts/installer/installer.


Getting started

Install direnv, run cp .envrc.sample .envrc, then run direnv allow in this directory. This will set coopcloud repos as private due to this bug.. Or you can run go env -w but I'm not sure how persistent this is.

Install Go >= 1.16 and then:

  • make build to build
  • ./abra to run commands
  • make test will run tests
  • make install will install it to $GOPATH/bin
  • go get <package> and go mod tidy to add a new dependency

Our Drone CI configuration runs a number of sanity on each pushed commit. See the Makefile for more handy targets.

Please use the conventional commit format for your commits so we can automate our change log.


We use goreleaser to help us automate releases. We use semver for versioning all releases of the tool. While we are still in the public alpha release phase, we will maintain a 0.y.z-alpha format. Change logs are generated from our commit logs. We are still working this out and aim to refine our release praxis as we go.

For developers, while using this -alpha format, the y part is the "major" version part. So, if you make breaking changes, you increment that and not the x part. So, if you're on 0.1.0-alpha, then you'd go to 0.1.1-alpha for a backwards compatible change and 0.2.0-alpha for a backwards incompatible change.

Making a new release

  • Change ABRA_VERSION to match the new tag in scripts (use semver)
  • Commit that change (e.g. git commit -m 'chore: publish next tag x.y.z-alpha')
  • Make a new tag (e.g. git tag -a x.y.z-alpha)
  • Push the new tag (e.g. git push && git push --tags)
  • Wait until the build finishes on
  • Deploy the new installer script (e.g. cd ./scripts/installer && make)
  • Check the release worked, (e.g. abra upgrade; abra -v)

Fork maintenance


We maintain a fork of godotenv for two features:

  1. multi-line env var support
  2. inline comment parsing

You can upgrade the version here by running go get<commit> where <commit> is the latest commit you want to pin to. We are aiming to migrate to YAML format for the environment configuration, so this should only be a temporary thing.


A number of modules in pkg/upstream are copy/pasta'd from the upstream docker/docker/client. We had to do this because upstream are not exposing their API as public.