How hassyyy/expense-manager-hassyyy works
Main Components
• Client (Browser)
• Load Balancer / Procfile (Heroku-style process)
• Web Server (Puma)
• Rails Application
• Router & Middleware
• Controllers (including Avo admin controllers)
• Models (ActiveRecord + DB)
• Views & Assets (Importmap, Stimulus controllers, CSS)
• ActiveJob (background jobs)
• ActionMailer (emails)
• ActionCable (WebSockets)
• Avo Admin (dashboard, cards, filters, actions)
• Database (PostgreSQL / MySQL / SQLite)
• Storage (ActiveStorage local/files or cloud)
• External Services
• Expensify API integration (via app/avo/actions/expensify.rb)
• Email SMTP provider
Relationships & Interactions
• Browser → HTTP(S) → Load Balancer / Dyno → Puma → Rails Router
• Router dispatches to Controllers → interact with Models (ActiveRecord → DB)
• Controllers render Views (ERB) and serve Assets (JS/CSS via Importmap + Stimulus)
• Avo Admin UI is a mounted Rails Engine under /avo, using its own Controllers, Views, Cards, Filters, and Actions
• Background tasks (e.g., sending receipts, scheduled jobs) flow from Controllers or Jobs → ActiveJob → Job Adapter → execution
• Real-time features (if any) use ActionCable → browser WebSocket connection
• ActiveStorage manages file uploads → Storage layer (local disk or S3)
• External API calls (Expensify) originate from Avo Actions or Jobs
• Outbound email via ActionMailer → SMTP service
Architectural Patterns & Technologies
• MVC (Model-View-Controller) at core
• Rails Engine (Avo) for admin interface
• Importmap + Stimulus.js for front-end interactivity (no webpacker)
• ActiveJob for asynchronous processing
• ActionCable for real-time channel support
• ActiveStorage for file handling
• Standard Rails initializers & config/environments for environment-specific behavior