SF.net SVN: postfixadmin:[937] trunk

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Revision: 937
          http://postfixadmin.svn.sourceforge.net/postfixadmin/?rev=937&view=rev
Author:   christian_boltz
Date:     2011-01-06 20:01:21 +0000 (Thu, 06 Jan 2011)

Log Message:
-----------
various documentation updates:

INSTALL.TXT:
- added a note to read the official PostfixAdmin documentation first,
  and that "external" HOWTOs on the web are often outdated or incomplete.
  That might sound selfish, but would already have saved several users
  some time.
- updated some links
- added link to the wiki
- added hint about config.local.php
- added note about write access for templates_c directory for www-data

UPGRADE.txt
- added note about setup.php?debug=1
- added note about postfix config update (alias domains)
- added note about templates_c permissions

Modified Paths:
--------------
    trunk/DOCUMENTS/UPGRADE.txt
    trunk/INSTALL.TXT

Modified: trunk/DOCUMENTS/UPGRADE.txt
===================================================================

--- trunk/DOCUMENTS/UPGRADE.txt	2011-01-05 20:57:53 UTC (rev 936)
+++ trunk/DOCUMENTS/UPGRADE.txt	2011-01-06 20:01:21 UTC (rev 937)
@@ -57,7 +57,14 @@
 
 (the last command assumes your Apache is running with group "www")
 
+Since version 2.4 we use smarty templates. That means the templates_c directory
+needs to be writeable for your webserver.
 
+  $ chown -R www-data templates_c/
+
+(if your Apache runs as user "www-data")
+
+
 4. Configure
 ------------
 Check the config.inc.php file. There you can specify settings that are
@@ -66,8 +73,8 @@
 Comparing config.inc.php with your previous using "diff" might save you some
 time.
 
-You can use a config.local.php file to contain your local settings - these will override any 
-defined in config.inc.php
+You can use a config.local.php file to contain your local settings. These will override any 
+defined in config.inc.php - and save some time when upgrading to a new version of PostfixAdmin ;-)
 
 5. Run setup.php
 ----------------------------------------
@@ -75,6 +82,7 @@
 Access setup.php through a web browser.
 
 It will attempt to upgrade your database, and also allow you to create a superadmin user.
+(In case the database upgrade fails, you can run setup.php?debug=1 to see the last executed query.)
 
 From version 2.3, you need to specify a setup_password in config.inc.php - 
 setup.php should guide you through this process. If you do not have a setup_password, type one
@@ -89,8 +97,14 @@
 Note that admin/ has been merged into the main directory. Login with the
 superadmin account to setup domains and domain admins.
 
+5. Upgrade your postfix config
+------------------------------
 
+Since version 2.3, PostfixAdmin supports alias domains ($CONF['alias_domain']).
+If you want to use them, you have to add some queries to your postfix config -
+see POSTFIX_CONF for details.
 
+
 6. Done
 -------
 This is all that is needed. Fire up your browser and go to the site that you

Modified: trunk/INSTALL.TXT
===================================================================
--- trunk/INSTALL.TXT	2011-01-05 20:57:53 UTC (rev 936)
+++ trunk/INSTALL.TXT	2011-01-06 20:01:21 UTC (rev 937)
@@ -15,15 +15,23 @@
 
 READ THIS FIRST!
 ----------------
-When this is an upgrade from Postfix Admin 1.5.4 please read DOCUMENTS/UPGRADE.TXT!!
+When this is an upgrade from a previous version of Postfix Admin, please read 
+DOCUMENTS/UPGRADE.TXT also!
 
 If you need to setup Postfix to be able to handle Virtual Domains and Virtual
-Users check out :
+Users check out:
 
-  - http://high5.net/howto/ 
+  - the PostfixAdmin documentation in the DOCUMENTS/ directory
+  - our wiki at http://sourceforge.net/apps/mediawiki/postfixadmin/
+
+There are also lots of HOWTOs around the web. Be warned that many of them 
+(even those listed below) may be outdated or incomplete. 
+Please stick to the PostfixAdmin documentation, and use those HOWTOs only if
+you need some additional information that is missing in the PostfixAdmin 
+DOCUMENTS/ folder.
   - http://codepoets.co.uk/postfixadmin-postgresql-courier-squirrelmail-debian-etch-howto-tutorial (Debian+Courier+PostgreSQL+Postfix+Postfixadmin)
   - http://bliki.rimuhosting.com/space/knowledgebase/linux/mail/postfixadmin+on+debian+sarge (Postfix+MySQL+Postfixadmin+Dovecot)
-  - http://gentoo-wiki.com/HOWTO_Setup_a_Virtual_Postfix/Courier_Mail_System_with_PostfixAdmin (Postfix+MySQL+Postfixadmin+Courier)
+  - http://en.gentoo-wiki.com/wiki/Virtual_mail_server_using_Postfix,_Courier_and_PostfixAdmin (Postfix+MySQL+Postfixadmin+Courier)
 
 
 1. Unarchive new Postfix Admin
@@ -61,7 +69,7 @@
 3. Configure PostfixAdmin so it can find the database
 -----------------------------------------------------
 
-Edit the config.inc.php file.
+Edit the config.inc.php file - or - create config.local.php and add your settings there.
 
 The most important settings are those for your database server.
 
@@ -74,9 +82,12 @@
 $CONF['configured'] = true;
 
 
-PostfixAdmin does not require write access to any files. You can therefore 
-leave the files owned as root (or a.n.other user); as long as the web server 
-user (e.g. www-data) can read them, it will be fine.
+PostfixAdmin does not require write access to any files except the tempates_c 
+directory (smarty cache). You can therefore leave the files owned as root (or
+another user); as long as the web server user (e.g. www-data) can read them, it
+will be fine.
+For templates_c/, allow write access (only) for the web server user (e. g. www-data).
+The easiest way to do this is   chown -R www-data templates_c
 
 The next 'step', is optional. Only do it, if other non-trusted users have access 
 to your user:


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.


