deployment

Deploy Rails applications across test, staging, and production environments using environment-specific tools: Kamal for test, Fly.io for staging and production, and Git hooks for admin. Each environment runs separate Rails instances managed by Navigator or Passenger, with routing handled through a centralized architecture supporting multi-tenant isolation.

Multi-tenancy architecture isolates each tenant (event) as a separate Rails instance with its own SQLite database, while sharing a Redis instance for real-time Action Cable updates. This approach provides data isolation, independent scaling, and simplified per-tenant backups across Fly.io regions.

Yes. Kamal handles test environment deployments, while Fly.io manages staging and production with multi-region support, automatic rsync backups, and region-aware routing. This combination provides environment-specific optimization and centralized cross-region replication for production reliability.

Configure Fly.io multi-region setup with automatic rsync backups, PDF generation appliances, and Action Cable for real-time updates. Region-aware routing distributes traffic intelligently, while centralized logging tracks deployments across all regions for monitoring and troubleshooting.

Navigator and Phusion Passenger manage multiple Rails instances in production, while NGINX handles routing between them. Kamal orchestrates test deployments, Fly.io manages staging and production infrastructure, and Redis supports real-time communication via Action Cable.

Yes. The architecture includes automatic rsync backups for each event's SQLite database and centralized logging across all environments. Multi-region replication on Fly.io provides disaster recovery and redundancy for production data.