LuceneXWMS
WMS/Documentation

LUCENEX / Documentation

Architecture & data

Frontend, API, database providers and the current Cloudflare boundary.

Reviewed 9 November 2026 · WMS 8020cd0
On this pageCurrent application stackApplication request pathCloudflare is not a completed backend replacement

Current application stack

  • Frontend: Vue 3, TypeScript, Vue Router, Vuex, Vuetify and Vite. XLSX and print helpers run in the browser.
  • Backend: C# / ASP.NET Core targeting .NET 7, Entity Framework Core, token authentication and server-side action authorization.
  • Database: SQLite is the current default. Provider configuration for MySQL, SQL Server and PostgreSQL exists, but this fork’s cited acceptance evidence is SQLite-based. A provider switch requires schema/data migration and workflow testing.
  • Visualization: embedded Unity WebGL assets, separately compiled from the Vue interface.

Application request path

Browser / Vue
  → same-origin /api
  → ASP.NET Core controllers
  → authorization + warehouse services
  → Entity Framework Core
  → persistent SQLite database

Cloudflare is not a completed backend replacement

The repository includes a Worker/static-assets deployment path that proxies API traffic to a .NET container and stores large Unity assets in R2. The account’s Containers access blocked that backend route. A native TypeScript/Workers/D1 rewrite was started as an unfinished draft and then paused; it has no documented workflow parity.

This documentation website runs independently on Cloudflare. Its availability does not mean the warehouse application is running.