On Fri, 14 Apr 2000, Armand A. Verstappen wrote:
> I've installed a sitegroup aware midgard, and created a sitegroup named
> 'envida'
>
> INSERT INTO sitegroups (name) values ("envida");
>
> I used the relog button on the updated admin interface and login in with
>
> admin*envida, using the appropriate password.
>
> Created a new host, new group and a new user. made the user member of the
> new group. The group nr. turned out to be 4. so:
>
> UPDATE sitegroups set admingroup=4;
>
> I can now login as the new user+envida, and I am told that I am logged into
> sitegroup envida at adminstrative level.
This is exactly how it works at the moment. In fact, I think this
description deserves a place in the manual while the admin site lacks SG
functionality, although I would quantify which sitegroup you want to set
the admingroup for. The above works if you have one sitegroup.
> I can see all the other sites that
> are configured, also the ones that are in SG0. Is this how it's supposed to
> be? I assumed other hosts would be hidden from view. I cannot change the
> ohter sites.
Whether this is how it's supposed to be is for you, the user, to decide.
I'm open to suggestions. This is how it works currently, yes. All content
in SG0 will be available to all sites, read-only. You are not supposed to
see sites other than those in SG0 or your own sitegroup.
I realize SiteGroups can be used to attain a level of confidentiality for
non-root users. The SG0 resources can not be confidential in the current
concept.
Emile
--
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]
