OpenLinker
OpenLinker keeps orders, inventory and fulfilment in sync across your store, marketplaces, invoicing and shipping. Self-hosted, Apache 2.0.
翻譯準備中
尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證製作者的介紹僅有上面的一句話。 更多詳情請閱讀儲存庫 README。 儲存庫 README ↗
正在載入完整 README。
檢視完整 README ↗SproutBox is a vertical farm management and marketplace web application built with Next.js (App Router), TypeScript, and Prisma (Postgres). It provides user roles for growers and restaurants, production planning, task allocation, QC flows, payouts, and Stripe-based payments.
This README gives contributors and maintainers a clear, runnable development workflow, architecture overview, required environment variables, security guidance, and contribution notes.
The app uses the Next.js App Router with server and client components. Prisma (with PostgreSQL) is used for data modelling and migrations. Authentication uses NextAuth-compatible patterns and a credentials provider alongside OAuth providers (optional).
Architecture highlights
src/app/src/app/api/src/components/src/lib/src/types/prisma/schema.prismagit clone <repo-url>
cd SproutBox
npm install
Create a .env.local file and set the required environment variables (see below).
Generate Prisma client and run migrations:
npx prisma generate
npx prisma migrate dev --name init
npx prisma db seed
npm run dev
Provide these values in .env.local (do not commit this file):
DATABASE_URL — Postgres connection string (example: postgresql://user:pass@host:5432/dbname)AUTH_SECRET or NEXTAUTH_SECRET — session/auth secretSTRIPE_SECRET_KEY — server-side Stripe secret keyNEXT_PUBLIC_STRIPE_PUBLIC_KEY — client-side Stripe publishable key (must be NEXT_PUBLIC_-prefixed to reach the browser; required for the restaurant checkout UI to render)STRIPE_WEBHOOK_SECRET — stripe webhook signing secretUPLOADTHING_TOKEN — UploadThing v7 API token (required for grower check-in/QC photo uploads)NEXT_PUBLIC_GA_MEASUREMENT_ID — GA4 Measurement ID (G-XXXXXXXXXX) for Google Analytics; see "Analytics" belowGOOGLE_CLIENT_ID & GOOGLE_CLIENT_SECRET — for Google OAuth (optional)Tip: Use your cloud provider or GitHub Actions / Vercel secrets to store production values.
prisma/schema.prisma.prisma/seed.ts. By default the seed script creates demo users; avoid running this in production or change seeded passwords via env overrides.npx prisma migrate reset --force
npx prisma db seed
npm run lint
The app loads Google Analytics 4 (src/components/shared/GoogleAnalytics.tsx, ID from
NEXT_PUBLIC_GA_MEASUREMENT_ID) and tracks pageviews across client-side App Router
navigation (src/components/shared/GoogleAnalyticsPageview.tsx — the base gtag config
only covers the first load, so this listens for pathname/searchParams changes and
fires the rest).
Custom events (src/lib/gtag.ts) map to the product's Acquisition / Conversion /
Engagement KPI categories:
| Event | Fired from | Maps to |
|---|---|---|
sign_up (method: grower) | GrowerOnboardingForm | Active Certified Growers (Acquisition) |
sign_up (method: restaurant) | RestaurantOnboardingForm | Restaurant partner count (Acquisition) |
purchase | NewOrderClient (no-Stripe path) / NewOrderClient on CheckoutModal completion (Stripe path) | MRR / Revenue |
checkin_submitted | CheckinModal | Grower engagement (proxy — see note below) |
pickup_requested | RequestPickupButton | Grower engagement |
Note: GA4 tracks the acquisition/engagement/conversion funnel (who signs up, who
orders, who stays active) — it does not compute operational KPIs like QC Pass Rate,
Kg Delivered/Week, or On-Time Delivery Rate, which live in the product database and
are already surfaced in /admin/analytics. There is also no explicit grower
task-accept/reject step in the product yet, so checkin_submitted is used as an
engagement proxy rather than a literal "Grower Acceptance Rate" event.
The project is deployed on Vercel, deploying automatically from main.
Vercel project settings:
DATABASE_URL, AUTH_SECRET/NEXTAUTH_SECRET, STRIPE_SECRET_KEY, NEXT_PUBLIC_STRIPE_PUBLIC_KEY, STRIPE_WEBHOOK_SECRET, and UPLOADTHING_TOKEN in the Vercel project's environment variables.npm run build as the build command..env files or secrets. Rotate any secrets that were committed accidentally.prisma/seed.ts contains default demo credentials — update or gate this behind a dev-only flag..next) from the repository and add to .gitignore.STRIPE_WEBHOOK_SECRET strictly in your secrets store; do not expose in client code.We welcome contributions — open issues and PRs.
Guidelines:
This project is released under the MIT License. See the LICENSE file for details.
If you'd like, I can now:
.env and .next to .gitignore and open a PR,prisma/seed.ts to require an env override for seeded credentials,