go/goreleaser
go/goreleaser
1
0
Fork 0
mirror of https://github.com/goreleaser/goreleaser.git synced 2025-01-08 03:31:59 +02:00
Code Issues Releases Activity
d18adfb57e
goreleaser/www/docs/scm/gitea.md
Carlos A Becker a3867c8ccb
docs: clarify token files a bit 
Signed-off-by: Carlos A Becker <caarlos0@users.noreply.github.com>
2022-12-28 10:19:29 -03:00

999 B
Raw Blame History

Gitea

API Token

GoReleaser requires an API token to deploy the artifacts to Gitea. You can create one in Settings | Applications | Generate New Token page of your Gitea instance.

This token should be added to the environment variables as GITEA_TOKEN.

Alternatively, you can provide the Gitea token in a file. GoReleaser will check ~/.config/goreleaser/gitea_token by default, but you can change that in the .goreleaser.yaml file:

# .goreleaser.yaml
env_files:
  gitea_token: ~/.path/to/my/gitea_token

Note that the environment variable will be used if available, regardless of the gitea_token file.

URLs

You can use GoReleaser with Gitea by providing its URLs in the .goreleaser.yaml configuration file. This takes a normal string, or a template value.

# .goreleaser.yaml
gitea_urls:
  api: https://gitea.myinstance.com/api/v1
  download: https://gitea.myinstance.com
  # set to true if you use a self-signed certificate
  skip_tls_verify: false