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/ ]