From 2ad55f0fcbafc0f160fabaa63b9089b0b3fff9ec Mon Sep 17 00:00:00 2001 From: Aaron Walker Date: Sat, 9 Jul 2005 12:48:54 +0000 Subject: Update postinstall-en.txt with upgrade information from upstream's upgrade doc. Package-Manager: portage-2.0.51.22-r1 --- www-apps/phpwebsite/ChangeLog | 5 +- www-apps/phpwebsite/Manifest | 28 ++++--- www-apps/phpwebsite/files/postinstall-en.txt | 113 +++++++++++++++++++++++++++ 3 files changed, 136 insertions(+), 10 deletions(-) (limited to 'www-apps/phpwebsite') diff --git a/www-apps/phpwebsite/ChangeLog b/www-apps/phpwebsite/ChangeLog index ce25794b6ee2..10778de7f135 100644 --- a/www-apps/phpwebsite/ChangeLog +++ b/www-apps/phpwebsite/ChangeLog @@ -1,6 +1,9 @@ # ChangeLog for www-apps/phpwebsite # Copyright 2000-2005 Gentoo Foundation; Distributed under the GPL v2 -# $Header: /var/cvsroot/gentoo-x86/www-apps/phpwebsite/ChangeLog,v 1.31 2005/07/09 01:08:59 weeve Exp $ +# $Header: /var/cvsroot/gentoo-x86/www-apps/phpwebsite/ChangeLog,v 1.32 2005/07/09 12:48:54 ka0ttic Exp $ + + 09 Jul 2005; Aaron Walker files/postinstall-en.txt: + Update postinstall-en.txt with upgrade information from upstream's upgrade doc. 09 Jul 2005; Jason Wever phpwebsite-0.10.1-r1.ebuild: Stable on SPARC wrt security bug #97461. diff --git a/www-apps/phpwebsite/Manifest b/www-apps/phpwebsite/Manifest index 65aa5c3a5d21..be44228896a8 100644 --- a/www-apps/phpwebsite/Manifest +++ b/www-apps/phpwebsite/Manifest @@ -1,18 +1,28 @@ -MD5 fd4c4199e7af20ae9b4b8b71d8349413 ChangeLog 6932 -MD5 24a724cdfd1390bba450f4b7c1a9dfc5 metadata.xml 360 -MD5 2605b5e8abb079f71b12202c38a8f86d phpwebsite-0.10.0-r1.ebuild 1616 +-----BEGIN PGP SIGNED MESSAGE----- +Hash: SHA1 + MD5 d1a2bc5cc4c9b25bfe5c58827fc477c8 phpwebsite-0.10.0-r2.ebuild 1734 +MD5 8b5fd42c34b5e4842d1299862927ee60 phpwebsite-0.10.1-r1.ebuild 1644 MD5 4f03dd69be734fbd9aa2969d30ebb2c2 phpwebsite-0.10.0.ebuild 1433 -MD5 41dbaed8aafa97c8930480adc9d77c58 phpwebsite-0.9.3_p4-r1.ebuild 1636 +MD5 2605b5e8abb079f71b12202c38a8f86d phpwebsite-0.10.0-r1.ebuild 1616 MD5 c9b0b64992415f435bb5cf0b8f603435 phpwebsite-0.9.3_p4-r2.ebuild 1853 MD5 5f35aa74e4a7118aa8b830cff357a04c phpwebsite-0.10.0-r3.ebuild 1905 -MD5 8b5fd42c34b5e4842d1299862927ee60 phpwebsite-0.10.1-r1.ebuild 1644 +MD5 41dbaed8aafa97c8930480adc9d77c58 phpwebsite-0.9.3_p4-r1.ebuild 1636 +MD5 b7afa1975844c705b106f0e0b0adc67d ChangeLog 7092 +MD5 24a724cdfd1390bba450f4b7c1a9dfc5 metadata.xml 360 +MD5 823ff723bde0deb5142a1753183467fd files/digest-phpwebsite-0.9.3_p4-r1 157 +MD5 6ddbbfb4f4e1e5c4d8bf717835d3c2d8 files/digest-phpwebsite-0.9.3_p4-r2 239 +MD5 87c3729bfda5e5188af3f0df1fcda7e7 files/postinstall-en.txt 4637 +MD5 0f181e50286192df906dd979448e0fd5 files/phpwebsite-0.10.0-xml-rpc.diff 1188 MD5 dab689c75fd084b695c69c427aa758b8 files/digest-phpwebsite-0.10.0 75 MD5 e328ec89d9602d614fbf60f87988f218 files/digest-phpwebsite-0.10.0-r1 147 MD5 c50eef019c793463d0818d3fe35b46f4 files/digest-phpwebsite-0.10.0-r2 221 -MD5 823ff723bde0deb5142a1753183467fd files/digest-phpwebsite-0.9.3_p4-r1 157 -MD5 6ddbbfb4f4e1e5c4d8bf717835d3c2d8 files/digest-phpwebsite-0.9.3_p4-r2 239 -MD5 37a63e58957baddea3334571305391bb files/postinstall-en.txt 434 MD5 835150acc17debf9125505dc224adc41 files/digest-phpwebsite-0.10.0-r3 305 -MD5 0f181e50286192df906dd979448e0fd5 files/phpwebsite-0.10.0-xml-rpc.diff 1188 MD5 2ca9ac185775bab6e8fbecf0584c5c67 files/digest-phpwebsite-0.10.1-r1 159 +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.1 (GNU/Linux) + +iD8DBQFCz8gFEZCkKN40op4RAl8FAJ0fLigh6+xHAan0eino1ZnUqL7l+ACgrndx +gg6RzuJ+DR9q/jo4iY67DNE= +=WNFf +-----END PGP SIGNATURE----- diff --git a/www-apps/phpwebsite/files/postinstall-en.txt b/www-apps/phpwebsite/files/postinstall-en.txt index b8130d7ea770..31702efbeaaf 100644 --- a/www-apps/phpwebsite/files/postinstall-en.txt +++ b/www-apps/phpwebsite/files/postinstall-en.txt @@ -1,5 +1,8 @@ phpWebSite is installed. +Installation Instructions +========================= + You will need to create a database for phpWebSite on your own before starting setup. @@ -15,3 +18,113 @@ Once you are done with installation you need to run: cd ${MY_INSTALLDIR}/setup ./secure_phpws.sh run apache users + +Upgrade Instructions +==================== + +Preparing to Upgrade +-------------------- + - Dump/backup your hub and branch databases. + - Backup your hub and branch directories/files. + - Create an index.php file that warns users of the upgrade. + +

