JMS E-Talyer
Offline-capable shop management for multi-branch automotive service, live on a server I operate.
- full-stack
- DevSecOps
- security
▲ Live in production on a server I operate · 400+ backend tests · security scanning gates every release.
JMS E-Talyer cover
/work/jms-e-talyer/cover.webp · 16:10- backend tests
- 400+
problem
Multi-branch automotive shops needed shared inventory, sales and service records that stay accurate even when a branch goes offline.
my role
Sole developer, owner & maintainer: application, DevSecOps pipeline, and a self-provisioned VPS I secure, manage and operate myself.
key decisions
- Offline-capable PWA with barcode scanning.
- Server-authoritative conflict resolution replays orders made offline safely on reconnect.
- 400+ backend tests and security scanning gate every release.
- Self-provisioned and self-managed VPS: provisioning, deployment, monitoring and maintenance owned end to end.
- Layered security scanning: static analysis, dependency auditing, secret scanning across full git history, dynamic testing, and container vulnerability scanning.
- Hardened container runtime: multi-stage builds, production-only dependencies, non-root user, correct signal handling, health checks.
- Manual-gated deployments with branch and environment guards; secrets injected at runtime with no credentials written to disk.
stack
- Next.js
- Express
- MongoDB
- Redis
- Docker
- GitHub Actions
evidence
JMS E-Talyer
live systemsMotor parts inventory and service booking, running on a VPS provisioned, secured and deployed end to end. The working views sit behind a sign-in, so this is the public storefront.
captured 2026-09-06 · jms-e-talyer.shop
jms-e-talyer.shop ↗screens
System architecture
/work/jms-e-talyer/architecture.webp · 16:10Main screen
/work/jms-e-talyer/screen-1.webp · 16:10Key workflow
/work/jms-e-talyer/screen-2.webp · 16:10