mirror of
https://github.com/Memo-2023/mana-monorepo.git
synced 2026-05-23 12:06:42 +02:00
Add Google's Gemini image edit family (Nano Banana) as a user-
selectable model for Wardrobe Try-On next to the existing OpenAI
path. Three concrete choices now expose themselves in the Solo and
Outfit Try-On buttons:
- openai/gpt-image-2 (default, falls back to gpt-image-1
server-side when the org isn't
verified)
- google/gemini-3-pro-image-preview (Nano Banana Pro — premium
identity / character consistency)
- google/gemini-3.1-flash-image-preview (Nano Banana 2 — newest,
fast, cheapest)
All three accept multi-image refs (face + body + garment) through
the same /api/v1/picture/generate-with-reference endpoint; the only
differences are the provider-specific request/response shape and
the model-id routing.
Server (apps/api/src/modules/picture/routes.ts):
- Guard now accepts `openai/*` and `google/*` prefixes and rejects
everything else as "not supported for edits". Each provider's key
is validated separately so missing GEMINI_API_KEY doesn't break
OpenAI calls and vice versa.
- New `callGeminiEdits(modelName)` helper mirrors the shape of
callOpenAiEdits: encodes the normalized PNG refs as base64
inline_data parts, POSTs to
generativelanguage.googleapis.com/v1beta/models/{model}:generateContent
with responseModalities=["TEXT","IMAGE"] and imageConfig
(aspectRatio + imageSize), pulls the generated image out of
candidates[].content.parts[].inlineData.
- Our internal size strings map cleanly: 1024x1024 → 1:1 / 1K,
1024x1536 → 2:3 / 1K, 1536x1024 → 3:2 / 1K. Gemini 1K is enough
for the thumbnail sizes Wardrobe renders; going higher bloats
payload without visible gain.
- creditsFor() gains a google/ branch proportional to upstream
pricing (pro ≈ 18, 3.1-flash ≈ 6, 2.5-flash ≈ 5).
- Response `model` reports `${provider}/${modelUsed}` so the picture
row's model metadata is accurate across providers.
Client (apps/mana/apps/web/src/lib/modules/wardrobe):
- api/try-on.ts: export `TryOnModel` union + `DEFAULT_TRY_ON_MODEL`.
RunGarmentTryOnParams / RunOutfitTryOnParams gain an optional
`model` field, threaded through `callGenerateWithReference`.
- components/TryOnModelPicker.svelte: new segmented control, three
options with label + one-line hint. Grid-auto-fits so it reflows
on the narrow workbench card.
- components/GarmentTryOnButton.svelte + TryOnButton.svelte: both
mount the picker above the Sparkle CTA. `estimatedCredits` on the
button label updates live when the user switches model so the
cost signal matches what the server will actually charge.
Env (scripts/generate-env.mjs): GEMINI_API_KEY and GOOGLE_API_KEY
now propagate from the root `.env.development` into `apps/api/.env`
so mana-api can pick them up at boot. The route reads GEMINI_API_KEY
with GOOGLE_API_KEY as fallback, matching how mana-llm ships today.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
||
|---|---|---|
| .. | ||
| e2e | ||
| scripts | ||
| src | ||
| static | ||
| .env.example | ||
| .gitignore | ||
| Dockerfile | ||
| eslint.config.js | ||
| MIDDLEWARE_SECURITY.md | ||
| package.json | ||
| playwright.config.ts | ||
| README.md | ||
| svelte.config.js | ||
| tsconfig.json | ||
| vite.config.ts | ||
| WELCOME_ROUTE_SETUP.md | ||
Mana Web
Modern SvelteKit web application for Mana credit/mana management system.
Features
- 🔐 Authentication with Supabase
- 🎨 Tailwind CSS for styling
- 📱 Responsive design
- 🔄 Real-time updates
- 🏢 Organization management
- 👥 Team management
- 💰 Credit/Mana transfers
- 🧪 Comprehensive testing
Tech Stack
- Framework: SvelteKit 2.x with Svelte 5 (Runes)
- Language: TypeScript
- Styling: Tailwind CSS 3.x
- Backend: Supabase (PostgreSQL + Auth)
- Middleware: Mana Middleware API
- Testing: Vitest + Playwright
- Deployment: Vercel/Netlify ready
Getting Started
Prerequisites
- Node.js 20+ and pnpm
- Supabase account and project
- Access to Mana Middleware
Installation
# Install dependencies
pnpm install
# Copy environment variables
cp .env.example .env
# Update .env with your credentials:
# - PUBLIC_SUPABASE_URL
# - PUBLIC_SUPABASE_ANON_KEY
# - PUBLIC_MIDDLEWARE_URL
Development
# Start dev server
pnpm dev
# Run type checking
pnpm check
# Run tests
pnpm test
# Run E2E tests
pnpm test:e2e
Building
# Build for production
pnpm build
# Preview production build
pnpm preview
Project Structure
src/
├── routes/ # File-based routing
│ ├── (auth)/ # Auth routes (login, register)
│ ├── (app)/ # Protected app routes
│ │ ├── dashboard/
│ │ ├── organizations/
│ │ ├── teams/
│ │ └── settings/
│ └── api/ # API endpoints
├── lib/
│ ├── components/ # Reusable components
│ │ ├── ui/ # UI primitives
│ │ └── features/ # Feature components
│ ├── stores/ # Svelte stores
│ ├── utils/ # Utilities
│ ├── types/ # TypeScript types
│ └── server/ # Server-only code
│ ├── db/ # Database utilities
│ ├── auth/ # Auth helpers
│ └── api/ # API integration
├── hooks.server.ts # Server hooks
└── app.css # Global styles
Environment Variables
Public Variables (exposed to client)
PUBLIC_SUPABASE_URL- Supabase project URLPUBLIC_SUPABASE_ANON_KEY- Supabase anonymous keyPUBLIC_MIDDLEWARE_URL- Mana Middleware URLPUBLIC_APP_NAME- Application name
Private Variables (server-only)
Add any private API keys or secrets here.
Deployment
Netlify (Production Setup)
The app is currently deployed to https://app.mana.how using Netlify.
Prerequisites
# Install Netlify CLI globally
npm install -g netlify-cli
# Login to Netlify
netlify login
Initial Setup (One-time)
The project is already configured with @sveltejs/adapter-netlify. If you need to set it up from scratch:
# Install the Netlify adapter
pnpm add -D @sveltejs/adapter-netlify
Update svelte.config.js:
import adapter from '@sveltejs/adapter-netlify';
Environment Variables
Ensure your .env file exists with the following variables:
PUBLIC_SUPABASE_URL=your_supabase_url
PUBLIC_SUPABASE_ANON_KEY=your_supabase_anon_key
MIDDLEWARE_URL=https://mana-middleware-111768794939.europe-west3.run.app
Important: Set these same environment variables in Netlify Dashboard → Site Settings → Environment Variables for production builds.
Deployment
# 1. Install dependencies (if needed)
pnpm install
# 2. Build for production
pnpm build
# 3. Deploy to production (site: mana)
netlify deploy --prod --site mana --dir build
The build process creates:
build/- Static assets and client code.netlify/- Serverless functions for SSR
Build Output
After running pnpm build, you should see:
- ✅ Client bundle in
build/ - ✅ Server functions in
.netlify/ - ✅ Netlify configuration (
_headers,_redirects)
Vercel (Alternative)
# Install Vercel adapter instead
pnpm add -D @sveltejs/adapter-vercel
# Deploy
vercel
Docker
# Build image
docker build -t mana-web .
# Run container
docker run -p 3000:3000 mana-web
Contributing
- Create a feature branch
- Make your changes
- Run tests and type checking
- Submit a pull request
License
Private - All rights reserved