ci: auto publish backend binaries

Once a new release is published, the new workflow uses Goreleaser to build the binaries and then uploads the assets manually.

.github/workflows/cli-publish.yml

@@ -0,0 +1,36 @@
+name: CLI
+
+on:
+  release:
+    types: [published]
+
+permissions:
+  contents: write
+
+jobs:
+  goreleaser:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+        with:
+          fetch-depth: 0
+      - uses: actions/setup-go@v4
+        with:
+          go-version: stable
+      - uses: goreleaser/goreleaser-action@v5
+        with:
+          distribution: goreleaser
+          version: latest
+          args: release --clean --snapshot
+          workdir: ./backend
+        env:
+          GORELEASER_CURRENT_TAG: 'v0.0.0' # can be anything since we're using --snapshot
+      - run: |
+          mkdir -p dist/artifacts
+          cp dist/*.{tar.gz,zip} dist/artifacts
+        working-directory: ./backend
+      - name: Upload assets
+        uses: softprops/action-gh-release@v1
+        with:
+          files: ./backend/dist/artifacts/*
+          fail_on_unmatched_files: true

.gitignore

@@ -31,4 +31,4 @@ e2e/test-results/
 e2e/playwright-report/
 e2e/playwright/.cache/
 /backend/build_info/version.txt
-
+/backend/dist

backend/.goreleaser.yaml

@@ -0,0 +1,24 @@
+before:
+  hooks:
+    - go mod tidy
+    - go generate ./...
+builds:
+  - env:
+      - CGO_ENABLED=0
+    goos:
+      - linux
+      - windows
+      - darwin
+
+archives:
+  - format: tar.gz
+    name_template: >-
+      {{ .ProjectName }}_
+      {{- title .Os }}_
+      {{- if eq .Arch "amd64" }}x86_64
+      {{- else if eq .Arch "386" }}i386
+      {{- else }}{{ .Arch }}{{ end }}
+      {{- if .Arm }}v{{ .Arm }}{{ end }}
+    format_overrides:
+    - goos: windows
+      format: zip

backend/README.md

@@ -51,7 +51,7 @@ To get the Hanko backend up and running you need to:
 5. [Configure JSON Web Key Set generation](#configure-json-web-key-set-generation)
 6. [Configure WebAuthn](#configure-webauthn)
 7. [Configure CORS](#configure-cors)
-8. [Start the backend](#run-the-backend)
+8. [Start the backend](#start-the-backend)
 
 ### Run a database
 
@@ -327,12 +327,14 @@ endpoints). These can be started separately or in a single command.
 docker run --mount type=bind,source=<PATH-TO-CONFIG-FILE>,target=/config/config.yaml -p 8000:8000 -it ghcr.io/teamhanko/hanko:latest serve public
 ```
 
-> **Note** The `<PATH-TO-CONFIG-FILE>` must be an absolute path to your config file created above.
+##### Using pre-built binaries
 
-The service is now available at `localhost:8000`.
+Each [GitHub release](https://github.com/teamhanko/hanko/releases) (> 0.9.0) has `hanko`'s binary assets uploaded to it. Alternatively you can use
+a tool like [eget](https://github.com/zyedidia/eget) to install binaries from releases on GitHub:
 
-`8000` is the default port for the public API. It can be [customized](./docs/Config.md) in the configuration through
-the `server.public.address` option.
+```bash
+eget teamhanko/hanko
+```
 
 ##### From source
 
@@ -346,6 +348,11 @@ Then run:
 ./hanko serve public --config <PATH-TO-CONFIG-FILE>
 ```
 
+> **Note** The `<PATH-TO-CONFIG-FILE>` must be an absolute path to your config file created above.
+
+`8000` is the default port for the public API. It can be [customized](./docs/Config.md) in the configuration through
+the `server.public.address` option.
+
 The service is now available at `localhost:8000`.
 
 #### Start the admin API