Turkmenistan's vehicle marketplace rewrite — an active Turborepo rebuild with Expo, NestJS bounded contexts, Prisma, and air-gapped deployment constraints.
Active ground-up rewrite of Turkmenistan's vehicle marketplace. S1-S3 are shipped; S4 Listings CRUD is the current build slice. The architecture is designed for air-gapped deployment with no cloud dependency on the critical production path.
AutoTM is a vehicle listing and transaction platform built specifically for the Turkmenistan market. The original version was a Flutter mobile app with a stock NestJS API. The current rewrite is a ground-up rebuild of the product and delivery system: clearer domain boundaries, shared contracts, mobile-first listing workflows, and deployment constraints suitable for infrastructure inside Turkmenistan.
Phase 1 — Marketplace MVP
Testing: API, mobile, and SMS-gateway suites cover the shipped slices. CI remains the source of truth for regressions.
Documentation: Architecture Decision Records, context docs, sprint files with Definition of Done, and agent skill docs for mobile and TypeScript runtime boundaries.
Turborepo monorepo scaffold, CI pipeline, Docker Compose dev environment, and local Postgres/Redis/MinIO services.
Completed May 2026
Phone OTP authentication via custom SMS gateway, JWT access tokens, bcrypt-hashed refresh tokens, multi-device session cap with FIFO eviction, and rate limiting.
Completed May 2026
Listings CRUD with mobile 7-step wizard, media upload state machine, catalog integration, and public listing discovery.
Target May 2026
Full-text search, advanced filters, saved searches, and garage/dealership profiles.
Target Jun 2026
Socket.IO real-time chat between buyers and sellers, message persistence, and read receipts.
Target Jun 2026
Push notifications via FCM/APNS, in-app notification center, and notification preferences.
Target Jul 2026
Admin dashboard with moderation queues, user management, analytics, and content administration.
Target Jul 2026
App store submissions, production hardening, load testing, monitoring, and beta release to Turkmenistan market.
Target Aug 2026
NestJS on Fastify with pure TypeScript domain layer, one use-case per file, and ports/adapters for cross-context communication.
Stock NestJS feature folders led to bloated services and tight coupling. Bounded contexts with explicit domain/application/infrastructure/presentation layers enforce clear boundaries between identity, catalog, listings, subscriptions, conversations, notifications, content, reports, and admin.
NestJS API, Prisma ORM, Next.js web, and Expo mobile. Replaced Flutter, Sequelize, and Firebase.
Prisma provides type-safe migrations and a single schema source of truth. Expo + React Native gives better ecosystem access than Flutter for the team. Next.js handles both public site and admin dashboard.
Monorepo with 7 apps and 5 shared packages. Rejected Nx, Lerna, and multi-repo.
Shared packages for Prisma schema (db), Zod contracts, UI tokens, tsconfig presets, and ESLint config. All clients consume the same types and validation rules.
Self-hosted Ubuntu servers with Docker Compose, Caddy, and no cloud dependencies. Docker tarballs shipped via SCP/USB.
Internet connectivity inside Turkmenistan is unreliable and foreign cloud providers have latency and compliance issues. Topology C: build on CI, bundle images, transfer to local servers.
OTP via fleet of Android phones running a Kotlin agent. JWT access tokens + bcrypt-hashed refresh tokens. No password database.
Local SMS providers are expensive and unreliable. A fleet of 5–20 Android phones with SIM cards provides a cost-effective, controllable OTP delivery system. Multi-device sessions capped at 10 with FIFO eviction.
Self-hosted MinIO for S3-compatible object storage. Sharp for server-side variant generation. Client-side compression mandatory.
Replaces Firebase Storage. MinIO runs locally alongside the API. Sharp generates thumbnails and compressed variants on upload. Client compresses before upload to save bandwidth.
Expo mobile app unit and integration tests covering components, hooks, and API client behavior.
Domain, application, and e2e layers tested. NestJS service layer, controller, and utility tests pass consistently in CI.
API, web, admin, worker, and SMS-gateway containers build successfully with production optimizations and multi-stage Dockerfiles.
Lint, typecheck, test, and build steps run on every push and PR via self-hosted runner labeled tm-proxy.
Type-safe Prisma client generated from a single schema in packages/db. 8 migrations applied covering identity, catalog, listings, media, and exchange rates.
Expo mobile app listing creation wizard with step validation, media upload staging, and catalog integration. Prisma schema extended with ListingDraft, ListingMedia, and ExchangeRate. Known gaps documented: autosave edge cases, orphan cleanup, public listing-detail route pending.
Read endpoints for Brand, Model, Color, BodyType, Region, City, EngineType, Transmission, and DriveType. Seed data in Turkmen, Russian, and English. FX rates table for currency conversion.
Phone OTP authentication via custom SMS gateway with 5-device fleet. JWT access tokens and bcrypt-hashed refresh tokens. Multi-device session cap at 10 with FIFO eviction. Rate limiting on OTP endpoints. Full domain + application + e2e test coverage.
Single schema file in packages/db covering identity, catalog, listings, media, exchange rates, and subscriptions. Type-safe client generated and consumed by API, worker, and SMS-gateway apps.
Turbo.json pipeline configured with lint, typecheck, test, and build stages. Shared packages established for Prisma schema, Zod contracts, UI tokens, tsconfig, and ESLint config. Docker Compose dev environment with Postgres 16, Redis 7, and MinIO.