docs: anonymize domains and add forgejo-mcp details
This commit is contained in:
parent
c868ff7e29
commit
5f71688f20
2 changed files with 18 additions and 3 deletions
|
|
@ -63,7 +63,7 @@ DATABASE_URL="postgresql://postgres:secure_db_prod_pass@postgres-vpn:5432/specia
|
|||
# Next.js Application Settings
|
||||
# -----------------------------------------------------------------------------
|
||||
# The public or VPN-locked domain resolved by Caddy
|
||||
NEXT_PUBLIC_APP_URL="https://special-hotel.gaboggamer.online"
|
||||
NEXT_PUBLIC_APP_URL="https://special-hotel.yourdomain.com"
|
||||
|
||||
# High-entropy random secret key for production JWT signatures.
|
||||
NEXTAUTH_SECRET="prod_high_entropy_session_secret_key"
|
||||
|
|
@ -153,6 +153,21 @@ Exposes browser automation tools (take screenshots, click, type, fill forms).
|
|||
}
|
||||
```
|
||||
|
||||
#### F. Forgejo / Gitea MCP Server (`forgejo-mcp` / `gitea-mcp`)
|
||||
Exposes tools allowing `agy` to interact directly with your Forgejo repository (creating and merging pull requests, reviewing code, creating issues) via API.
|
||||
* **Use Case**: Enables `agy` to manage issues, automate code review tasks, verify pull request status, and merge pull requests directly using standard API endpoints.
|
||||
* **Harness Registration**:
|
||||
```json
|
||||
"forgejo-mcp": {
|
||||
"command": "npx",
|
||||
"args": ["-y", "forgejo-mcp"],
|
||||
"env": {
|
||||
"FORGEJO_REMOTE_URL": "https://git.yourdomain.com",
|
||||
"FORGEJO_AUTH_TOKEN": "your_forgejo_api_token_here"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 3. Managing Pull Requests via CLI (Forgejo Client)
|
||||
|
|
@ -173,7 +188,7 @@ Configure a login profile for your server:
|
|||
```bash
|
||||
tea login add \
|
||||
--name forgejo \
|
||||
--url https://git.gaboggamer.online \
|
||||
--url https://git.yourdomain.com \
|
||||
--token <YOUR_FORGEJO_PERSONAL_ACCESS_TOKEN>
|
||||
```
|
||||
*Note: You can generate a Personal Access Token in the Forgejo Web UI under Settings ➔ Applications.*
|
||||
|
|
|
|||
|
|
@ -43,6 +43,6 @@ This plan outlines the step-by-step path to construct, test, and host the platfo
|
|||
|
||||
## Phase 7: Deployment & Security Hardening
|
||||
* [ ] Write Dockge-compatible `docker-compose.yml` for the Next.js container.
|
||||
* [ ] Add `git.gaboggamer.online` or a sub-subdomain block in `/home/gabogg/docker/caddy/Caddyfile`.
|
||||
* [ ] Add `git.yourdomain.com` or a sub-subdomain block in the host Caddyfile.
|
||||
* [ ] Configure DNS resolution inside the WireGuard network.
|
||||
* [ ] Final end-to-end security audits.
|
||||
|
|
|
|||
Loading…
Reference in a new issue