"John P . Looney" wrote:
> If it does match, and the database is being accessed by apache, then it
> could be that the admin files could be missing (/asgard doesn't have any
> files on disk though I think /admin does) - so it could be a problem with
> whatever is in that /admin directory in your ServerRoot.
Sorry to step in so late, but the complaint 'database not defined for
...'
actually means that the virtualhost does not appear to have a
MidgardDatabase
directive. If you see this error, no actual connection to the database
has
been established. I'd like to see the full entries for the VirtualHosts
-- passwords masked out of course.
pp <[EMAIL PROTECTED]> wrote:
> Look , Matthias has the same problem ( or I did't understood clearly).
> He use debian , so do I.
> Is it debian bug or midgard is so REdHat oriented? ;))
There's nothing specifically debian-unfriendly about Midgard, although
I haven't checked the installation process of late. I actually use
Mandrake
for main development, and swap some partitions between solaris, debian,
BSDs, or whatever comes my way. The SF compilation farm doesn't cut it
since
that certainly doesn't cover everything, plus you can't install all the
dependencies that you need.
SO:
If anyone has a installation problem that you think is
platform/distribution
related, and you happen to have a box handy that I can log in to (and
that's
NOT a production machine -- I'll need root-equivalency and I'll most
likely
install or break stuff along the way), let me know. I'm scrounging
around for
a scratch box which will make it easier to swap platforms, but I don't
really
want to scratch my main machine or my laptop.
Emile
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
