How codeandomexico/decidim-monterrey works
Project type and purpose
• This is a full-stack Ruby on Rails monolith customized from the Decidim open-source participatory democracy platform.
• Its purpose is to serve as the Decidim Monterrey site: a web platform where citizens can propose, debate, vote, submit forms, etc., backed by reusable Decidim engines (budgets, proposals, surveys, verifications, etc.) and a custom “ine” module for neighborhood data.
Top-level file structure and architectural clues
• app/: MVC code (controllers, models, views, cells, jobs, mailers, permissions, forms, helpers).
• config/: Rails config, routes, environments, initializers (Decidim, workflows, CarrierWave, OAuth, etc.).
• db/: CSV seed data, migrations (hundreds of Decidim engine migrations).
• lib/extensions/: Rails concerns and service overrides that plug into Decidim’s APIs (workflows, permissions, commands).
• decidim-module-ine/: A mountable Rails engine (controllers, models, views, uploaders, jobs, mailers, presenters, packs, lib/engine).
• omniauth-idmty/: A standalone OAuth strategy gem for authentication.
• docker/, docker-compose-*.yml: Containers for web, worker, database, and environment-specific setups.
• config/webpack & app/packs: Webpacker for JS/CSS asset bundling.
Extracted architecture from README
• Rails + Puma serve HTTP(S) requests, assets via Webpacker.
• Postgres (or configured RDBMS) stores all Decidim data + module data + user records.
• ActiveStorage or CarrierWave handles file uploads.
• Background jobs run via ActiveJob/Delayed Job.
• Emails sent with ActionMailer.
• OmniAuth-IDMTY handles external identity provider integration.
• Entire stack runs in Docker containers for consistency across environments.