How mdop297/isnex works
Project type and purpose
• This is a full-stack, polyglot microservices monorepo (managed by Nx/pnpm) called “IsNex.”
• It provides:
• A Next.js frontend (apps/client)
• Two NestJS backend services—Auth (apps/auth-svc) and Document (apps/document-svc)
• A Python data-processing service (apps/data-processing-svc)
• Shared libraries for TypeScript (libs/tscommon) and Python (libs/pycommon)
• It targets containerized deployment (Docker, Docker Compose, Kubernetes, Skaffold) and CI/CD (GitHub Actions, Husky hooks, linting, Jest/Pytest).
File structure
• Top-level dirs:
• apps/… – service and client applications
• libs/… – shared code for TS and Python
• infras/… – Kubernetes manifests for dev and prod
• docker-compose*.yml, skaffold.yaml – local and cluster orchestration
• CI/CD & lint configs (.github/, jest.config.ts, eslint.*, commitlint, husky, Makefile)
• Each NestJS service has its own Dockerfile, Prisma schema/migrations (for Auth), and standard src/app MVC layout.
• The Next.js client under apps/client uses TypeScript, PostCSS, ESLint, and Next’s file-based routes.
• The Python service uses PyProject, Poetry or pip-tools (uv.lock), pytest tests, and shares code via libs/pycommon.