Difference between revisions of "Upgrading"

From Davical
Jump to navigationJump to search
m (Added database upgrade information)
Line 1: Line 1:
 
{{Languages|Upgrading}}
 
{{Languages|Upgrading}}
 
== Normal Upgrading Procedure ==
 
== Normal Upgrading Procedure ==
 +
 
Check the [[Release Notes]] for upgrading from one version to another.
 
Check the [[Release Notes]] for upgrading from one version to another.
 +
 +
The general procedure for installing a new release of DAViCal is basically a matter of overwriting the existing PHP files under <code>/etc/davical/</code> with their recent version.
 +
 +
When upgrading DAViCal versions it will normally also be necessary to upgrade [[AWL]] versions at the same time.
  
 
In most cases you will need to apply an update to the database using [[update-davical-database]], but in some cases even this will not be required and you should be safely able to just install the new version.
 
In most cases you will need to apply an update to the database using [[update-davical-database]], but in some cases even this will not be required and you should be safely able to just install the new version.
  
From version 0.9.8 an error message will be displayed if your database version is out of date.
+
There is a special command to do this:
 +
 
 +
dba/[[update-davical-database]]
  
When upgrading DAViCal versions it will normally also be necessary to upgrade [[AWL]] versions at the same time.
+
This will:
 +
* Apply any outstanding database schema patches
 +
* Install any new locale data
 +
* Update the permissions for the application dbuser
 +
* Update the database function and view definitions
  
It might be necessary to recreate the accounts clientside after an upgrade of the server [http://sourceforge.net/mailarchive/message.php?msg_id=28368290].
+
From version 0.9.8 an error message will be displayed if your database version is out of date.
  
<hr>
+
Although it can be avoided most of the time, for exceptionally extensive or fundamental upgrades it might be necessary to recreate the accounts clientside after an upgrade of the server [http://sourceforge.net/mailarchive/message.php?msg_id=28368290]. Refer to the Release Notes for Details.
  
 
==== RSCDS => DAViCal Upgrades ====
 
==== RSCDS => DAViCal Upgrades ====

Revision as of 13:40, 7 July 2014

Help
Available languages

Normal Upgrading Procedure

Check the Release Notes for upgrading from one version to another.

The general procedure for installing a new release of DAViCal is basically a matter of overwriting the existing PHP files under /etc/davical/ with their recent version.

When upgrading DAViCal versions it will normally also be necessary to upgrade AWL versions at the same time.

In most cases you will need to apply an update to the database using update-davical-database, but in some cases even this will not be required and you should be safely able to just install the new version.

There is a special command to do this:

dba/update-davical-database

This will:

  • Apply any outstanding database schema patches
  • Install any new locale data
  • Update the permissions for the application dbuser
  • Update the database function and view definitions

From version 0.9.8 an error message will be displayed if your database version is out of date.

Although it can be avoided most of the time, for exceptionally extensive or fundamental upgrades it might be necessary to recreate the accounts clientside after an upgrade of the server [1]. Refer to the Release Notes for Details.

RSCDS => DAViCal Upgrades

Once upon a time the DAViCal CalDAV Server was called 'RSCDS' (the Really Simple CalDAV Store), but it was renamed at around version 0.9.2.

If you are upgrading from a really old version like that then there are some changes in the new version in some internal naming and file locations:

  • Configuration is now in /etc/davical/
  • DocumentRoot is now in /usr/share/davical/htdocs/

Things you might want to change, but which can be left as they were:

  • The database is now named 'davical' by default
  • The web application access the database as the 'davical_app'
  • The database should generally be access as the 'davical_dba' user for DBA activities