You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
--host and FORGE_HOST now accept a full http://host:port URL, and a
scheme = http key is accepted under [domain] in config (settable via
forge auth login --scheme). The API base URL is built from that scheme
instead of hardcoding https, so a local Forgejo/Gitea on a private IP
without TLS is reachable.
DetectForgeType and Client.RegisterDomain accept an optional scheme
prefix on the domain argument for the same reason; the bare host is
still used as the registry key.
Copy file name to clipboardExpand all lines: README.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -128,6 +128,16 @@ type = gitlab
128
128
129
129
This tells forge that the project uses GitLab and that `gitlab.internal.dev` is a GitLab instance, so contributors don't each need `--forge-type` or `FORGE_HOST`.
130
130
131
+
For a self-hosted instance served over plain HTTP (a local Forgejo in Docker, say), add `scheme = http` to its section in `~/.config/forge/config`, use `forge auth login --scheme http`, or pass a full URL to `--host`/`FORGE_HOST`:
132
+
133
+
```ini
134
+
[172.30.0.10:3000]
135
+
type = forgejo
136
+
scheme = http
137
+
```
138
+
139
+
Committed `.forge` files cannot set the API scheme.
140
+
131
141
Precedence from highest to lowest: CLI flags, environment variables, `.forge`, `~/.config/forge/config`, built-in defaults.
0 commit comments