rails new MultiTenancy -d=postgresqlbundle exec rails generate scaffold Home tagline:stringbundle exec rails generate scaffold Message text:stringbundle exec rails generate scaffold Tenant subdomain:stringbundle exec rake db:drop db:create db:migratelayouts/_header.html.erb
<nav class="navbar navbar-expand-lg navbar-light bg-light">
<div class="container-fluid">
<a class="navbar-brand" href="<%= homes_path %>">Home</a>
<a class="navbar-brand" href="<%= messages_path %>">Messages</a>
</div>
</nav>layouts/application.html.erb
<body>
<%= render "layouts/header" %>
<%= yield %>
</body>config/routes.rb
root "homes#index"config/environments/development.rb
config.hosts << "lvh.me"Addition to gem file:
gem 'ros-apartment', require: 'apartment' # works with rails 7bundle exec rails generate apartment:installIn a rails console:
Apartment::Tenant.create('glitzy')bundle exec rails generate scaffold User email tenant:referencesWith apartment setup, there is no need for "references" to a tenant. This next scaffold automatically works because it is not in the exclusion list in the apartment.rb initializer.
bundle exec rails generate scaffold Projects titlehttps://gorails.com/episodes/multitenancy-with-apartment?autoplay=1
Each PostgreSQL schema has the same tables as any other. Only by looking at the apartment initalizer exclusions can anyone know which tables are tenant specific.
Ideally there would be a single "shared" schema and a schema for each tenant. This would allow the database to be more easily understood by a database administrator.