Lychee
uramaki.lychee
Self-hosted photo and visual-asset manager for uploading, organizing, browsing and sharing media.
A Docker Compose file for Lychee alone, generated from the catalog and checked by the safety inspector. Sign in and use Kitchen Credits to activate it.
Uses the Medusa cart and payment-session path. This test control does not create an order or capture payment.
Lychee provides the human-facing DAM surface for TC-BENTO-001. The v7.8.5 container exposes its web/API service on port 8000, supports PostgreSQL through DB_CONNECTION=pgsql, and supports S3-compatible object storage through configurable endpoint and path-style settings. Sushii Assets uses only the MIT/core feature set; upstream Supporter Edition/Keygen-gated features are outside the v0.1 boundary.
You know it worked when
- Lychee reaches its /up readiness endpoint on the private application network.
- Lychee connects to the authored PostgreSQL provider using DB_CONNECTION=pgsql.
- Uploading an image stores application metadata in PostgreSQL and media bytes in the authored S3-compatible object store.
- The same asset remains readable after the approved restart boundary.
Known sharp edges
- Supporter Edition features require separate upstream entitlement and are excluded from TC-BENTO-001 v0.1.
- S3 credentials and the application key are secrets and must be supplied by reference rather than committed.
- The accepted runtime proof must capture the actual pulled OCI digest; the source contract pins the versioned v7.8.5 image tag.