How n7consulting/incipio works
Project type and purpose
• Jeyser CRM is a monolithic Symfony-based ERP/CRM web application.
• It exposes a browser-based UI, backed by PHP controllers, Twig templates, Doctrine ORM, and various Symfony services.
• It’s packaged for Docker-Compose with a Traefik reverse proxy, MySQL, mailer service, and the PHP web container.
File structure
• Top-level “docker” and “docker-compose.yml.dist” define the deployment architecture (Traefik proxy, web, mysql, mail).
• “public/” holds the front controller (index.php), assets (CSS/JS/images), and the manifest.
• “src/” follows standard Symfony MVC:
• Controller/ – HTTP controllers by feature
• Entity/ – Doctrine entities for domain objects
• Repository/ – data access layers
• Service/ – business logic modules (comments, key-value store, project and publishing services)
• EventListener/ – domain event subscriptions
• Form/ – request validation and form building
• “templates/” contains the Twig view layer.
• “config/” has Symfony configuration, routing, bundles, security, environment-specific settings.
• “var/” holds runtime artifacts: sessions, file store, key-value JSON.
README for additional insights
• Confirms it’s an open-source, GDPR-compliant ERP/CRM for junior enterprises.
• Mentions features: member/customer management, project/document management, docx export.
• Deployable in 5 commands (leverages Docker).
Main components
a. Client: Web browser (React-free, standard HTML/CSS/JS)
b. Reverse proxy: Traefik (HTTPS, SSL, routing)
c. Web container: Nginx or Apache fronting PHP-FPM, serving Symfony
d. Application: Symfony PHP MVC
• Presentation layer: Twig templates & static assets
• Controllers: API/endpoints, form handling
• Services & Event Listeners: business rules (CommentManager, ChartManager, CsvImporter, etc.)
• Domain layer: Entities, Repositories (Doctrine ORM)
• Form layer: Symfony Form components
e. Persistence: MySQL database (Doctrine)
f. File storage:
• var/documents for .docx templates and generated files
• var/key_value_store JSON store (KeyValueStore service)
g. Mailer: Docker “mail” container (SMTP) used by SwiftMailer
h. External services: none hard-coded, but could integrate e-mail, third-party importers
Relationships and interactions
• Browser ↔ Traefik: HTTPS requests
• Traefik ↔ Web container: route to port 80
• Web container ↔ Symfony front controller → Controllers
• Controllers → Forms → Services → Repositories
• Services ↔ Database (via Doctrine)
• Services ↔ File system (documents, key‐value store)
• Services ↔ Mail container (SwiftMailer)
• EventListeners subscribe to domain events inside the app
Architectural patterns and design principles
• MVC (Presentation: Twig; Controllers; Model: Entities + Repositories)
• Dependency Injection via Symfony service container
• Layered architecture: Presentation, Application (Controllers + Forms), Domain (Entities, Business Services), Infrastructure (DB, file store, mailer)
• Modular service organization by bounded context (Comment, Project, Publish, Stat, KeyValueStore)
• Docker Compose for environment orchestration
Technologies, frameworks, and libraries
• Symfony 4/5 (Bundles, DI Container, HTTP Kernel)
• Doctrine ORM + Migrations + Fixtures
• Twig templating engine
• SwiftMailer for email
• Behat for acceptance tests
• Docker (Docker Compose, Traefik)
• MySQL
• PHPUnit/Behat for testing
Don’t overthink – decompose as much as possible
• Docker Compose containers individually
• Every external interaction: mailer, file I/O, database, browser