On Tue, 21 Dec 1999, David Guerizec wrote:
> Here is what I mean:
>
> in httpd.conf, we just have one MidgardDatabase, MidgardUsername and
> MidgardPassword directive, which point to the 'midgard' meta-DB.
> in the 'midgard' meta-DB, we have several records corresponding to the
> 'normal' DBs and hosts
>
> example of meta-DB structure:
>
> id, hostname, port, auth, DBname, DBuser, DBpassword, Realm ...
You beat me to my addition :) Anyway, as I said, it brings a performance
hit.
> instead of repeating it for each new vhost and we could have a super-admin
> site to manage all the hosts
Actually, this was how Midgard was meant to work in the first place, but
within a single DB. The admin user would be the ISP, who can assign
modify (and soon read) permission to distinctive groups (different
customers perhaps).
I still like the idea you brought up, though, so I'll put in some thought
on how to bring the best of both worlds. One thing that springs to mind
is an extended MidgardDatabase parameter that would allow specification
of the servername it applies to (outside any vhost definition) but I
don't know if that'll help you any.
Bye,
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]