Please be patient while we upgrade the site.

+We'll be back in a jiffy!"; +?> + + - Close and restart your browser. If you have a session live while updating + your site, it MIGHT interfere with the upgrade process. If you are using + Boost to upgrade, you can skip this step. + +If you are upgrading to 0.9.3 or greater, you should make the images/ +directory and subdirectories writable by the web server. + +Prepare your branches if you are running any off of your hub site. Depending +on the owner of these directories will affect the commands to run. The base +directory of each branch will need to be writable. + +If the owner is the webserver and you have root access: +chmod o+rwx branch1/ +chmod o+rwx branch2/ +etc... + +otherwise: +chmod 0777 branch1/ +chmod 0777 branch2/ +etc... + +The images and themes directories will also need to be writable for the +upgrade: + +chmod -R o+rwx branch1/{images,themes} +chmod -R o+rwx branch2/{images,themes} + +-or- + +chmod -R 0777 branch1/{images,themes} +chmod -R 0777 branch2/{images,themes} + +If the webserver is not given the proper permissions then the branch upgrade +will not be successfull. + + +Once you have you have finished these steps (and ONLY after) should you +continue. + +Running the Upgrade +-------------------------------------- +Now you can untar the new files into your installation. If you go to +your site's index.php file, you will see a few error messages. The +aforementioned index.php prevents most people from seeing these messages. +Point your browser to 'http://www.myWebSitesName.com/setup/' where +'www.myWebSitesName.com' is the address for your web site. + +The first thing the upgrader will do is upgrade your core modules. It +will also check to see if you are running any branch sites and automatically +upgrade them as well. + +You should receive a 'Core Updated!' message. Underneath these messages +will be a list of modules that appear to need upgrading as well. Click +the checkboxes of the modules you want updated (or click the 'Check All' button +to check all of them) and click the 'Update Modules' button. Your site and +all your branch sites should now be updated. + +If you made a warning index.php file, dump it and put the real file back. +You should now be able to use your site as normal. + +Should something go wrong +-------------------------------------- +If you go to your site and receive errors the FIRST thing you should try +is closing your browser, reopening it, and trying to use your site again. +Sometimes old sessions will conflict with the upgraded information. + +If you get an error message or your sites still don't function, restore your +backed up databases and files and try again. If it STILL doesn't work, contact +us via Sourceforge, we want to know what went wrong. + +Please include your OS, web server, PHP, and phpWebSite version information. +Also include any error messages that were displayed. The more data you supply +us, the better chance you will receive help. + +You may also try using the repair.php file. It contains answers to a few +commonly experienced problems. + +Returning to update.php +--------------------------------------- +Most of the time, Boost will handle your upgrade needs. However, should +an upgraded module cause problems before you can get to the Boost module, +you can always return to update.php to upgrade the offending module. + +Securing your Site +--------------------------------------- +Although setup.php, update.php, and repair.php require passwords to enter, +you may want to prevent malicious users (read: jerks) from even accessing +these files. One way would be to limit read access on that directory after +you are finished using it. Another measure would be to alter your +allow_setup.php file. Open this file in an editor and change the 'TRUE' +to 'FALSE' like so: + +$_SESSION['allow_setup'] = FALSE; + +Change this back to TRUE when you need to update again. -- cgit v1.2.3-65-gdbad