> ## Content Index
> Fetch the complete content index at: https://notes.d4rkcyber.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Blaq Samurai
- URL: https://notes.d4rkcyber.com/blaq-samurai/
- Published: 2026-06-02T00:00:00.000Z
- Updated: 2026-10-28T14:12:05.000Z
- Description: Commerce storefront and admin stack combining a Next.js public shop, Medusa backend, PostgreSQL, Redis, Stripe, and custom collection pages.
- Author: David Dami
- Tags: Projects, ecommerce, nextjs, medusa, stripe

## Overview

Blaq Samurai is an ecommerce project that combines a custom Next.js storefront with a Medusa backend, database services, and a private admin surface.

The project is structured as a real commerce stack rather than a static shop. It includes storefront pages, collection routes, checkout code, custom order flows, backend commerce services, and operational data mounts.

## What It Does

- Serves a branded Next.js storefront
- Connects to a Medusa commerce backend
- Uses PostgreSQL and Redis for backend state
- Supports Stripe-related checkout dependencies
- Includes collection pages, product management routes, order/admin pages, and custom order routes
- Mounts persistent data and upload directories for runtime assets

## Architecture

The Compose stack includes PostgreSQL, Redis, Medusa, and the web storefront. The web service runs a prebuilt image and receives backend URL, publishable key, admin credentials, and Stripe-related configuration through environment variables.

The source tree shows a split between public routes and the `shogun` dashboard area. Public pages cover collections, checkout, custom orders, and marketing sections. Dashboard pages cover products, orders, settings, collections, login, MFA, and setup.

## Why It Matters

Blaq Samurai is one of the larger product projects in the Python directory. It demonstrates a full self-hosted commerce deployment with frontend polish, backend services, persistent storage, and payment integration concerns.

## Current Status

The project has a production Dockerfile, Compose stack, Medusa backend image, storefront image, and a wide route surface. The next useful documentation step is a deployment map that explains which container owns each user-facing capability.