How hassyyy/expense-manager-jaan works
Project type and purpose
• From the file tree and README title (“expense-manager”), this is a full-stack Ruby on Rails monolithic web application for tracking expenses/transactions.
• It uses Rails MVC, Stimulus JS (importmap), Avo (a Rails admin engine), ActionCable (real-time channels), ActiveJob, and ActionMailer.
File structure
• Top-level Ruby/Rails config: Gemfile, config/, db/, app/, bin/, lib/, public/, storage/.
• app/ splits into:
• app/controllers – HTTP controllers plus an Avo sub-controller for admin UI
• app/models – ActiveRecord models (Transaction)
• app/views – ERB views for both public UI and Avo cards/partials/layouts
• app/assets + app/javascript – CSS (Sprockets) and Stimulus controllers (importmap)
• app/channels – ActionCable channels
• app/jobs & app/mailers – background jobs & emails
• Avo admin: app/avo/cards, dashboards, filters, resources define metrics and CRUD
• Config: Puma web server, database.yml, importmap, initializers for Avo, CSP, etc.
• Procfile indicates Heroku/Procfile-based deployment.
Readme insights
• We infer from conventions and file tree that this is a standard Rails MVC monolith with an admin engine.