Hi again,
> I am using SuSE 8.0 with Apache 1.3.26 and the latest
> PHP and Midgard. I did a source installation because
Apache and Midgard and SuSE 8.0 are ok. But you will probably run into some
troubles with several packages of the standart SuSE 8.0 distri if you try to
compile midgard from source:
1. Newest PHP could be a little tricky. Look at the user-list for that or
downgrade to php version < 2.xx.
2. according to www.olav.net glibc-2.2.5-105 (as included in SuSE 8) could
make trouble. Better install the previous version from SuSE 7.3 (can be
found on suse ftp server).
3. Note That ALL devel packages should be installed (apache-devel
mysql-devel...)
4. look at OLAV.net on what glib and expat to install, also please check if
gcc and flex are installed
5. autoconf and automake versions of SuSE >7.3 gave me problems when
installing.
Using autoconf 2.13 and automake 1.4 worked for me.
Also make sure libtool is installed (I use version 1.3.5).
6. Again: I never got the midgard.rpm to work, so I would strongly urge you
to use the sources from www.midgard-project.org
7. If you plan to use NADMIN download the patches and apply them before
compiling midgard.
> Midgard did not work at first as compiled in, but when
> I removed the rpm, it took the Apache init.d script
> and I couldn't find a copy that I was smart enough to
> get to work with this installation.
I don't get this part... But SuSE has an easy way to restart apache: use
rcapache [start|stop|restart] from anywhere...
>I tried starting
> and stopping manually for a while, but I am working on
> a laptop which is shutdown frequently for transport
> and I was forever forget to cut Apache on or off.
>
> I put the rpms back in, and surprisingly, they worked.
You mean apache or midgard?
> (My experience with rpms and modules has not been
> good.) However, though some funky mechanism, I have
> yet to completely figure out, SuSE has made it
> possible to roll in a whole bunch of modules like
> mod_perl, ssl, JServe, php, zope, midgard, xml, etc.
You can simply uninstall the modules you don't need.
For midgard to work you may leave mod_php. I also hav mod-perl installed.
Most others are optional.
Mod_ssl has come under attack, since there is a trojan out there using a
hole in modssl. So unless you really need mod_ssl I would uninstall it.
> that are a pain to combine altogether. And they all
> work, except for Midgard, which I think would work if
> I could get the databases constructed.
Hmm, maybe...
>
> I am assuming ./dbinstall would do that if I could
> find where to run it, but I tried running it in every
> directory midgard appeared to no avail.
well to find it, just run: updatedb; locate -e dbinstall;
This should give you the exact location.
cd to the directory the dbinstall-script is located in.
Before you run the script, you will have to configure it:
mkdir -p /var/www/{blobs,cache}; #creates directories for pictures and
caching
./configure --with-db-admin-user=root
--with-db-admin-password='password for mysql'
--with-host=[my.host.name]
--with-ip=[my.ip.in.here]
--with-blobdir=/var/www/blobs --with-pagecache=/var/www/cache
--with-midgard=/usr/local/midgard/bin/midgard-config # might be different
path,
#look for
midgard-config using locate -e midgard-config
--with-apxs=/usr/sbin/apxs
--with-apache-user=wwwrun
--with-apache-group=nogroup
--with-asgard
--with-php=4
--with-install=new;
Now midgard-database can be installed using ./dbinstall;
> I couldn't find anything on the Midgard site, but I do
> read German so I'll take a look at the site you
> offered. If you have any further ideas, I'd love to
> hear them. LD
Hope I could help,
med-men
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
