I’ve got a Kratos deployment setup that seems to o...
# talk-kratos
p
I’ve got a Kratos deployment setup that seems to offer very basic multi-domain capabilities. Basically, 2 kratos stacks configured for different domains, but pointing at the same database. This seems to enable the 2 domains to have a shared user database. Of course, cookie sessions are still separated by domain. That’s ok for us right now. I’m wondering if there are any known side effects of having 2 different domain instances of kratos pointing at the same user database? Is there any known interference in this sort of configuration?
I’m seeing some issues with the Mail courier. Seems there’s supposed to only be one instance, and even if you run multiple, (one per domain), it’s a race for which one pulls the next message from the DB, so a reset email for
<http://domain1.com|domain1.com>
can be sent from
<http://domain2.com|domain2.com>
.
No way for the couriers to distinguish which domain an email is intended to be sent by.