+
Gitea
+
+Generate a Gitea access token [here](http://gitea.com/user/settings/applications). At minimum, you'll need to select the `read:repository` scope, but `read:user` and `read:organization` are required for the `user` and `org` fields of your config file:
+
+
+
+Next, update your configuration with the `token` field:
+```json
+{
+ "$schema": "https://raw.githubusercontent.com/sourcebot-dev/sourcebot/main/schemas/v2/index.json",
+ "repos": [
+ {
+ "type": "gitea",
+ "token": "my-secret-token",
+ ...
+ }
+ ]
+}
+```
+
+You can also pass tokens as environment variables:
+```json
+{
+ "$schema": "https://raw.githubusercontent.com/sourcebot-dev/sourcebot/main/schemas/v2/index.json",
+ "repos": [
+ {
+ "type": "gitea",
+ "token": {
+ // note: this env var can be named anything. It
+ // doesn't need to be `GITEA_TOKEN`.
+ "env": "GITEA_TOKEN"
+ },
+ ...
+ }
+ ]
+}
+```
+
+You'll need to pass this environment variable each time you run Sourcebot:
+
+
+docker run -e GITEA_TOKEN=my-secret-token /* additional args */ ghcr.io/sourcebot-dev/sourcebot:latest
+
+
+
+
## Using a self-hosted GitLab / GitHub instance
@@ -226,7 +273,7 @@ If you're using a self-hosted GitLab or GitHub instance with a custom domain, yo
1. Install