How tarunvelli/rails-tabler-starter works
Main Components
A. Frontend Layer:
• Views (app/views) using ERB templates
• Assets (JavaScript, CSS) using Tabler UI framework
• Client-side controllers using Stimulus.js (app/javascript/controllers)
B. Backend Layer:
• Rails Controllers (app/controllers)
• Models (app/models)
• Background Jobs (Sidekiq)
• Authentication (Devise)
• Authorization (Pundit)
C. Data Layer:
• PostgreSQL Database
• Redis (for Sidekiq)
• Active Storage
Component Relationships
[Client Browser] ←→ [Frontend Layer]
• ↓
[Rails Application]
• ↙ ↓ ↘
[PostgreSQL] [Redis] [Storage]
Specific Implementation Details
a) User Management System:
• Devise Authentication
• OmniAuth Integration
• User Roles & Permissions
b) Multi-tenant Architecture:
• Spaces (Organizations/Teams)
• Subscription Management
• Role Management
c) Background Processing:
• Sidekiq Workers
• Scheduled Jobs
Important Flows to Highlight
a) Authentication Flow:
User → Devise → OmniAuth → Application
b) Authorization Flow:
Request → Pundit Policies → Controller → Response
c) Multi-tenant Flow:
User → Space → Roles → Permissions
Additional Elements
Architectural patterns:
• MVC pattern implementation
• Service-oriented components
• Policy objects (Pundit)
• Background job processing
Technical Stack Callouts
Key technologies:
• Ruby on Rails
• PostgreSQL
• Redis
• Sidekiq
• Devise
• Pundit
• Tabler UI
• Stimulus.js
Deployment Components
Deployment-related elements:
• Asset compilation
• Database migrations
• Background job workers
• Storage service
Remember to emphasize:
The background processing capabilities
This will give other developers a clear understanding of how the different parts of the system interact while highlighting the key architectural decisions that make this starter template powerful and flexible.