How sleede/fab-manager works
Project type and purpose
• Full-stack web application (Ruby on Rails backend + SPA-style front-end in TypeScript/TSX + AngularJS directives).
• Provides REST API, OpenAPI endpoints, background processing, search, payment, SSO.
• Front-End (Browser)
• Components: React/TSX modules, AngularJS directives, CSS/SCSS assets, Webpack bundle.
• Interfaces: REST API client, OpenAPI client.
• Back-End Web Tier (Rails App Server)
• Controllers (MVC & API controllers), Views (ERB, Jbuilder JSON), Service Objects, Models, Policies, Concerns, Uploaders, Validators.
• Persistence & Infrastructure
• Primary Data Store: PostgreSQL
• Full-Text Search: Elasticsearch
• Cache & Queue: Redis (Sidekiq for background jobs)
• File Storage: ActiveStorage (local/S3)
• External Services
• Payment Gateways: Stripe, Payzen (via lib/stripe and lib/pay_zen)
• SSO Providers: OAuth2, OpenID Connect, SAML (lib/omni_auth/strategies)
• Email/Scheduling: SMTP, ActionMailer, Sidekiq Workers
Detail relationships and data flows
• Browser → Web Tier: HTTP(S) requests to Nginx/Passenger or Puma (config/puma.rb)
• Web Tier → DB: ActiveRecord ORM calls
• Web Tier → Elasticsearch: via application code (config/initializers/elasticsearch.rb)
• Web Tier → Redis/Sidekiq: enqueue/dequeue background jobs (workers/)
• Sidekiq Workers → DB, External APIs, Email
• Web Tier → External Payment/SSO: HTTP calls through wrapper libraries (lib/stripe, lib/pay_zen, lib/omni_auth)
Architectural patterns
• Layered architecture: Presentation → Application (Controllers/Services) → Domain (Models/Policies) → Infrastructure
• Service-object pattern: app/services/ for business logic
• Modular front-end: component-based (app/frontend/src/javascript/components), typed API clients
• Monolithic deployment: single codebase in Docker/Vagrant (Dockerfile, Vagrantfile), CI via GitHub Actions/GitLab CI