Each site starts off as an independent Drupal install, running off a single shared code base (using Drupal's multi-site feature).

I have a client who doesn't wish to blend sites into a multisite at this time (though it would make good sense soon enough). I set out to do set up sso with multiple codebases, though blended the databases and prefixed the tables into a single db.

Everything is working fine and as it should.

Am I missing something? Is the multisite a requirement or makes-it-easier-to-set-up suggestion?

Thanks.

Comments

brst t’s picture

brst t commented

Elaborating.

Works easily enough with two sites -- one is the controller the other is the client. Additional sites after that yield '>1 installed modules' type error messages.

Staying with the no multisite, symlinks make for an easy workaround. The client sites/all/modules/sso link to the controller sites/all/modules/sso. The rest of the README instructions still follow.

So, for both cases, I have prefixed the database tables per installation. Analogous to a multisite, but still separate codebases.

1) For a pair of sites, multisite not req'd. One is contoller only. The other site is client only.
2) For more than two sites, multisite can be sidestepped by symlinking the clients' sites/all/modules/sso to the controller's.

Again with the so far so good. 'Everything is working fine and as it should.'

And yeah, a multisite is still the easier route to proceed.

'Each site starts off as an independent Drupal install, running off a single shared code base (using Drupal's multi-site feature).'

Not sure how to edit or reword this at the moment, but it'd be good to include some note of the potential of 1) and 2) above.