intranet/extranet combo - good idea?
Hi, I'll be developing both an intranet and an extranet for a client (a church). Now, I'm thinking of doing this with subdomains and a common codebase, like: www.churchname.com intranet.churchpage.com This would enable single logins for the staff, but I'm curious if this the way to go as I haven't really found a lot of info about these kinds of setups on drupal.org. is this a good way to do it, or do you think I will run into too many problems regarding security and other stuff? Is it better to separate the intra- and extranets? thanks! Morten
Morten, I've done two different sites that do Intranet and Extranets on the same Drupal installation/ same database with no subdomains. As with just about everything in Drupal there are many ways to do the same thing. On one site I use Taxonomy Access Control and on the other site I use Content Access. I would recommend using Content Access; that combined with the built-in ability regarding "roles" and you've got all you need. With content Access you create content types specifically for viewing only on the Intranet. So you create a new content type called "Staff Post" for instance which has all the same fields as a "Story" but because it is its own Content Type you have more control over when it shows up. You'll have to have Views installed as well (sometimes I forget that isn't part of core since I use it in every Drupal install that I do) so that you can create an Intranet home page. Feel free to ask more details if you end up taking one of these routes. Shai On 9/7/07, Morten Holmstrup <morten@holmstrups.dk> wrote:
Hi,
I'll be developing both an intranet and an extranet for a client (a church).
Now, I'm thinking of doing this with subdomains and a common codebase, like:
www.churchname.com intranet.churchpage.com
This would enable single logins for the staff, but I'm curious if this the way to go as I haven't really found a lot of info about these kinds of setups on drupal.org.
is this a good way to do it, or do you think I will run into too many problems regarding security and other stuff? Is it better to separate the intra- and extranets?
thanks! Morten
-- [ Drupal support list | http://lists.drupal.org/ ]
I'll be developing both an intranet and an extranet for a client (a church).
Now, I'm thinking of doing this with subdomains and a common codebase, like:
www.churchname.com intranet.churchpage.com
This would enable single logins for the staff, but I'm curious if this the way to go as I haven't really found a lot of info about these kinds of setups on drupal.org.
is this a good way to do it, or do you think I will run into too many problems regarding security and other stuff? Is it better to separate the intra- and extranets?
The simplest at this point would probably be to share a filesystem, if you want, but have different databases, then set up single signon. Splitting one site across several domains or subdomains can be complicated. The multidomain module does this, ostensibly, but can be rather tricky to configure. If you do SSO in the arrangement you say, you wlll want to watch out for cookie collisions. Laura
Laura and Shai, thanks a lot for your suggestions! I think I'll go with separate installations then, as this seems the easiest way and I really dont have the nerves to risk potential showstoppers along the way. cheers Morten
The simplest at this point would probably be to share a filesystem, if you want, but have different databases, then set up single signon. Splitting one site across several domains or subdomains can be complicated. The multidomain module does this, ostensibly, but can be rather tricky to configure.
If you do SSO in the arrangement you say, you wlll want to watch out for cookie collisions.
Laura
Would it work to use Organic Groups and just have the intranet part be private groups on one site? Jean On 9/9/07, Morten Holmstrup <morten@holmstrups.dk> wrote:
Laura and Shai,
thanks a lot for your suggestions! I think I'll go with separate installations then, as this seems the easiest way and I really dont have the nerves to risk potential showstoppers along the way.
cheers Morten
The simplest at this point would probably be to share a filesystem, if you want, but have different databases, then set up single signon. Splitting one site across several domains or subdomains can be complicated. The multidomain module does this, ostensibly, but can be rather tricky to configure.
If you do SSO in the arrangement you say, you wlll want to watch out for cookie collisions.
Laura
-- [ Drupal support list | http://lists.drupal.org/ ]
-- Jean Gazis www.jeangazis.com www.boxofrain.us "Believe those who are seeking the truth; doubt those who find it." - André Gide
Jean, Morten, and all, I've used Organic Groups, Taxonomy Access Control and Content Access, and I think, all other things being equal, that Content Access is the simplest of the three, especially for a beginner. I find organic groups fairly easy to use when groups are public but pretty complicated and confusing when trying to pull off private groups. I also think that if Morten is a beginner, it's not a bad idea to use separate installations, as he has concluded. I would use a different theme for each site or use Garland with different color schemes so that staff really understand that the sites are different and won't get confused about logging in etc... on the different sites. Shai On 9/9/07, Jean Gazis <jgazis@gmail.com> wrote:
Would it work to use Organic Groups and just have the intranet part be private groups on one site?
Jean
On 9/9/07, Morten Holmstrup < morten@holmstrups.dk> wrote:
Laura and Shai,
thanks a lot for your suggestions! I think I'll go with separate installations then, as this seems the easiest way and I really dont have the nerves to risk potential showstoppers along the way.
cheers Morten
The simplest at this point would probably be to share a filesystem, if you want, but have different databases, then set up single signon. Splitting one site across several domains or subdomains can be complicated. The multidomain module does this, ostensibly, but can be rather tricky to configure.
If you do SSO in the arrangement you say, you wlll want to watch out for cookie collisions.
Laura
-- [ Drupal support list | http://lists.drupal.org/ ]
-- Jean Gazis www.jeangazis.com www.boxofrain.us
"Believe those who are seeking the truth; doubt those who find it." - André Gide -- [ Drupal support list | http://lists.drupal.org/ ]
participants (4)
-
Jean Gazis -
Laura Scott -
Morten Holmstrup -
Shai Gluskin