b69e9d6f81
Decap is served from vienalatina.com and posts its OAuth code to git.vienalatina.com/login/oauth/access_token from the browser. Gitea disables CORS by default, so the browser discarded the response and Decap surfaced it as "TypeError: Failed to fetch" after a successful authorize — the login looks broken at the last step, with nothing wrong on either side individually. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NizVpJ2dwzCbjCrTLCjeHn
32 lines
1.4 KiB
YAML
32 lines
1.4 KiB
YAML
# Gitea — self-hosted git + OAuth provider for Decap and Woodpecker.
|
|
# Copy this directory to /srv/gitea/ on the server, then: docker compose up -d
|
|
# Web UI is bound to localhost only; Caddy proxies git.vienalatina.com to it.
|
|
|
|
services:
|
|
gitea:
|
|
image: gitea/gitea:1.22
|
|
restart: unless-stopped
|
|
environment:
|
|
- USER_UID=1000
|
|
- USER_GID=1000
|
|
- GITEA__server__DOMAIN=git.vienalatina.com
|
|
- GITEA__server__ROOT_URL=https://git.vienalatina.com/
|
|
- GITEA__server__SSH_DOMAIN=git.vienalatina.com
|
|
- GITEA__service__DISABLE_REGISTRATION=true
|
|
- GITEA__webhook__ALLOWED_HOST_LIST=ci.vienalatina.com
|
|
# Decap is served from vienalatina.com but exchanges its OAuth code for a
|
|
# token by calling git.vienalatina.com from the browser — a cross-origin
|
|
# request. Without this, Gitea returns no Access-Control-Allow-Origin, the
|
|
# browser drops the response, and Decap reports "TypeError: Failed to
|
|
# fetch" right after you authorize, which reads like a Decap bug.
|
|
- GITEA__cors__ENABLED=true
|
|
- GITEA__cors__ALLOW_DOMAIN=https://vienalatina.com
|
|
- GITEA__cors__METHODS=GET,HEAD,POST,PUT,PATCH,DELETE,OPTIONS
|
|
- GITEA__cors__HEADERS=Content-Type,User-Agent,Authorization
|
|
volumes:
|
|
- ./data:/data
|
|
- /etc/timezone:/etc/timezone:ro
|
|
- /etc/localtime:/etc/localtime:ro
|
|
ports:
|
|
- "127.0.0.1:3000:3000"
|