Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multitenancy, approach #1 #121

Closed
wants to merge 3 commits into from
Closed

Multitenancy, approach #1 #121

wants to merge 3 commits into from

Conversation

FZambia
Copy link
Member

@FZambia FZambia commented Jun 3, 2020

This is the first approach for multitenancy for different installations of the same app. Relates to #113

There are a lot of possible ways to solve actually. This one seems the most straightforward to me at moment.

So what changed here?

  1. Define option ChannelEnvDelimiters to sth like []
  2. Include env string as JWT claim or return in Credentials, for example "env": "site_01.com"
  3. After this client will only be able to subscribe or publish to [site_01.com]namespace:channel - i.e. only to channels that start with its environment.
  4. [site_01.com] won't affect namespace configuration

@FZambia
Copy link
Member Author

FZambia commented Jul 6, 2020

Closing in favour of #129

@FZambia FZambia closed this Jul 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant