Changes

This is taken from an email sent by John to the dev discussion list, which may well contain useful information about configuring the system for testing:

This is taken from an email sent by John to the dev discussion list, which may well contain useful information about configuring the system for testing:

I personally didn't install the e-smith-horde,ingo,imp,turba packages, as those were built for horde 3, and I hadn't tested whether horde would even load using those files.  I saw that some of updated horde files were going to be installed, because someone changed the dependency to Requires: horde >= 3.2, which tries to pull them from the centos repo.

I personally didn't install the e-smith-horde,ingo,imp,turba packages, as those were built for horde 3, and I hadn't tested whether horde would even load using those files.  I saw that some of updated horde files were going to be installed, because someone changed the dependency to Requires: horde >= 3.2, which tries to pull them from the centos repo.

I tested what I have built and been using.  They loaded fine, and brought in all of the other dependencies.

I tested what I have built and been using.  They loaded fine, and brought in all of the other dependencies.

Webserver wasn't working, enabled it using:

Webserver wasn't working, enabled it using:

  service httpd start or /bin/systemctl start  httpd.service

  service httpd start or /bin/systemctl start  httpd.service

Permanently enable using:

Permanently enable using:

  systemctl enable httpd

  systemctl enable httpd

Couldn't access webserver.

Couldn't access webserver.

Also need to stop firewalld for now as well using:

Also need to stop firewalld for now as well using:

  service firewalld stop or /bin/systemctl stop  firewalld.service

  service firewalld stop or /bin/systemctl stop  firewalld.service

For testing, I just disabled it permanently using:

For testing, I just disabled it permanently using:

  /bin/systemctl disable firewalld.service

  /bin/systemctl disable firewalld.service

to renable:

to renable:

  /bin/systemctl enable firewalld.service

  /bin/systemctl enable firewalld.service

I am now able to access the webserver.  Note, I put a sample index.html in the doc root to verify.

I am now able to access the webserver.  Note, I put a sample index.html in the doc root to verify.

I saved a copy of a good httpd.conf, then I did an expand-template /etc/httpd/conf/httpd.conf so that all of the horde information would be there.  Re-starting httpd threw an error out, as expected.

I saved a copy of a good httpd.conf, then I did an expand-template /etc/httpd/conf/httpd.conf so that all of the horde information would be there.  Re-starting httpd threw an error out, as expected.

I manually changed /etc/httpd/conf.d/ssl.conf and added the alias info.  Then manually changed httpd.conf and added all of the horde <Directory parameters, and remarked out the <directory stanzas that deny access to the whole server filesystem.  Lines 102-105 for me.  Didn't want to waste any additional time figuring out what needs to be really  done at this time.

I manually changed /etc/httpd/conf.d/ssl.conf and added the alias info.  Then manually changed httpd.conf and added all of the horde <Directory parameters, and remarked out the <directory stanzas that deny access to the whole server filesystem.  Lines 102-105 for me.  Didn't want to waste any additional time figuring out what needs to be really  done at this time.

Restarted httpd, then went to webmail, and the page appeared.

Now on to mariabd.

Restarted httpd, then went to webmail, and the page appeared.

Enabled using:

 

Enabled using:

  systemctl enable mariadb

  systemctl enable mariadb

  cd /etc/e-smith/templates/etc/e-smith/sql/init/ and started to manually run all of the horde-related scripts.

  cd /etc/e-smith/templates/etc/e-smith/sql/init/ and started to manually run all of the horde-related scripts.

== Notes ==

== Notes ==