How troll-os/openex works
Project type and purpose
• This is a full-stack, monolithic web application designed for planning and conducting crisis exercises and adversary simulation (OpenEx).
• Backend is a Java Spring-Boot RESTful API (openex-api module), sharing domain model libraries (openex-model, openex-framework).
• Frontend is a React/TypeScript single-page application (openex-front) providing public, private and admin UIs.
• The platform supports scheduling (Quartz via Spring scheduler), migrations (Flyway), file storage (MinIO), email/SMS/social integrations, SSO (OIDC, SAML, OAuth2).
File structure
• Top-level modules:
• openex-api: Spring Boot application (controllers, services, scheduler, security, imports, injectors).
• openex-framework: shared execution framework and contract definitions for injectors.
• openex-model: JPA entities, repositories, converters, MinIO driver, custom validators.
• openex-front: React app with Yarn/Vite, split into public, private, admin sections; uses Redux actions and reducers.
• Dev tooling and deployment:
• Dockerfiles, docker-compose, CI/CD configs (.circleci, .github workflows, .drone.yml).
• Flyway migration scripts in resources/db/migration.
README for additional insights
• Tech stack: Java 17+ with Spring Boot, React 18+, TypeScript, Yarn 4, Docker.
• Integrations: OpenEx ecosystem (email providers, OpenCTI), SSO providers (OAuth2, OIDC, SAML).
• Editions: Community (Apache 2.0) and Enterprise (non-commercial).