When engineering a new SaaS app, how you plan to handle customer data tenancy is usually one of the first decisions you and your team will need to ...
For further actions, you may consider blocking this person and/or reporting abuse
Should this
be
?
You are correct! Fixed.
Awesome, am borrowing (stealing, whatever) it for Rails 7 Jumpstart themes at
github.com/xhostcom/rails-jumpstar...
Muchos Gracias, and may the forces of evil become extremely confused on the way to your house.
Nice write up!
Since github.com/rails/rails/pull/46522 you don't need the
optional: true
One thing though if the new user has not signed up yet, can not set an account, or account_id, get error You must set an account with Current.account=
Needs workaround for that.
Two possible options to consider:
Hello,
Any further updates on scaling multi tenant ?
Don't forget to check out github.com/ErwinM/acts_as_tenant 👍
After including the concern i cant even initialise my registration form because it raises Current::MissingCurrentAccount.
Is there a way around it?
Do you use factory_bot for testing? How do you manage it in your test suite?