19723f30fb
Bisher hielt Medusa Ereignisse, Workflows und Sperren nur im Speicher. Was beim Neustart in der Schlange stand (Bestellmail, Versandlabel nach Zahlungseingang), war weg, und Medusa warnte beim Start "Local Event Bus installed. This is not recommended for production". Redis lief im Stack schon mit, wurde aber nur für Sitzungen genutzt. Jetzt laufen Event-Bus, Workflow-Engine und Locking über Redis, sobald REDIS_URL gesetzt ist. Ohne Caching-Modul: Webhook und Erstattungsabgleich lesen direkt nach dem Schreiben. Dafür Medusa 2.17.0 -> 2.17.2: In 2.17.0 wartet der Redis-Event-Bus beim Start auf Worker.run(), das erst beim Beenden zurückkehrt — der Server lauscht nie. 2.17.2 behebt genau das. @medusajs/ui 4.1.15 -> 4.1.19 (gehört zu 2.17.2). Geprüft: Start mit allen drei Modulen, Bestellung über die Store-API, Bestellmail kommt über die Redis-Warteschlange, Abo-Job in Redis eingeplant. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Medusa DTC Starter
Documentation | Website
Building blocks for digital commerce
Medusa DTC Starter
A production-ready monorepo starter for direct-to-consumer ecommerce stores powered by Medusa and Next.js. Includes a fully featured storefront with product browsing, cart, checkout, customer accounts, and order management.
Features
- All of Medusa's commerce features
- Multi-region support with automatic country detection
- Product catalog with variant selection
- Cart with promotion codes
- Multi-step checkout with shipping and payment
- Customer accounts with order history and address management
- Order transfer between accounts
Getting Started
Deploy with Medusa Cloud
The fastest way to get started is deploying with Medusa Cloud:
- Create a Medusa Cloud account
- Deploy this starter directly from your dashboard
Local Installation
**Prerequisites:
- Node.js v20+
- PostgreSQL v15+
- pnpm v10+
- Clone the repository and install dependencies:
git clone https://github.com/medusajs/dtc-starter.git
cd dtc-starter
pnpm install
- Set up environment variables for the backend:
cp apps/backend/.env.template apps/backend/.env
- Set the database URL in
apps/backend.env:
# Replace with actual database URL, make sure the database exists.
DATABASE_URL=postgres://postgres:@localhost:5432/medusa-dtc-starter
- Run migrations:
cd apps/backend
pnpm medusa db:migrate
- Add admin user:
cd apps/backend
pnpm medusa user -e admin@test.com -p supersecret
- Start Medusa backend:
cd apps/backend
pnpm dev
-
Open the admin dashboard at
localhost:9000/appand log in. Retrieve your publishable API key at Settings > Publishable API key. -
Set up environment variables for the storefront:
cp apps/storefront/.env.template apps/storefront/.env.local
- Update
apps/storefront/.env.localwith your Medusa publishable API key:
NEXT_PUBLIC_MEDUSA_PUBLISHABLE_KEY=pk_6c3...
- Start storefront:
cd apps/storefront
pnpm dev
The storefront runs on http://localhost:8000.
You can slo run the following command from the root to start both backend and storefront:
pnpm dev
Configuration
The storefront is configured via environment variables in apps/storefront/.env.local:
| Variable | Description | Default |
|---|---|---|
NEXT_PUBLIC_MEDUSA_PUBLISHABLE_KEY |
Publishable API key from your Medusa backend | — |
NEXT_PUBLIC_MEDUSA_BACKEND_URL |
URL of your Medusa backend | http://localhost:9000 |
NEXT_PUBLIC_DEFAULT_REGION |
Default region country code | dk |
NEXT_PUBLIC_BASE_URL |
Base URL of the storefront | https://localhost:8000 |
NEXT_PUBLIC_STRIPE_KEY |
Stripe publishable key (optional) | — |