How cacic-fct/event-manager works
Overview
CACiC Event Manager is a monorepo for event registrations, attendance control, and certificate issuance. It contains public and administrative Angular applications, a TypeScript backend, shared libraries, persistent storage definitions, and operational integrations.
Components
• Public application — apps/public/src/main.ts
Angular application for public event discovery, registration, profiles, calendars, attendance collection, certificates, notifications, sports, and offline workflows. Routes and feature areas live under apps/public/src/app.
• Administrative application — apps/admin/src/main.ts
Angular application for event, attendance, subscription, certificate, people, permissions, publication, audit, place, prize-draw, and sports administration. Its backend-facing API adapters are organized under apps/admin/src/app/graphql.
• Backend service — apps/backend/src/main.ts
Server-side application exposing feature areas through GraphQL resolvers and HTTP controllers. Major domains include authentication and authorization, events, attendance, event forms, subscriptions, certificates, people, publishing, sports, prize draws, audit logs, calendars, privacy, notifications, search, and realtime updates.
• Relational persistence — apps/backend/prisma/schema
Prisma schema is split by domain, including events, people, attendance, certificates, permissions, forms, sports, and subscriptions. Historical database changes are recorded under apps/backend/prisma/migrations, establishing PostgreSQL as durable application state.
• Shared domain and API contracts — libs/shared-data-types/src/index.ts
Reusable TypeScript models and inputs for events, attendance, certificates, users, forms, subscriptions, sports, and related entities. Dedicated public and admin contract libraries provide narrower consumer-facing surfaces through libs/event-manager-public-contracts/src/index.ts and libs/event-manager-admin-contracts/src/index.ts.
• Reusable Angular platform code — libs/shared-angular/src/index.ts
Shared authentication, service-worker, privacy, realtime, forms, scanner, sports, notification, and UI components used by the applications.
• Browser offline state — libs/public-indexed-db/src/index.ts
IndexedDB-backed caches and queues for public data, attendance, oral attendance, sports operations, calendar preferences, and user offline data. This is a client-side persistence boundary rather than backend storage.
• Certificate template assets — certificate-templates/certificate-template.schema.json
Schema and template assets define certificate presentation variants, while certificate issuance and validation remain backend responsibilities.
External interfaces and dependencies
The README documents local backend dependencies on PostgreSQL, Redis, Typesense, and SeaweedFS, configured operationally under docker. The tree also exposes Keycloak authentication, S3 storage, Novu notifications, gRPC contracts, Turnstile, weather, and realtime/search integrations. These providers are external actors; the repository contains adapters and configuration boundaries, not the provider systems themselves.
Relationships
Browser users and administrators interact with the public or admin Angular applications. Those applications expose route-level pages and API clients, while backend resolvers/controllers define the server interface; the tree supports this boundary but does not prove exact request sequencing. Backend domain services own authorization, business rules, and durable writes through Prisma, with Redis, search, object storage, notifications, and realtime services serving specialized concerns. Shared contracts and libraries provide common models and UI behavior without owning feature persistence. Certificate templates are consumed as assets by the certificate area, and public IndexedDB supports offline client behavior independently of PostgreSQL.
Main entry points: src/main.ts Backend service · src/main.ts Public application · src/main.ts Administrative application · index.ts Shared domain types
Components 15
Applications and backend
- Public application · Public event discovery, registration, attendance, certificates, and offline workflows.
apps/public/src/main.ts - Administrative application · Administrative management for events, attendance, people, certificates, and permissions.
apps/admin/src/main.ts - Backend service · GraphQL resolvers and HTTP controllers for domain services and integrations.
apps/backend/src/main.ts - Relational persistence · Defines durable PostgreSQL application state by domain.
apps/backend/prisma/schema
Shared libraries and assets
- Shared domain types · Reusable models and inputs for application domains.
libs/shared-data-types/src/index.ts - Shared Angular platform · Reusable authentication, forms, realtime, scanner, notification, and UI code.
libs/shared-angular/src/index.ts - Browser offline state · Client-side caches and queues for public offline workflows.
libs/public-indexed-db/src/index.ts - Certificate templates · Certificate presentation schemas and variants.
certificate-templates/certificate-template.schema.json
External systems
- Browser users
- Administrators
- PostgreSQL
- Redis
- Typesense
- Object storage · Includes configured S3-compatible storage such as SeaweedFS.
- Integration providers · Authentication, notifications, gRPC, Turnstile, weather, and realtime providers.
Connections 17
- Browser users → Public application: interacts with
- Administrators → Administrative application: interacts with
- Public application → Backend service: uses API
- Administrative application → Backend service: uses API
- Shared domain types → Public application: defines models for
- Shared domain types → Administrative application: defines models for
- Shared domain types → Backend service: defines models for
- Shared Angular platform → Public application: provides platform code
- Shared Angular platform → Administrative application: provides platform code
- Public application → Browser offline state: uses offline state
- Backend service → Relational persistence: writes durable state
- Relational persistence → PostgreSQL: targets
- Backend service → Redis: uses · Specialized cache and operational dependency.
- Backend service → Typesense: uses search
- Backend service → Object storage: uses storage
- Backend service → Integration providers: integrates with
- Certificate templates → Backend service: provides certificate assets