Question 1

How to switch tenants based on custom logic in Apartment?

Accepted Answer

Subclass the Generic elevator and implement a parse_tenant_name method that returns the tenant name from the request. The README provides an example using a custom middleware to handle dynamic switching based on request parameters.

Question 2

Apartment vs ActsAsTenant for Rails multi-tenancy?

Accepted Answer

Apartment excels with PostgreSQL schemas and scalable multi-database setups, offering better performance for large SaaS apps. ActsAsTenant is simpler, using a scoping approach ideal for single-database apps with less isolation overhead.

Question 3

Does Apartment work with MySQL databases?

Accepted Answer

Yes, but without PostgreSQL schema support, it uses separate databases per tenant, which can be less efficient. The README notes it's compatible but primarily optimized for PostgreSQL, requiring additional configuration for MySQL.

Question 4

How to handle background jobs with Apartment?

Accepted Answer

Use companion gems like apartment-sidekiq or apartment-activejob, which integrate Apartment with background job systems to maintain tenant context during asynchronous processing, as mentioned in the README's background workers section.

Question 5

How to fix memory issues in Apartment with ActiveRecord 4.x?

Accepted Answer

Upgrade to ActiveRecord 4.2.2 or later, or apply the memfix patch from the README by using a specific Rails version from GitHub, as the issue stems from PostgreSQL data type mapping bugs in older ActiveRecord.

Question 6

Setting up Apartment on Heroku with PostgreSQL extensions?

Accepted Answer

Configure persistent schemas like shared_extensions in the initializer and set schema_search_path in database.yml to include them. The README details steps for installing extensions and ensuring compatibility on Heroku.

Apartment

What is Apartment?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions