How common-member/nightrip works
Project type and purpose
• This is a full-stack, monolithic web application built with Ruby on Rails (v7.2.2.1) serving server-rendered HTML enhanced by Hotwire (Turbo + Stimulus).
• Purpose: “NighTrip” is a night-scape search & social sharing service where users can browse, post, comment on, and “diagnose” (quiz-driven recommendations of) night-view spots; it supports user auth (Devise + Omniauth), favoriting, rankings, and PWA features.
File structure
• app/ contains an MVC layout: controllers (app/controllers), models (app/models), views (app/views), plus channels (Action Cable), jobs (Active Job), mailers.
• app/javascript/controllers holds Stimulus controllers for dynamic behaviors (autocomplete, comments, form steps).
• app/assets/stylesheets uses Tailwind CSS + daisyUI.
• config/ defines routes, database (PostgreSQL), storage (Active Storage → Amazon S3), cable (WebSockets), environments, initializers (e.g. Devise, Geocoder).
• Dockerfile.*, compose.yml, and render.yaml orchestrate containerization & deployment on Render; GitHub Actions for CI; Procfile.dev for local process management.
README
• Confirms the tech stack: Rails, Ruby 3.3.6, Turbo+Stimulus, Tailwind/DaisyUI, Google Maps API, PostgreSQL, S3, Render, Docker, GitHub Actions.