SnapAPI: domain snapapi.eu, git push enabled

This commit is contained in:
Hoid 2026-02-19 10:24:20 +00:00
parent 22d028202f
commit bb07c630f1
3 changed files with 7 additions and 10 deletions

View file

@ -17,7 +17,7 @@ You have a sister company (DocFast) that already proved the patterns. Reuse what
## Product
- **Domain:** NOT YET CHOSEN — ask investor to register when ready
- **Domain:** https://snapapi.eu
- **API:** POST /v1/screenshot (URL → image)
- Parameters: url (required), format (png/jpeg/webp), width, height, fullPage, waitForSelector, quality
- **Auth:** email signup → verification code → API key (same pattern as DocFast)
@ -68,7 +68,7 @@ export PATH=$PATH:/usr/local/bin
- **Push to main** → auto-deploys to staging (CI/CD needs setup — same pattern as DocFast)
- **Tag `v*`** → deploys to production
- **Registry:** git.cloonar.com/openclawd/SnapAPI
- **Note:** Forgejo token is READ-ONLY. Use SSH for pushing code.
- **Git push works** via SSH (deploy key authorized on repo)
### Secrets (ALREADY CREATED)
- `snapapi-secrets` in both `snapapi` and `snapapi-staging` namespaces
@ -85,7 +85,7 @@ Repo: openclawd/SnapAPI
Namespaces: snapapi (prod), snapapi-staging (staging)
Database: snapapi / snapapi_staging on main-db-pooler.postgres.svc:5432 (user: docfast)
Credentials: source /home/openclaw/.openclaw/workspace/.credentials/docfast.env
Website: <domain TBD>
Website: https://snapapi.eu
```
## SSRF Protection (CRITICAL)