MyGo 云音乐
用 Go 与 MyGo 写成的第三方网易云音乐桌面客户端。原生界面,没有 WebView;边下边播,无损与 Hi-Res,逐字歌词与「律动」,刘海播放器。
Translation pending
ქართული AI ვიდეო სტუდია Reels‑ისთვის: აღწერე სცენა და მიიღე მზა ვიდეო — კადრებით, ქართული ხმით, მუსიკით და სუბტიტრებით. ფასი ჩანს, სანამ დაიწყებ.
Translation pending
MediaTypeScript · PLpgSQLGitHub @kintsurashviligaga-opsOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Loading the full README. The saved excerpt is shown below.
Production-ready Next.js 14 SaaS platform with 13 AI services, premium subscription billing, and enterprise-grade security.
🚀 Launch Status: 95% Ready | ✅ All Services Live | ✅ Production HardenedRead the full README ↗Production-ready Next.js 14 SaaS platform with 13 AI services, premium subscription billing, and enterprise-grade security.
🚀 Launch Status: 95% Ready | ✅ All Services Live | ✅ Production Hardened
Do not use OneDrive paths for this project.
C:\Users\admin\OneDrive\...C:\Projects\avatar-g-frontend-v3Migration steps (one-time):
mkdir C:\Projects -Force
robocopy "C:\Users\admin\OneDrive\Desktop\avatar-g-frontend-v3" "C:\Projects\avatar-g-frontend-v3" /MIR /XD node_modules .next .turbo /R:1 /W:1
Open the correct folder in VS Code (not OneDrive):
code "C:\Projects\avatar-g-frontend-v3"
Verify current working directory:
npm run check:cwd
Expected output:
OK: Not running inside OneDrive path.If you see a OneDrive warning, close the workspace and reopen C:\Projects\avatar-g-frontend-v3.
After moving/opening, run:
npm ci
npm run typecheck
npm run build
# 1. Install dependencies
npm install
# 2. Set up environment variables
cp .env.example .env.local
# Fill in: NEXT_PUBLIC_SUPABASE_URL, SUPABASE_SERVICE_KEY, STRIPE_SECRET_KEY, etc.
# 3. Run database migrations
supabase db push
# 4. Start development server
npm run dev
# 5. Open browser
# Open the exact "Local" URL printed by Next.js in terminal
# (default: http://localhost:3000)
Use a fixed dev port so localhost does not jump between ports:
# Default fixed port
npm run dev
# Alternative fixed port for parallel sessions
npm run dev:3003
If a port is busy:
netstat -ano | findstr :3003
taskkill /PID <pid> /F
NEXT_PUBLIC_SUPABASE_URL=https://your-project.supabase.co
NEXT_PUBLIC_SUPABASE_ANON_KEY=your-anon-key
SUPABASE_SERVICE_KEY=your-service-key
TELEGRAM_BOT_TOKEN=...
TELEGRAM_SETUP_SECRET=...
SITE_URL=https://www.myavatar.ge
STRIPE_SECRET_KEY=sk_test_...
STRIPE_WEBHOOK_SECRET=whsec_...
STRIPE_PRICE_PRO=price_... # Basic $30
STRIPE_PRICE_PREMIUM=price_... # Premium $150
NEXT_PUBLIC_APP_URL=http://localhost:3000
/app
/services/* - 13 service pages (video-studio, voice-lab, etc.)
/pricing - Subscription pricing page ($0/$30/$150)
/admin/analytics - Admin dashboard (metrics, charts)
/api
/agents/execute - AI job orchestration endpoint
/billing/* - Stripe webhook + subscription management
/admin/analytics - Analytics API (users, revenue, credits)
/components
/landing - CinematicScene (3D hero), OrbitingServices
/ui - shadcn/ui components (Button, Card, Badge)
/lib
/agents - Agent registry + 13 agent definitions
/orchestration - Unified AI orchestration layer (retry/timeout)
/billing - Plans config, Stripe integration, credit enforcement
/auth - Server-side auth utilities
# 1. Lint check
npm run lint
# 2. Type check
npx tsc --noEmit
# 3. Production build
npm run build
# 4. Start production server
npm run start
# 5. Enterprise verification suite
npm run test:enterprise
npm run verify:production
Verification report output:
artifacts/verification-report.jsonLoad test hook:
npm run load:test -- --baseUrl=http://localhost:3000 --endpoint=/api/observability/latency --requests=120 --concurrency=20
GET /api/billing/planGET /api/billing/usage?range=day|week|monthGET /api/billing/usage/export?range=day|week|monthGET /api/admin/billing/plansGET /api/admin/billing/users/:idGET /api/org/brandingPOST /api/agent-g/router/executeGET /api/observability/latencyGET /api/metrics/kpis?range=monthGET /api/metrics/revenueGET /api/metrics/conversionPOST /api/growth/referrals/codePOST /api/growth/referrals/trackPOST /api/growth/events/processPOST /api/growth/churn-risk/scan/ - Landing page (3D hero + orbiting services)/pricing - Pricing page ($0/$30/$150)/services/video-studio - Video generation UI/services/voice-lab - Voice cloning UI/chat - AI chat interface/agent - Premium Avatar G Agent (requires $150/mo)/admin/analytics - Admin dashboard (TODO: add role check)/api/admin/analyticsdeduct_credits(), add_credits()# 1. Connect GitHub repo to Vercel
vercel link
# 2. Set environment variables in Vercel dashboard
# (all vars from .env.local)
# 3. Deploy
git add .
git commit -m "Production audit complete"
git push origin main
# Auto-deploys via Vercel GitHub integration
# 4. Configure Stripe webhook
# URL: https://yourdomain.com/api/billing/webhook
# Events: checkout.session.completed, customer.subscription.*, invoice.*
Proprietary - Avatar G Platform
Built with Next.js 14 · TypeScript · React Three Fiber · Supabase · Stripe
# 1. Verify all files are present
ls -la app/page.tsx
ls -la app/api/chat/route.ts
ls -la components/workspace/ChatPanel.tsx
# 2. Install dependencies
npm install
# 3. Test build locally
npm run build
# 4. If successful, commit and push
git add .
git commit -m "feat: complete Avatar G neural ecosystem with all 8 services"
git push origin main
# 5. Vercel will auto-deploy
# Visit your deployment URL
All files are now complete and production-ready. The 404 error should be resolved once you deploy these files, particularly the app/page.tsx which was missing before.