How richardmaycode/mobbwash_clone works
Project type and purpose
• This is a Ruby on Rails full-stack web application (monolith) that serves both customer and admin interfaces, exposes JSON endpoints (e.g. prices/show.json.jbuilder), supports real-time updates via ActionCable, background processing via ActiveJob, push notifications (WebPush), PWA features, and integrates with external services (Stripe, mailers, etc.).
File structure (high-level)
• Top-level:
• app/ (MVC folders: controllers, models, views; assets & JavaScript packs using importmap + Stimulus + Tailwind)
• config/ (routes, environments, initializers, cable, database, job queue config)
• lib/webpush (notification logic)
• db/ (migrations, seeds, schema)
• bin/, Dockerfile, Procfile.dev, .github CI workflows
• Patterns:
• MVC (app/controllers → app/models → app/views)
• Concerns (reusable modules under app/controllers/concerns, app/models/concerns)
• Stimulus controllers under app/javascript/controllers
• PWA: manifest + service-worker in app/views/pwa
• ActiveJob with custom adapter (solid_queue.yml)
• ActionCable (app/channels)
• External integrators (Stripe controllers, WebPush, ActionMailer)
README
• Placeholder, so infer standard Rails deployment: Puma web server, PostgreSQL (or similar), job queue, Redis if used, SMTP or third-party mailer, S3/local storage for ActiveStorage.
Detail
• PWA service worker component and manifest.
• Stimulus controllers interacting with specific Rails endpoints.
• Call out the importmap module loader.
• Where Tailwind CSS is applied (assets pipeline).
• Initialization via config/initializers (e.g., permissions_policy, content_security_policy).