Koozali.org: home of the SME Server
Obsolete Releases => SME 7.x Contribs => Topic started by: smiit on April 15, 2009, 05:21:33 PM
-
Has anyone attempted to manually install or update to eGroupware 1.6 from the current SME contrib of version 1.4?
It looks like the dependencies for 1.6:
* minimum php 5.1+, recommended php5.2
* MySQL 5.0+
* Postgres 8.0+
will be in SME 8 so I'm inclined to wait rather than upgrade those packages on a stable 7.4 machine.
I've been looking for a good Groupware solution and am waiting to see if Zarafa comes along further or if eGroupware is the way to go since the 1.4 version integrates so well into SME.
Getting solid, attractive, secure (ssl is a must) shared calendar and contact functionality always seems very close but not quite ready for prime time.
-
I tried with standard SME4.7 and it didn't work, just an empty white page. So I tried running under php5-cgi (there is a howto somewhere) and I got the installation check which told me to install a module (I don't remember the name) only available for mysql5.
So, without upgrading to mysql5 and php5 I think there is no chance.
-
Upgrading to php5/mysql5 seems to be needed. Outlook's synch and Projects need them. php5-cgi does not cover all specs requested to run egw-1.6.
I did it on a couple of systems, and some yum updates will be problematic. In those cases, I revert to standard php/mysql, yum update and then upgrade to php5/mysql5.
If you can use sme8, it runs without any patch. I have many drupal sites (v.6) and egw 1.6 on sme8.
-
a little question...
i need install EGW 1.6 todo tests... i have some troubles.
have you install 1.6 from scratch or have you do an upgrade of an 1.4 ?
thnaks by advance
-
I prefer to install with subversion. Updates are then done with the same command. It might not be appropriate to work like this in case there is a problem during the download. The other way is to checkout in a temp folder and then replace the existing one.
cd /opt/egroupware
svn checkout http://svn.egroupware.org/egroupware/branches/1.6/aliases/default .
Files permission can then be easily changed with a script available on contribs:
#!/bin/sh
cd /opt/egroupware
# setperms
echo "...Setting file access rules :"
echo " - Changing owner recursivly..."
chown -R root:www /opt/egroupware/egroupware
echo " - Recursive CHMOD 550 on folders..."
find egroupware -type d -exec chmod 550 {} \;
echo " - Recursive CHMOD 440 on files..."
find egroupware -type f -exec chmod 440 {} \;
echo " - Customization of CHMOD for a few folders..."
chmod 770 /opt/egroupware/egroupware/phpgwapi/images
chown www /opt/egroupware/egroupware/header.inc.php
chmod 600 /opt/egroupware/egroupware/header.inc.php
echo "...Permissions Ok."
With php5/mysql5 upgrade (not php5-cgi), EGW will do outlook synch, projects, timesheets, tracker.
-
@soprom
I have many drupal sites (v.6)
Currently we are using SME 7.4. (8 comes later for us)
I have Drupal 6x in an ibay. If you also have D6 in ibays, how did you go about providing a public upload directory???
When I do "ibay reconfigure" the write perms are removed from /sites/default/files
Cheers
-
Drupal 6 works with sme7.4 but are you using "private directory path" ?
I didn't see this problem but drupal doc says to put it outside document root:
http://drupal.org/node/22240 (http://drupal.org/node/22240)
-
Drupal 6 works with sme7.4 but are you using "private directory path" ?
Yes
I didn't see this problem but drupal doc says to put it outside document root:
http://drupal.org/node/22240
This would be no prob if drupal is installed in /opt, but we have it in an ibay
Cheers
-
When I do "ibay reconfigure" the write perms are removed from /sites/default/files
Permissions are changed from which user to what new user?
(note that the subject was about "eGroupware 1.6 update")
-
Oops, hijacked the thread in a manner of speaking - apologies to you and the moderators (who will no doubt give me what for...) What now? I was just being curious with my first post to this thread.
To answer your question, I used the standard ibay setup:
Write=admin, Read=everyone. So I set the perms manually for /sites/default/files so that Drupal can write there, but if one were to, say restart the server for some reason, Drupal can no longer write to that path.
Cheers,