Ecommerce Template
Next.js·React 등으로 만든 최신 전자상거래 템플릿
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기README 전체를 불러오는 중입니다. 아래는 저장된 발췌입니다.
Built with Next.js (frontend/framework) + Supabase (database, auth, security)
• Vercel (hosting).README 전문 보기 ↗Built with Next.js (frontend/framework) + Supabase (database, auth, security)
/admin) where you review, approve, verify,
or reject every new businesssupabase/schema.sql — this sets up everything in one go,
including the photo storage bucketsupabase/migration-v2.sql instead — it only adds what's
new (verification fields, the admin-security trigger, photo storage) without
touching your existing data or recreating tables that already existGo to Authentication → Providers → Email in your Supabase dashboard and turn off "Confirm email." Here's why this matters: right now, a business needs to be logged in the moment they submit their application for their details to save correctly. If email confirmation is required, they'd have a gap between signing up and being able to log in — which would break the submission. You can turn this back on later once you want extra signup rigor; it's not required for the site to work either way, just recommended off for now.
In Supabase, go to Project Settings → API. You'll see two keys: the anon public key (already in use) and the service_role key. Copy the service_role key — treat this like a master password, never share it or put it anywhere public. It's what lets the admin page approve/reject businesses regardless of the normal security rules.
Copy .env.local.example to .env.local and fill in:
NEXT_PUBLIC_SUPABASE_URL / NEXT_PUBLIC_SUPABASE_ANON_KEY — from beforeSUPABASE_SERVICE_ROLE_KEY — from step 4ADMIN_PASSWORD — choose your own strong password for the /admin pageADMIN_SESSION_SECRET — any long random string (e.g. generate one at
randomkeygen.com, the "CodeIgniter Encryption Keys"
ones work well) — this is used to sign your admin login session, not the password
itselfnpm install
npm run dev
Visit http://localhost:3000
In Vercel → Domains, add luupa.net (or whichever you bought) and follow the DNS steps shown.
Visit yoursite.com/admin and enter the password you set in step 5. From there you can:
Nobody can reach this data without your password — not through the website's normal pages, not by tampering with browser requests, since the actual approve/reject action runs through a protected server route using the service role key, which never touches the browser at all.
app/ — edit and save, changes appear instantly in devSUBCATEGORIES lists in
components/SignupWizard.tsx, app/business/dashboard/page.tsx, and app/browse/page.tsx