Hi,
> Sounds Great! I will definitely be looking forward to seeing it. Right now
> it's a bit hazy. All I know is that I've had to edit the following tables:
>
> grp, host, member, person, sitegroups to get the SiteGroups to work for SG1.
> Then a made a whole new set of records within these same tables for SG0.
> What was interesting is that I had to have two separate host records for
> /admin. I ended up using www.mycomputer.com:8101 for SG1 and
> www.mycomputer:8099 for SG2. I'm assuming that each site group has to have a
> unique httpd.conf entry? Not possible to have multiple SiteGroups assigned
> to the same ip address, right?
Without having time to think about it, I really don't know what you've
done. The following is from the SG doc, "After adding the "sitegroup"
table and columns to the Midgard database, the new table is empty and the
fields for every record are set to 0. So all records in the database
default to the shared, read-only SG0. Because there's is no easy way to
migrate existing records into the new SiteGroup environment, we recommend
you begin by applying SiteGroups to new records."
This basically means, leave everything the way it is in the default
installation. When you build your new host, first create a new SG, log
into the new SG, create the host which then belongs to the new SG that
you logged into.
If you want the admin site to be available to your users it should be SG0.
This means it can be read but that nobody can modify it. This is probably
the most common way of using the admin site that ships with Midgard.
If you build custom admin sites, you would probably want them accessible
by the relative SiteGroup for whomever needs access to it. I don't think
you're intending to build custom admin sites. If your admin site is in any
SG, members of that SG will be able to modify the admin site, not what you
want. I'm guessing that your admin site should be SG0.
Also, maybe this is what you were trying to accomplish by adding admin
sites to multiple SGs, a user whois a member of a SG has their permissions
restricted to that SG. If a user requires membership in multiple SGs, you
must create an account for that person in each SG that they need
membership to. You can use the same name and pass combos in SG to simplify
things.
I'm sorry this SG stuff seems so confusing. Once you get the hang of it,
it's just like anything else...so simple you'll want to beat yourself
about the head with a welding torch. I hope I'm not confusing you or
misinterpreting what you're doing. If I am, have coffee and wait for
Emile, maybe?
Let me know
Ron
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
