Multi site Support

[suresh-kumar-ogilvy]

Hi Good day

Does this package support multisite drupal installation(separate database)?
In other words, every domain has its own .env file so we can load the different content by site same source code.

Thanks

[shadcn]

Yes. You can use one Drupal back-end and have multiple Next.js front-ends.

All the examples in the /examples dir are actually built from one Drupal site.

[suresh-kumar-ogilvy]

Thanks, @shadcn I Understand. We are thinking of rolling out around 20 sub-sites from one central site. is there a way to load the env config per domain/host? then don't need to set up 20 front-end servers.

[shadcn]

do you mean for the DrupalClient?

You should be able to do something like this:

const baseUrl = doSomethingToRetrieveBaseUrl()
export const drupal = new DrupalClient(baseUrl)

[suresh-kumar-ogilvy]

yes something like this , based on host

[shadcn]

Yeah you should be able to do this.

Another solution you could explore is having a Next.js site that acts as a server between your clients and Drupal.

All your clients talk to this proxy and this proxy decides what config/data to send based on the host.

[suresh-kumar-ogilvy]

Thank you for the detailed info.
I assume all the next.js "Site x" will send some kind of unique token i.e host (since all custom domains will be hosted in one instance) to the API server and then the API server connects with drupal.

[shadcn]

Yeah. You can also use the request headers.

[suresh-kumar-ogilvy]

Thank you, since we are using the hostname as a unique key [[...slug]].tsx must use getServerSideProps to fetch the hostname?

is there any other way to fetch the hostname?

I did try this example https://github.com/vercel/examples/tree/main/edge-functions/hostname-rewrites some reason it doesn't support [[...slug].tsx

[shadcn]

@suresh-kumar-ogilvy What does your setup look like? Are you fetching data directly from Drupal?

[suresh-kumar-ogilvy]

yes, created a drupal custom module to get config by hostname
I did try using the API server but couldn't able to fetch the hostname from "Site A" if using getStaticPaths

[sing78]

I am also interested in Drupal/Next.js/multisite (one drupal installation,many Next.js front-end sites,multiple databases)
Is this possible a guide to be written?
Thanks

[shadcn]

@sing78 Sure. Can you provide some more details about your architecture? Are you using Drupal in multi-site mode?

[sing78]

Hi,
I have to create multiple identical sites(same configuration, same theme, same content types but different content and users) with drupal and Next.js.
My first questions is:Do I need to create multiple databases or can I use a single database for all sites and if yes how?
If I use multiple databases, one drupal installation, and many Next.js front ends, how can I accomplish this?
Please provide as many details as possible and if possible useful links,
thanks

[theodorosploumis]

@sing78 What you need is:

• One codebase for the Backend (Drupal code, including configuration)
• One codebase for the Frontend (NextJS) but with different .env files for each frontend site
• Multiple databases for each site

In fact, this is a normal Drupal multisite.

The only important thing you have to decide is if every site is going to share the same Drupal configuration or not.