Experience with multi-tenancy and AlchemyCMS

[jasonbouffard]

Does anyone have any experience running Alchemy in a multi-tenant scenario?

We've got a web application that is currently multi-tenant simply based on a 'user-group' design. We're looking to integrate CMS capabilities based on group access and are considering AlchemyCMS. Would love to hear any opinions or experiences in running Alchemy in this manner.

We're also open to other options via gems like these running alongside Alchemy:

• row based - https://github.com/ErwinM/acts_as_tenant
• schema based - https://github.com/rails-on-services/apartment

[tvdeyen]

Alchemy's top-level tenant is the Alchemy::Site. All languages and their pages are connected to a site (aka domain). So, you would need to scope alchemy_sites to your "user-group" model.

One caveat though is that tags, pictures and attachments are not scoped by site. If you want to restrict what people have access to you would need to add an account_id or user_group_id to alchemy_pictures and gutentag_tags and add a default scope to the models ensuring they are always scoped by it.