Files
gitea-mcp/appsettings.json
T
zhengchen.tao 0f07300cec
Build Docker Image / build (push) Has been cancelled
Build Docker Image / deploy (push) Has been cancelled
refactor: unify JwtOptions schema with obsidian-mcp + simplify deploy
- Config/JwtOptions: flatten SigningKeyCurrent/Previous into nested
  SigningKey { Current, Previous } class to match obsidian-mcp shape.
  Both services now bind the same env var pattern (Jwt__SigningKey__Current),
  removing the schema fork that caused gitea-mcp to start with empty keys
  when compose used the obsidian-mcp convention.
- Auth/JwtBearerSetup, appsettings.json, README: follow rename.
- .gitea/workflows/build-image.yml: deploy job no longer clones nas-infra
  to a temp dir (which lacks the gitignored .env.shared). Now cd directly
  into /volume1/docker/compose/gitea-mcp, exposed by gitea-runner mount.
2026-05-16 17:24:09 +08:00

34 lines
789 B
JSON

{
"Logging": {
"LogLevel": {
"Default": "Information",
"Microsoft.AspNetCore": "Warning",
"GiteaMcp": "Debug"
}
},
"AllowedHosts": "*",
"Gitea": {
"BaseUrl": "https://git.zhengchentao.win",
"AdminPat": "",
"RepoBlacklist": "",
"DefaultLimit": 50,
"MaxFileBytes": 1048576
},
"Jwt": {
"Issuer": "https://auth.zhengchentao.win",
"Audience": "gitea",
"SigningKey": {
"Current": "",
"Previous": ""
}
},
"Mcp": {
"OAuthDiscovery": {
"Issuer": "https://auth.zhengchentao.win",
"AuthorizationEndpoint": "https://auth.zhengchentao.win/authorize",
"TokenEndpoint": "https://auth.zhengchentao.win/token",
"RegistrationEndpoint": "https://auth.zhengchentao.win/register"
}
}
}