diff --git a/docs/website/index.php b/docs/website/index.php index 84e56100..6122a2dc 100644 --- a/docs/website/index.php +++ b/docs/website/index.php @@ -3,8 +3,9 @@ include("inc/page-header.php"); ?>
DAViCal is a server for calendar sharing. It is an implementation of the CalDAV protocol which is designed -for storing calendaring resources (in iCalendar format) on a remote shared server.
+DAViCal is a server for calendar sharing. It is an implementation +of the CalDAV protocol which is designed for storing calendaring +resources (in iCalendar format) on a remote shared server.
An increasing number of calendar clients support the maintenance of shared remote calendars through CalDAV, including Mozilla Calendar (Sunbird/Lightning), Evolution, Mulberry, Chandler, and various other closed-source products @@ -30,9 +31,9 @@ and writing the same calendar entries over time, and scheduling of meetings with versions of Linux, FreeBSD, Mac OSX and even Microsoft Windows. We definitely do not recommend using Windows for this unless you are completely hobbled by silly internal IT policies and have to do so.
-You can download DAViCal from http://debian.mcmillan.net.nz/
-Start looking on the DAViCal Installation Page for more places to download, and +
Start by looking on the DAViCal + Installation Page for instructions on places to download, and detailed instructions as to what to do when you have it.
There is a lot of information on the wiki about DAViCal configuration settings but in most cases the configuration will need very few of these settings.
diff --git a/docs/website/installation.php b/docs/website/installation.php index 353d672e..6c199551 100644 --- a/docs/website/installation.php +++ b/docs/website/installation.php @@ -5,73 +5,41 @@Ideally you will be running a recent Debian (or Ubuntu) release and will -be able to add:
--deb http://debian.mcmillan.net.nz/debian lenny awm --
to your /etc/apt/sources.list. Once you have done that you
-can use apt-get or synaptic or some other equivalent package
-manager to fetch and install DAViCal and all the dependencies.
This repository is signed by Andrew McMillan's public key, which you can install so that -you don't get asked for confirmation all the time:
- --sudo apt-key advanced --keyserver pgp.net.nz --recv-keys F6E0FA5CF0307507BB23A512EAFCFEBF8FEB8EBF -- -
Skip to the "Database Setup" part if you have done that already.
- +Recent Debian (and Ubuntu) releases have DAViCal 1.1.1 and AWL 0.53 + (a library referenced by DAViCal) available in their repositories, + and you can use apt-get or similar tools to download and install + DAViCal. Once you have done that, you should be able to proceed to + the Database Setup section, below.
Please write something up about your experiences in the Wiki, adding distribution specific -notes to pages somewhere under here: - http://wiki.davical.org/w/Installation_Stuff
+The DAViCal wiki contains + information on installation on other versions of Linux. Please feel + free to contribute your experiences, using the mailing list if you + don't have a wiki account.
-We have created RPM packages of DAViCal and libawl-php from the .deb packages -using "alien". These are reported to work fine, so use them and then proceed to the -Pre-requisites section below. If you would like to work with us to create native -RPM packages please get in touch!
+In many cases, you will need to download the latest versions of
+the DAViCal and awl packages from
+the repository on
+GitLab. More details on this are on
+the Downloading
+ page on the wiki.
On SuSE Linux you may need to look in /var/lib/pgsql/data/ for the pg_hba.conf file.
- -Davical and the awl library ebuilds are available on the sunrise overlay. -You'll have to add this overlay to your system:
--emerge layman -layman -f -a sunrise -echo "source /usr/portage/local/layman/make.conf" >> /etc/make.conf -- -
From there, you can keep the overlay in sync with the command:
-layman -s sunrise- -
Davical can now be installed with a normal:
-emerge davical- -
You will need to download the latest versions of the DAViCal and awl packages
-from the sourceforge download page for DAViCal.
You will need to untar these. Preferably you will untar them from within the "/usr/share" directory and everything
-will be in it's expected location (well, except the docs, but it will at least be tidy and everything will be in one place).
We would like to hear from non-Debian users regarding things which might have been missed, or things you have -learned about the system, so please write about your installation experiences on the Wiki, or post a message -in the Sourceforge forums.
+We would like to hear from non-Debian users regarding things which +might have been missed, or things you have learned about the system, +so please write about your installation experiences on the Wiki, or +post a message on the mailing list.
We would really like to hear from you. As far as we can see there is no reason why this -can't all work on FreeBSD, Microsoft Windows, VMS, Mac OS or whatever else, as long as the -pre-requisites are able to be installed.
-For Unix and unix-like operating systems the "Other Linux Users" instructions are likely -to be reasonably close to what you need. For other systems everything will need some -adjustment, and in particular some of the path name and shell expectations coded into -the database creation scripts are likely to need love.
+We would really like to hear from you. As far as we can see there +is no reason why this can't all work on FreeBSD, Microsoft Windows, +VMS, Mac OS or whatever else, as long as the pre-requisites are able +to be installed.
+ +For Unix and unix-like operating systems the "Other Linux Users" +instructions are likely to be reasonably close to what you need. For +other systems everything will need some adjustment, and in particular +some of the path name and shell expectations coded into the database +creation scripts are likely to need love.
We're available to answer questions, anyway :-)
Since the CalDAV store takes over a significant amount of path -hierarchy, it can be easier in it's own virtual +hierarchy, it can be easier in its own virtual host. If you want it to operate within the web root of some other application there are instructions on the Wiki about doing this, as well as other fancy tricks such as configuring URL rewriting in