Question 1

How do I switch tenants in a Milia Rails app?

Accepted Answer

Use set_current_tenant(tenant_id) in controllers for user-initiated switches, but note Milia handles this automatically during authentication. For background jobs, use Tenant.set_current_tenant, as detailed in the API reference.

Question 2

Milia vs Apartment gem: which is better for multi-tenancy?

Accepted Answer

Milia uses row-based tenancy with Devise integration, ideal for shared database setups with simpler isolation. Apartment supports schema-based tenancy, better for strict data separation. Choose based on your isolation needs and authentication stack.

Question 3

Can I use Milia without Devise authentication?

Accepted Answer

It's challenging because Milia is designed to work out-of-the-box with Devise. You'd need to manually override authentication callbacks and integrate your own auth system, which increases complexity and risk.

Question 4

What's the best way to test multi-tenancy with Milia?

Accepted Answer

Set up tenant-specific test data using Tenant.set_current_tenant in test setups. The README mentions testing guidelines in a separate file, but ensure you mock tenant contexts to avoid cross-tenant contamination.

Question 5

How to handle tenant data migration in Milia?

Accepted Answer

Iterate over tenants with Tenant.find_each and set_current_tenant for each, then run migrations per tenant. This ensures data is scoped correctly, as shown in the API's iteration example.

Question 6

Is Milia safe for production with sensitive data?

Accepted Answer

Yes, but with caveats: it enforces row-based security, but SQL outside ActiveRecord isn't tenant-scoped. Perform thorough security audits, as the README warns, and avoid manual tenant_id modifications.

Milia

What is Milia?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions