React-boilerplate: Multi Tenant (theming)

Created on 13 Jul 2016  Â·  2Comments  Â·  Source: react-boilerplate/react-boilerplate

Hello all

I'm really enjoying working with the boilerplate so far, it's a great blend of simplicity and capability.

The question I'm wondering about is, what would be the simplest path towards using this for a multi tenant environment?

Here's my basic requirements:

  • To have a default app with pages, components and containers
  • To be able to additionally include CSS and custom components for another domain, but within the same codebase
  • To be able to work in any tenant in dev, and then use npm run build <tenant_name>

I'm already using this thread to implement variables for use in JS and CSS, so I'm wondering if the simplest path is individual webpack config files for each tenant. I'm not sure if I'd need to then go on to use separate entry point files for each tenant.

Another thought I had was to possibly use node environment variables, although I'm not sure if this would scale well.

Any thoughts or suggestions greatly appreciated!

question

All 2 comments

I think you'd want to go with a separate entry point for each tenant, otherwise you'll end up copy-and-pasting the webpack config _a lot_.

I'll close this issue for now – hope you can figure it out!

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

hieubq90 picture hieubq90  Â·  3Comments

VadimuZz picture VadimuZz  Â·  4Comments

avdeev picture avdeev  Â·  3Comments

fobus42 picture fobus42  Â·  3Comments

joehua87 picture joehua87  Â·  3Comments