chiyi
622bc9ba9a
Now only the generate/video submit uses proxy.url; cookie-exchange/login, token refresh, credit-balance and project/session bootstrap all go direct. Also splits adobe GenerateVideo (submit=proxy, poll/download=local). Verified live: adobe gpt 1K cookie-exchange via local IP, submit 23.244.30.102 (proxy) vs local 76.209.9.65, 2.0MB PNG. Build+vet pass.
Vivid AI Backend
Go backend for vivid-ai, using:
- Gin
- GORM
- PostgreSQL
- Redis
Current scope
This is an in-progress rewrite. The current skeleton already includes:
- app bootstrap
- PostgreSQL and Redis initialization
- GORM auto-migrations
- session storage in Redis
- image access control for
/images/:user/:name - public site endpoint:
/admin/api/site - public showcase endpoint:
/admin/api/showcase - session-based auth endpoint:
/admin/api/auth/me
Environment
Set these before running:
$env:POSTGRES_DSN="host=127.0.0.1 user=postgres password=postgres dbname=vivid_ai port=5432 sslmode=disable TimeZone=Asia/Shanghai"
$env:REDIS_ADDR="127.0.0.1:6379"
$env:HTTP_ADDR=":6061"
Optional:
$env:APP_ENV="development"
$env:APP_TITLE="Vivid AI"
$env:SESSION_COOKIE_NAME="vivid_session"
$env:CORS_ORIGINS="http://localhost:5173,http://127.0.0.1:5173"
Run
go run ./cmd/api
Notes
- Generated media defaults to
../../ai-gateway/data/generatedrelative to the backend working directory. - Private images require either:
- session cookie
- bearer session token
- bearer API key
- Showcase images are public.