diff --git a/docs/website/installation.php b/docs/website/installation.php index 070af270..045e5881 100644 --- a/docs/website/installation.php +++ b/docs/website/installation.php @@ -83,8 +83,8 @@ a number of years.
The following other software is also needed:
On your database server you will need to create a user called -'davical_app' which should not be able to create databases or users, -and which will be granted minimum privileges for the application.
--createuser --no-createdb --no-createrole davical_app -- -
You may need to become the 'postgres' user to do this, in which case -you will need to be the postgres user to create the database as well. -For example:
--su postgres -c createuser --no-createdb --no-createrole davical_app --
To create the database itself, run the script:
@@ -130,8 +114,7 @@ of itself and it expects them to be located in /usr/share/awl/dba which might be a reasonable place, but it might not be where you have put them. -Similarly to creating the user, this script also expects to be -running as a user who has rights to create a new database, so you +
This script expects to be running as a user who has rights to create a new database, so you may need to do this as the "postgres" user, for example:
su postgres -c /usr/share/davical/dba/create-database.sh @@ -154,8 +137,8 @@ local davical davical_app trustThis means that anyone on the local computer (including the web application) will have rights to connect to the DAViCal -database as the 'davical_app' user. It will not allow remote access, -or access as any user other than 'davical_app'.
+database as the 'davical_app' or 'davical_dba' user. It will not allow remote access, +or access as any user other than 'davical_app' or 'davical_dba'.If you want to connect to the database over TCP/IP rather than unix sockets, the line in the pg_hba.conf file should look something @@ -181,7 +164,7 @@ into effect.
Relative to an existing DocumentRoot
You can create a symlink from an existing web root directory to the -/usr/share/rscds/htdocs directory, such as:
+/usr/share/davical/htdocs directory, such as:cd /my/apache/docroot @@ -220,7 +203,6 @@ single virtual host. php_value include_path /usr/share/awl/inc php_value magic_quotes_gpc 0 php_value register_globals 0 - php_value open_basedir 1 php_value error_reporting "E_ALL & ~E_NOTICE" php_value default_charset "utf-8" </VirtualHost> @@ -307,8 +289,9 @@ psql davical -c 'select username, password from usr;' won't be readable in this way - only the initial configuration leaves passwords readable like this for security reasons. -If all is working then you should be ready to configure a client -to use this, and the docs for that are elsewhere.
+Check the '/setup.php' page in your installation and if everything +is working then you should be ready to configure a client +to use your new DAViCal installation, and the docs for that are elsewhere.
If you had to do something else that is not covered here, or if you have any other notes you want to add to help others through the installation process, please write something up @@ -320,10 +303,15 @@ about your experiences in the Wiki, including distribution specific notes, to pa
Whenever you upgrade the DAViCal application to a new version you will need to run dba/update-davical-database which will apply any pending database patches, as well as -enabling any new translations.
+enabling new translations, loading database views and functions, and setting application +permissions to database tables. -In due course the running of this script will be able to be handled by -the packaging system, but that change will not happen until early 2007.
+When the database is created all the tables are owned by a 'davical_dba' user which +you will also want to add access for in your pg_hba.conf, although in that case you +may want to set the user to have a password, since it has full control over the DAViCal +database structure and content.
+ +See http://wiki.davical.org/w/Update-davical-database for more information.