Applications¶
Purpose¶
The factual inventory of application source areas in this repository and their current production activation state.
Applications¶
| App | Workspace | Worker name | Domain | Runtime / status |
|---|---|---|---|---|
| Corporate | @akshaya/corporate-web |
akshaya-group-global |
akshayagroupglobal.com |
Static + Worker routes (/customer-portal*, /api/customer/*) - active |
| Software | @akshaya/software-web |
akshaya-software |
software.akshayagroupglobal.com |
Static + Worker routes (/freelancer-portal*, /api/freelancer/*) - active |
| Logistics | @akshaya/logistics-web |
akshaya-logistics |
logistics.akshayagroupglobal.com |
Static frontend - active, backend integration still being completed |
| Commerce | @akshaya/commerce-web |
akshaya-commerce |
commerce.akshayagroupglobal.com |
Static + Worker routes (run_worker_first: ["/api/*"]) - active, D1-backed production catalog/checkout/orders as of feature/commerce-production-backend |
| Embroidery | @akshaya/embroidery-web |
akshaya-embroidery |
embroidery.akshayagroupglobal.com |
Static frontend + central API enquiries - active |
| Admin | @akshaya/admin-web |
akshaya-admin |
admin.akshayagroupglobal.com |
Worker-first (run_worker_first: true) - active |
| Investors | @akshaya/investors-web |
akshaya-investors |
investors.akshayagroupglobal.com |
Source retained only - inactive / not deployed |
Plus the central API Worker: @akshaya/api-worker, name akshaya-group-global-api, domain
api.akshayagroupglobal.com.
Active production scope¶
The active production deployment set is Corporate, Software, Logistics, Commerce, Embroidery, Admin and the central API. Both automatic and manual production workflows use the same active-app scope and finish with the production smoke test.
Logistics is an active site whose current React business data is still largely prototype/
local-browser state - the real D1-backed application Worker for it is not yet implemented (out of
scope for feature/commerce-production-backend, which covers Commerce only). Commerce is no
longer in that state: as of feature/commerce-production-backend it has its own D1-backed Worker
(public catalog reads, authenticated checkout, real order history) and calls the central
OPERATIONS_API_TOKEN-protected /api/commerce/orders server-to-server for order creation, the
same protected-surface pattern this paragraph used to describe as still-pending for it. See
Applications → Commerce for the full detail.
Investors¶
Investors is deliberately inactive. Its source and historical Cloudflare configuration remain so a future reactivation can reuse them, but:
- it is absent from both production deployment workflows;
- it is absent from production smoke testing;
- the root production deploy script is disabled;
/api/investors/*is blocked by the central API entry point.
Reactivation should be a deliberate future change that restores deployment, backend policy, security controls and smoke/E2E coverage together.
Per-application detail¶
See Applications section for one dedicated page per app.