From: Jason B. <jas...@mi...> - 2006-09-29 12:51:49
|
> 0) Setup mysql, apache, etc (out of egw scope) and have those services > started. At least, make sure the user you specified for egw db has the > necessary privileges (the db can be blank or not exist). You can find this > info in the header.inc.php. If you change it, you'll need to enter header / > Admin later to change accordingly. For this test server, I just shut down MySQL on the production server for a moment, and tarred up the entire /var/lib/mysql. That got me all relevant databases, users, permissions, etc. > Just add that the path is an apache setting, not a fixed one, and depends on > the operating system or distro and personal needs about how to access > egroupware. Yeah, I just follow (one) Redhat convention for using /var/www/html to store Apache files. > Also, make sure the webserver owns the tree. As last point, if > some core change or upgrade (for instance, higher php o mysql versions) has > taken place in the new server, you might need to enter Header / Admin to > update th0se settings before going on. Basics like proper file ownership are in my own eGW setup docs. And I have, in the past, missed the possible need to change the header stuff when migrating an eGW install. > 5b) Restore additional sites accordingly, together with LDAP, if used. Not using LDAP yet, but experimenting with it now. (The open-sourced Fedora Directory Server -- anyone have better suggestions than that for LDAP?) > 6) Restore the last backup from /setup Since this install is still 1.0.0.009, I don't think I have a backup option yet. Thanks again, guys! --Jason Byrns |