added polish help files
[squirrelmail.git] / UPGRADE
CommitLineData
f4057b81 1Upgrading from 0.3 or 0.4
2=========================
2b996daf 3If you are upgrading from versions 0.3 or 0.4 of SquirrelMail, you can use
4this guide to make the transition a bit smoother. If you have been using a
5previous version (0.1 or 0.2), it is suggested that you just start from
6scratch and configure your settings as if it was your first install.
f4057b81 7
2b996daf 8NOTE: The new plugin architecture required the use of some functions which
9are not in all versions of PHP4. You will need at least PHP4 beta2. If you
10need to upgrade please go ahead and install the latest release version of
11PHP4.
f4057b81 12
131. Backups
14===========
2b996daf 15
16Make a backup of your current SquirrelMail directory. If you use "cp", be
17sure to use the "-Rp" options. -R means recursive, and -p will save the
18permissions in the directory. In this example, we assume that your httpd
19document directory is /home/httpd/html.
f4057b81 20
21 $ cd /home/httpd/html
22 $ cp -Rp squirrelmail-0.4 squirrelmail-0.4.bak
23
24
252. Unarchives Squirrelmail-0.5.tar.gz
26======================================
2b996daf 27Make sure that you're in your httpd document directory (/home/httpd/html)
28and then unarchive the squirrelmail archive (whatever the filename is):
29
f4057b81 30 $ tar -zxvf squirrelmail-0.5.tar.gz
31
32
333. Copy backups in place
34=========================
35Here is the main part. There are two parts to this step: copy preferences,
2b996daf 36and copy config details. The preference files are backwards compatible, so
37it is fine to copy the old user preferences into the new directory.
38However, the configuration file has changed quite a bit, so you will want to
39be sure to run the configure script (conf.pl) to set up any new config
40details.
f4057b81 41
42First, copy the files in place:
43
44 $ cp squirrelmail-0.4.bak/data/* squirrelmail-0.5/data
45 $ cp squirrelmail-0.4.bak/config/config.php squirrelmail-0.5/config
46
47Note that if at all possible, start the configuration process from scratch.
48It is less prone to missing configuration options than copying your old
49configuration. The ideal solution would be to copy your users' preference
50files, and then run conf.pl to re-configure SquirrelMail (without using the
51old config file). If you do copy the config.php file, you will want to run
52conf.pl and check for new options.
53
54
554. Change permissions
56======================
57The web server must have write permission to the data directory. In this
58example, we assume that user "nobody" and group "nobody" are the web server
59as is often the case with Apache.
60
61 $ cd squirrelmail-0.5
62 $ chown -R nobody.nobody data
63
64
655. DONE!
66=========
2b996daf 67That should be all! The most important part is copying your users'
68preference files back into the new data directory. This will insure that
69your users will have their old preferences.