[Pkg-owncloud-commits] [owncloud-doc] 151/227: Break installation_source.rst into multiple pages per Web server configuration
David Prévot
taffit at moszumanska.debian.org
Sat Oct 11 17:20:44 UTC 2014
This is an automated email from the git hooks/post-receive script.
taffit pushed a commit to branch master
in repository owncloud-doc.
commit fffc0ff08382b5b3e9049b56e9968b2457d051f7
Author: Carla Schroder <carla at owncloud.com>
Date: Mon Sep 22 21:31:46 2014 -0700
Break installation_source.rst into multiple pages per Web server configuration
---
.../installation/configuration_hiawatha.rst | 12 +
.../installation/configuration_lighttpd.rst | 57 +++
admin_manual/installation/configuration_nginx.rst | 102 ++++
admin_manual/installation/configuration_yaws.rst | 30 ++
admin_manual/installation/index.rst | 4 +
admin_manual/installation/installation_source.rst | 523 +++++++--------------
6 files changed, 368 insertions(+), 360 deletions(-)
diff --git a/admin_manual/installation/configuration_hiawatha.rst b/admin_manual/installation/configuration_hiawatha.rst
new file mode 100644
index 0000000..c32cbfe
--- /dev/null
+++ b/admin_manual/installation/configuration_hiawatha.rst
@@ -0,0 +1,12 @@
+Hiawatha Configuration
+======================
+
+Add ``WebDAVapp = yes`` to the ownCloud virtual host. Users accessing
+WebDAV from MacOS will also need to add ``AllowDotFiles = yes``.
+
+Disable access to data folder::
+
+ UrlToolkit {
+ ToolkitID = denyData
+ Match ^/data DenyAccess
+ }
diff --git a/admin_manual/installation/configuration_lighttpd.rst b/admin_manual/installation/configuration_lighttpd.rst
new file mode 100644
index 0000000..ad6b901
--- /dev/null
+++ b/admin_manual/installation/configuration_lighttpd.rst
@@ -0,0 +1,57 @@
+Lighttpd Configuration
+======================
+
+This assumes that you are familiar with installing PHP applications on
+Lighttpd.
+
+It is important to note that the :file:`.htaccess` used by ownCloud to
+protect the :file:`data` folder is ignored by lighttpd, so you have to secure
+it by yourself, otherwise your :file:`owncloud.db` database and user data are
+publicly readable even if directory listing is off. You need to add these two
+snippets to your Lighttpd configuration file:
+
+Disable access to data folder::
+
+ $HTTP["url"] =~ "^/owncloud/data/" {
+ url.access-deny = ("")
+ }
+
+Disable directory listing::
+
+ $HTTP["url"] =~ "^/owncloud($|/)" {
+ dir-listing.activate = "disable"
+ }
+
+**Note for Lighttpd users on Debian stable (wheezy):**
+
+Recent versions of ownCloud make use of the **HTTP PATCH** feature, which was
+added to Lighttpd at version 1.4.32 while Debian stable only ships 1.4.31. The
+patch is simple, however, and easy to integrate if you're willing to build your
+own package.
+
+Download the patch from
+http://redmine.lighttpd.net/attachments/download/1370/patch.patch
+
+Make sure you have the build tools you need::
+
+ apt-get build-dep lighttpd
+ apt-get install quilt patch devscripts
+
+Patch the package source::
+
+ apt-get source lighttpd
+ cd lighttpd-1.4.31
+ export QUILT_PATCHES=debian/patches # This tells quilt to put the patch in
+ the right spot
+ quilt new http-patch.patch
+ quilt add src/connections.c src/keyvalue.c src/keyvalue.h # Make quilt
+ watch the files we'll be changing
+ patch -p1 -i /patch/to/downloaded/patch.patch
+ quilt refresh
+
+Increment the package version with ``dch -i``. This will open the changelog with
+a new entry. You can save as-is or add info to it. The important bit is that the
+version is bumped so apt will not try to "upgrade" back to Debian's version.
+
+Then build with ``debuild`` and install the .debs for any Lighttpd packages you
+already have installed.
\ No newline at end of file
diff --git a/admin_manual/installation/configuration_nginx.rst b/admin_manual/installation/configuration_nginx.rst
new file mode 100644
index 0000000..8155330
--- /dev/null
+++ b/admin_manual/installation/configuration_nginx.rst
@@ -0,0 +1,102 @@
+Nginx Configuration
+===================
+
+- You need to insert the following code into **your nginx config file.**
+- Adjust **server_name**, **root**, **ssl_certificate** and
+ **ssl_certificate_key** to suit your needs.
+- Make sure your SSL certificates are readable by the server (see `Nginx HTTP
+ SSL Module documentation <http://wiki.nginx.org/HttpSslModule>`_).
+
+.. code-block:: python
+
+ upstream php-handler {
+ server 127.0.0.1:9000;
+ #server unix:/var/run/php5-fpm.sock;
+ }
+
+ server {
+ listen 80;
+ server_name cloud.example.com;
+ # enforce https
+ return 301 https://$server_name$request_uri;
+ }
+
+ server {
+ listen 443 ssl;
+ server_name cloud.example.com;
+
+ ssl_certificate /etc/ssl/nginx/cloud.example.com.crt;
+ ssl_certificate_key /etc/ssl/nginx/cloud.example.com.key;
+
+ # Path to the root of your installation
+ root /var/www/;
+ # set max upload size
+ client_max_body_size 10G;
+ fastcgi_buffers 64 4K;
+
+ rewrite ^/caldav(.*)$ /remote.php/caldav$1 redirect;
+ rewrite ^/carddav(.*)$ /remote.php/carddav$1 redirect;
+ rewrite ^/webdav(.*)$ /remote.php/webdav$1 redirect;
+
+ index index.php;
+ error_page 403 /core/templates/403.php;
+ error_page 404 /core/templates/404.php;
+
+ location = /robots.txt {
+ allow all;
+ log_not_found off;
+ access_log off;
+ }
+
+ location ~ ^/(?:\.htaccess|data|config|db_structure\.xml|README) {
+ deny all;
+ }
+
+ location / {
+ # The following 2 rules are only needed with webfinger
+ rewrite ^/.well-known/host-meta
+/public.php?service=host-meta last;
+ rewrite ^/.well-known/host-meta.json
+/public.php?service=host-meta-json last;
+
+ rewrite ^/.well-known/carddav /remote.php/carddav/ redirect;
+ rewrite ^/.well-known/caldav /remote.php/caldav/ redirect;
+
+ rewrite ^(/core/doc/[^\/]+/)$ $1/index.html;
+
+ try_files $uri $uri/ index.php;
+ }
+
+ location ~ \.php(?:$|/) {
+ fastcgi_split_path_info ^(.+\.php)(/.+)$;
+ include fastcgi_params;
+ fastcgi_param SCRIPT_FILENAME
+$document_root$fastcgi_script_name;
+ fastcgi_param PATH_INFO $fastcgi_path_info;
+ fastcgi_param HTTPS on;
+ fastcgi_pass php-handler;
+ }
+
+ # Optional: set long EXPIRES header on static assets
+ location ~* \.(?:jpg|jpeg|gif|bmp|ico|png|css|js|swf)$ {
+ expires 30d;
+ # Optional: Don't log access to assets
+ access_log off;
+ }
+
+ }
+
+.. note:: You can use ownCloud over plain http, but we strongly encourage you to
+ use SSL/TLS to encrypt all of your server traffic, and to protect
+ user's logins and data in transit.
+
+- Remove the server block containing the redirect
+- Change **listen 443 ssl** to **listen 80;**
+- Remove **ssl_certificate** and **ssl_certificate_key**.
+- Remove **fastcgi_params HTTPS on;**
+
+.. note:: If you want to effectively increase maximum upload size you will also
+ have to modify your **php-fpm configuration** (**usually at
+ /etc/php5/fpm/php.ini**) and increase **upload_max_filesize** and
+ **post_max_size** values. You’ll need to restart php5-fpm and nginx
+ services in order these changes to be applied.
diff --git a/admin_manual/installation/configuration_yaws.rst b/admin_manual/installation/configuration_yaws.rst
new file mode 100644
index 0000000..298df40
--- /dev/null
+++ b/admin_manual/installation/configuration_yaws.rst
@@ -0,0 +1,30 @@
+Yaws Configuration
+==================
+
+This should be in your **yaws_server.conf**. In the configuration file, the
+**dir_listings = false** is important and also the redirect from **data/**
+to somewhere else, because files will be saved in this directory and it
+should not be accessible from the outside. A configuration file would look
+like this
+
+.. code-block:: xml
+
+ <server owncloud.myserver.com/>
+ port = 80
+ listen = 0.0.0.0
+ docroot = /var/www/owncloud/src
+ allowed_scripts = php
+ php_handler = <cgi, /usr/local/bin/php-cgi>
+ errormod_404 = yaws_404_to_index_php
+ access_log = false
+ dir_listings = false
+ <redirect>
+ /data == /
+ </redirect>
+ </server>
+
+The Apache :file:`.htaccess` that comes with ownCloud is configured to redirect
+requests to non-existent pages. To emulate that behaviour, you need a custom
+error handler for yaws. See this `github gist for further instructions
+<https://gist.github.com/2200407`_ on how to create and compile that error
+handler.
\ No newline at end of file
diff --git a/admin_manual/installation/index.rst b/admin_manual/installation/index.rst
index 11580fe..a7479a2 100644
--- a/admin_manual/installation/index.rst
+++ b/admin_manual/installation/index.rst
@@ -13,3 +13,7 @@ Installation
installation_source
installation_others
installation_wizard
+ configuration_nginx
+ configuration_lighttpd
+ configuration_yaws
+ configuration_hiawatha.rst
\ No newline at end of file
diff --git a/admin_manual/installation/installation_source.rst b/admin_manual/installation/installation_source.rst
index 19a7ca5..973f204 100644
--- a/admin_manual/installation/installation_source.rst
+++ b/admin_manual/installation/installation_source.rst
@@ -4,10 +4,8 @@ Manual Installation
If you do not want to use packages, here is how you setup ownCloud from
scratch using a classic :abbr:`LAMP (Linux, Apache, MySQL, PHP)` setup:
-This document provides a complete walk-through for installing ownCloud
-on Ubuntu 12.04 LTS Server with Apache and MySQL.
-It also provides guidelines for installing it on other distributions,
-web servers and database systems.
+This document provides a complete walk-through for installing ownCloud on Ubuntu
+14.04 LTS Server with Apache and MySQL.
Prerequisites
~~~~~~~~~~~~~
@@ -33,7 +31,7 @@ To run ownCloud, your web server must have the following installed:
Database connectors (pick at least one):
-* PHP module sqlite (>= 3, usually not recommendable for performance reasons)
+* PHP module sqlite (>= 3, usually not recommended for performance reasons)
* PHP module mysql
* PHP module pgsql (requires PostgreSQL >= 9.0)
@@ -43,7 +41,8 @@ Database connectors (pick at least one):
authentication, depends on this)
* PHP module fileinfo (highly recommended, enhances file analysis performance)
* PHP module bz2 (recommended, required for extraction of apps)
-* PHP module intl (increases language translation performance and fixes sorting of non-ASCII characters)
+* PHP module intl (increases language translation performance and fixes sorting
+ of non-ASCII characters)
* PHP module mcrypt (increases file encryption performance)
* PHP module openssl (required for accessing HTTPS resources)
@@ -73,13 +72,13 @@ For preview generation (*optional*):
**Remarks:**
-* Please check your distribution, operating system or hosting partner documentation
- on how to install/enable these modules.
+* Please check your distribution, operating system or hosting partner
+ documentation on how to install/enable these modules.
* Make sure your distribution's php version fulfils the version requirements
specified above. If it doesn't, there might be custom repositories you can
use. If you are e.g. running Ubuntu 10.04 LTS, you can update your PHP using
- a custom `PHP PPA`_: ::
+ a custom `PHP PPA <https://launchpad.net/~ondrej/+archive/php5>`_::
sudo add-apt-repository ppa:ondrej/php5
sudo apt-get update
@@ -89,126 +88,122 @@ For preview generation (*optional*):
mod_webdav) to access your ownCloud data via WebDAV. ownCloud has a built-in
WebDAV server of its own.
-Example installation on Ubuntu 12.04.4 LTS Server
+Example installation on Ubuntu 14.04 LTS Server
*************************************************
-On a machine running a pristine Ubuntu 12.04.4 LTS server, you would install the
+On a machine running a pristine Ubuntu 14.04 LTS server, you would install the
required and recommended modules for a typical ownCloud installation, using
Apache and MySQL by issuing the following commands in a terminal::
- sudo apt-get install apache2 mysql-server libapache2-mod-php5
- sudo apt-get install php5-gd php5-json php5-mysql php5-curl
- sudo apt-get install php5-intl php5-mcrypt php5-imagick
+ apt-get install apache2 mysql-server libapache2-mod-php5
+ apt-get install php5-gd php5-json php5-mysql php5-curl
+ apt-get install php5-intl php5-mcrypt php5-imagick
**Remarks:**
-* This installs the packages for the ownCloud core system. If you are planning on
- running additional apps, keep in mind that they might require additional packages.
- See the list above for details.
+* This installs the packages for the ownCloud core system. If you are planning
+ on running additional apps, keep in mind that they might require additional
+ packages. See the Prerequisites section (above) for details.
-* At the execution of each of the above commands you might be prompted whether you
- want to continue; press "Y" for Yes (that is if your system language is English.
- You might have to press a different key if you have a different system language).
+* At the execution of each of the above commands you might be prompted whether
+ you want to continue; press "Y" for Yes (that is if your system language is
+ English. You might have to press a different key if you have a different
+ system language).
-* At the installation of the MySQL server, you will be prompted for a root password.
- Be sure to remember the password you enter there for later use (you will need it
- during ownCloud database setup).
+* At the installation of the MySQL server, you will be prompted for a root
+ password. Be sure to remember the password you enter there for later use
+ as you will need it during ownCloud database setup.
-First, download the archive of the latest ownCloud version:
+Now download the archive of the latest ownCloud version:
-* Navigate to the `ownCloud Installation Page`_
-* Click "Tar or Zip file"
-* In the opening dialog, chose the "Linux" link.
-* This will start the download of a file named owncloud-x.y.z.tar.bz2 (where
+* Navigate to the `ownCloud Installation Page <http://owncloud.org/install>`_.
+* Click the **Archive file for server owners** button.
+* Click **Download Unix**.
+* This downloads a file named owncloud-x.y.z.tar.bz2 (where
x.y.z is the version number of the current latest version).
* Save this file on the machine you want to install ownCloud on.
-* If that's a different machine than the one you are currently working on, use
- e.g. FTP to transfer the downloaded archive file there.
-* Extract the archive contents. Open a terminal and run::
-
- cd path/to/downloaded/archive
- tar -xjf owncloud-x.y.z.tar.bz2
-
- where :code:`path/to/downloaded/archive` is to be replaced by the path where you
- put the downloaded archive, and x.y.z of course has to be replaced by the actual
- version number as in the file you have downloaded.
-
-* Copy the ownCloud files to their final destination in the document root of your
- web server (you can skip this step if you already downloaded and extracted the
- files there)::
-
- sudo cp -r owncloud /path/to/your/webservers/document-root
-
- where ``/path/to/your/webservers/document-root``, needs to be replaced by the
- actual path where the document root of your web server is configured to be.
-
- * If you don't know where your web server's document root is located, consult
- its documentation. For Apache on Ubuntu 12.04 LTS for example, this would
- usually be ``/var/www``. So the concrete command to run would be::
-
- sudo cp -r owncloud /var/www
-
- * The above assumes you want to install ownCloud into a subdirectory "owncloud"
- on your web server. For installing it anywhere else, you'll have to adapt the
- above command accordingly.
+* Verify the MD5 or SHA256 sum::
+
+ md5sum owncloud-x.y.z.tar.bz2
+ sha256sum owncloud-x.y.z.tar.bz2
+
+* You may also verify the PGP signature::
+
+ wget https://download.owncloud.org/community/owncloud-x.y.z.tar.bz2.asc
+ wget https://owncloud.org/owncloud.asc
+ gpg --import owncloud.asc
+ gpg owncloud-x.y.z.tar.bz2
+
+* Now you can extract the archive contents. Open a terminal, navigate to your
+ download directory, and run::
+
+ tar -xjf owncloud-x.y.z.tar.bz2
+
+* Copy the ownCloud files to their final destination in the document root of
+ your web server::
+
+ cp -r owncloud /path/to/webserver/document-root
+
+ where ``/path/to/webserver/document-root`` is replaced by the
+ document root of your Web server. Typically, on Ubuntu systems this
+ ``/var/www/owncloud``, so your copying command is::
+
+ cp -r owncloud /var/www/`
Set the Directory Permissions
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-The user running your web server must own at least the config/, data/ and apps/
-directories in your ownCloud installation folder so that you can configure ownCloud,
-create/modify and delete your data files through ownCloud and install apps through
-the web interface. If you are planning on also using the automatic updater app for
-updating, the whole ``owncloud`` folder must be owned by (or at least be writable to)
-the user running php on your system.
+Your HTTP user must own at least the ``config/``, ``data/``
+and ``apps/`` directories in your ownCloud directory so that you can
+configure ownCloud, create, modify and delete your data files, and install apps
+via the ownCloud Web interface. If you are planning to use the automatic
+updater app for updating ownCloud, the whole ``owncloud/`` directory must be
+writable by the HTTP user.
-.. note:: When using an NFS mount for the data directory, do not change ownership as above.
- The simple act of mounting the drive will set proper permissions for ownCloud to
- write to the directory. Changing ownership as above could result in some issues
- if the NFS mount is lost.
+You can find your HTTP user in your HTTP server configuration files. Or you can
+create a PHP page to find it for you. To do this, create a plain text file with
+a single line in it:
-* The generic command to run is::
+ ``<?php echo exec('whoami'); ?>``
+
+Name it ``whoami.php`` and place it in your ``/var/www/html`` directory, and
+then open it in a Web browser, for example ``http://servername/whoami.php``. You
+should see a single line in your browser page with the HTTP user name.
- sudo chown -R <php-user>:<php-user> /path/to/your/webservers/document-root/owncloud
+.. note:: When using an NFS mount for the data directory, do not change
+ ownership as above. The simple act of mounting the drive will set
+ proper permissions for ownCloud to write to the directory. Changing
+ ownership as above could result in some issues if the NFS mount is
+ lost.
- where ``<php-user>`` is to be replaced by the user running php scripts, and
- ``/path/to/your/webservers/document-root/owncloud`` by the folder where the
- extracted ownCloud files are located.
+* The generic command to change ownership of all files and subdirectories in a
+ directory is::
-* For Ubuntu 12.04 LTS server, where the ``owncloud`` folder was copied into the
- Apache document root at ``/var/www``, and the user running Apache and php
- scripts is called ``www-data``, this would mean you need to run::
+ chown -R <http-user>:<http-user> /path/to/owncloud/
- sudo chown -R www-data:www-data /var/www/owncloud
+* This example is for Ubuntu 14.04 LTS server::
+
+ chown -R www-data:www-data /var/www/owncloud
-* For Arch Linux should run (as root):
- ::
+* Arch Linux::
- chown -R http:http /path/to/your/owncloud
+ chown -R http:http /path/to/owncloud/
-* Fedora users should run (as root):
- ::
+* Fedora::
- chown -R apache:apache /path/to/your/owncloud
+ chown -R apache:apache /path/to/owncloud/
-* openSUSE users should run (as root):
- ::
+* openSUSE::
- chown -R wwwrun:www /path/to/your/owncloud
+ chown -R wwwrun:www /path/to/owncloud/
+Apache is the recommended Web server.
-Web Server Configuration
-~~~~~~~~~~~~~~~~~~~~~~~~
+Apache Web Server Configuration
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.. note:: You can use ownCloud over plain http, but we strongly encourage you to
- use SSL/TLS. If you don't use it, and you for example access your
- ownCloud over an unsecured WiFi, everyone in the same WiFi can grab
- your authentication data or the content of files synchronized while you
- are on the WiFi.
-
-Apache is the recommended web server.
-
-Apache Configuration
-********************
+ use SSL/TLS to encrypt all of your server traffic, and to protect
+ user's logins and data in transit.
Enabling SSL
............
@@ -217,18 +212,18 @@ An Apache installed under Ubuntu comes already set-up with a simple
self-signed certificate. All you have to do is to enable the ssl module and
the according site. Open a terminal and run::
- sudo a2enmod ssl
- sudo a2ensite default-ssl
- sudo service apache2 reload
+ a2enmod ssl
+ a2ensite default-ssl
+ service apache2 reload
-If you are using a different distribution, check their documentation on how to
+If you are using a different distribution, check your documentation on how to
enable SSL.
.. note:: Self-signed certificates have their drawbacks - especially when you
plan to make your ownCloud server publicly accessible. You might want
- to consider getting a certificate signed by an official signing
- authority. SSLShopper for example has an article on your
- `options for free SSL certificates`_.
+ to consider getting a certificate signed by commercial signing
+ authority. Check with your domain name registrar or hosting service,
+ if you're using one, for good deals on commercial certificates.
Configuring ownCloud
....................
@@ -238,22 +233,19 @@ you'll have to find out which Apache version you are using.
Usually you can do this by running one of the following commands::
- sudo apachectl -v
- apache2 -v
+ apachectl -v
+ apache2 -v
Example output::
- Server version: Apache/2.2.22 (Ubuntu)
- Server built: Jul 12 2013 13:37:10
-
-This indicates an Apache of the 2.2 version branch (as e.g. you will find on
-Ubuntu 12.04 LTS).
+ Server version: Apache/2.4.7 (Ubuntu)
+ Server built: Jul 22 2014 14:36:38
Example config for Apache 2.2:
.. code-block:: xml
- <Directory /path/to/your/owncloud/install>
+ <Directory /path/to/owncloud>
Options Indexes FollowSymLinks MultiViews
AllowOverride All
Order allow,deny
@@ -265,29 +257,23 @@ Example config for Apache 2.4:
.. code-block:: xml
- <Directory /path/to/your/owncloud/install>
+ <Directory /path/to/owncloud>
Options Indexes FollowSymLinks MultiViews
AllowOverride All
Require all granted
</Directory>
-* This config entry needs to go into the configuration file of the "site" you want
- to use.
+* This configuration entry needs to go into the configuration file of the
+ "site" you want to use.
* On a Ubuntu system, this typically is the "default-ssl" site (to be found in
- the :file:`/etc/apache2/sites-available/default-ssl`).
-* Edit the site file with your favorite editor (note that you'll need root
- permissions to modify that file). For Ubuntu 12.04 LTS, you could for example run
- the following command in a Terminal::
-
- sudo nano /etc/apache2/sites-available/default-ssl
-
+ the :file:`/etc/apache2/sites-available/default-ssl.conf`).
* Add the entry shown above immediately before the line containing::
</VirtualHost>
(this should be one of the last lines in the file).
-* A minimal site configuration file on Ubuntu 12.04 might look like this:
+* A minimal site configuration file on Ubuntu 14.04 might look like this:
.. code-block:: xml
@@ -325,282 +311,99 @@ Example config for Apache 2.4:
<Directory /var/www/owncloud>
Options Indexes FollowSymLinks MultiViews
AllowOverride All
- Order allow,deny
Allow from all
- # add any possibly required additional directives here
- # e.g. the Satisfy directive (see below for details):
- Satisfy Any
+ Require all granted
+ Dav Off
+ Satisfy Any
</Directory>
</VirtualHost>
</IfModule>
-* For ownCloud to work correctly, we need the module mod_rewrite. Enable it by running::
+* For ownCloud to work correctly, we need the module ``mod_rewrite``. Enable it
+ by running::
- sudo a2enmod rewrite
+ a2enmod rewrite
* In distributions that do not come with ``a2enmod``, the module needs to be
- enabled manually by editing the Apache config files, usually :file:`/etc/httpd/httpd.conf`.
- consult the Apache documentation or your distributions documentation.
+ enabled manually by editing the Apache config files, usually
+ :file:`/etc/httpd/httpd.conf`. Consult the Apache documentation or your Linux
+ distribution's documentation.
* In order for the maximum upload size to be configurable, the
:file:`.htaccess` in the ownCloud folder needs to be made writable by the
- server (this should already be done, see section `Set the Directory Permissions`_).
+ server (this should already be done, see section `Set the Directory
+ Permissions`_).
-* You should make sure that any built-in WebDAV module of your web server is disabled
- (at least for the ownCloud directory), as it will interfere with ownCloud's
- built-in WebDAV support.
+* You should make sure that any built-in WebDAV module of your web server is
+ disabled (at least for the ownCloud directory), as it will interfere with
+ ownCloud's built-in WebDAV support.
- If you need the WebDAV support in the rest of your configuration, you can turn it off
- specifically for the ownCloud entry by adding the following line in the
- configuration of your ownCloud. In above "<Directory ..." code, add the following line
- directly after the ``allow from all`` / ``Require all granted`` line): ::
+ If you need the WebDAV support in the rest of your configuration, you can turn
+ it off specifically for the ownCloud entry by adding the following line in
+ the ``<Directory`` section for your ownCloud server. Add the following line
+ directly after the ``allow from all`` / ``Require all granted`` line::
- Dav Off
+ Dav Off
-* Furthermore, you need to disable any server-configured authentication for ownCloud, as
- it's internally using Basic authentication for its \*DAV services.
- If you have turned on authentication on a parent folder (via e.g. an ``AuthType Basic``
- directive), you can turn off the authentication specifically for the ownCloud entry;
- to do so, in above "<Directory ..." code, add the following line directly after the
- ``allow from all`` / ``Require all granted`` line): ::
+* You must disable any server-configured authentication for ownCloud, as it
+ uses Basic authentication internally for DAV services. If you have turned on
+ authentication on a parent folder (via e.g. an ``AuthType Basic``
+ directive), you can turn off the authentication specifically for the ownCloud
+ entry. Following the above example configuration file, add the following line
+ directly after the ``allow from all`` / ``Require all granted`` line in the
+ ``<Directory`` section::
- Satisfy Any
+ Satisfy Any
-* When using ssl, take special note on the ServerName. You should specify one in the
- server configuration, as well as in the CommonName field of the certificate. If you want
- your ownCloud to be reachable via the internet, then set both these to the domain you
- want to reach your ownCloud under.
+* When using ssl, take special note on the ServerName. You should specify one in
+ the server configuration, as well as in the CommonName field of the
+ certificate. If you want your ownCloud to be reachable via the internet, then
+ set both of these to the domain you want to reach your ownCloud server.
-.. note:: By default, the certificates' CommonName will get set to the host name at the time
- when the ssl-cert package was installed.
+.. note:: By default, the certificates' CommonName will be set to the host name
+ at the time the ssl-cert package was installed.
* Finally, restart Apache.
- * For Ubuntu systems (or distributions using upstartd), run::
-
- sudo service apache2 restart
-
- * For systemd systems (Fedora, Arch Linux, OpenSUSE), run::
-
- systemctl restart httpd.service
-
-Nginx Configuration
-*******************
-
-- You need to insert the following code into **your nginx config file.**
-- Adjust **server_name**, **root**, **ssl_certificate** and **ssl_certificate_key** to suit your needs.
-- Make sure your SSL certificates are readable by the server (see `Nginx HTTP SSL Module documentation`_).
-
-.. code-block:: python
-
- upstream php-handler {
- server 127.0.0.1:9000;
- #server unix:/var/run/php5-fpm.sock;
- }
-
- server {
- listen 80;
- server_name cloud.example.com;
- return 301 https://$server_name$request_uri; # enforce https
- }
-
- server {
- listen 443 ssl;
- server_name cloud.example.com;
-
- ssl_certificate /etc/ssl/nginx/cloud.example.com.crt;
- ssl_certificate_key /etc/ssl/nginx/cloud.example.com.key;
-
- # Path to the root of your installation
- root /var/www/;
-
- client_max_body_size 10G; # set max upload size
- fastcgi_buffers 64 4K;
-
- rewrite ^/caldav(.*)$ /remote.php/caldav$1 redirect;
- rewrite ^/carddav(.*)$ /remote.php/carddav$1 redirect;
- rewrite ^/webdav(.*)$ /remote.php/webdav$1 redirect;
+ * On Ubuntu systems run::
+
+ service apache2 restart
- index index.php;
- error_page 403 /core/templates/403.php;
- error_page 404 /core/templates/404.php;
+ * On systemd systems (Fedora, Arch Linux, OpenSUSE), run::
- location = /robots.txt {
- allow all;
- log_not_found off;
- access_log off;
- }
+ systemctl restart httpd.service
+
- location ~ ^/(?:\.htaccess|data|config|db_structure\.xml|README) {
- deny all;
- }
-
- location / {
- # The following 2 rules are only needed with webfinger
- rewrite ^/.well-known/host-meta /public.php?service=host-meta last;
- rewrite ^/.well-known/host-meta.json /public.php?service=host-meta-json last;
-
- rewrite ^/.well-known/carddav /remote.php/carddav/ redirect;
- rewrite ^/.well-known/caldav /remote.php/caldav/ redirect;
-
- rewrite ^(/core/doc/[^\/]+/)$ $1/index.html;
-
- try_files $uri $uri/ index.php;
- }
-
- location ~ \.php(?:$|/) {
- fastcgi_split_path_info ^(.+\.php)(/.+)$;
- include fastcgi_params;
- fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
- fastcgi_param PATH_INFO $fastcgi_path_info;
- fastcgi_param HTTPS on;
- fastcgi_pass php-handler;
- }
+Install Wizard
+~~~~~~~~~~~~~~
- # Optional: set long EXPIRES header on static assets
- location ~* \.(?:jpg|jpeg|gif|bmp|ico|png|css|js|swf)$ {
- expires 30d;
- # Optional: Don't log access to assets
- access_log off;
- }
+Finish setting up your ownCloud server by following
+the :doc:`installation_wizard`.
- }
+Other Web Servers
+~~~~~~~~~~~~~~~~~
+
+Microsoft Internet Information Server (IIS)
+*******************************************
-.. note:: You can use ownCloud without SSL/TLS support, but we strongly encourage you not to do that:
+See :doc:`installation_windows` for further instructions.
-- Remove the server block containing the redirect
-- Change **listen 443 ssl** to **listen 80;**
-- Remove **ssl_certificate** and **ssl_certificate_key**.
-- Remove **fastcgi_params HTTPS on;**
+Nginx Configuration
+*******************
-.. note:: If you want to effectively increase maximum upload size you will also
- have to modify your **php-fpm configuration** (**usually at
- /etc/php5/fpm/php.ini**) and increase **upload_max_filesize** and
- **post_max_size** values. You’ll need to restart php5-fpm and nginx
- services in order these changes to be applied.
+See :doc:`configuration_nginx`
Lighttpd Configuration
**********************
-This assumes that you are familiar with installing PHP application on
-lighttpd.
-
-It is important to note that the :file:`.htaccess` used by ownCloud to
-protect the :file:`data` folder are ignored by lighttpd, so you have to secure
-it by yourself, otherwise your :file:`owncloud.db` database and user data are
-publicly readable even if directory listing is off. You need to add two
-snippets to your lighttpd configuration file:
-
-Disable access to data folder::
-
- $HTTP["url"] =~ "^/owncloud/data/" {
- url.access-deny = ("")
- }
-
-Disable directory listing::
-
- $HTTP["url"] =~ "^/owncloud($|/)" {
- dir-listing.activate = "disable"
- }
-
-**Note for Lighttpd users on Debian stable (wheezy):**
-
-Recent versions of ownCloud make use of the **HTTP PATCH** feature, which was added to Lighttpd at version 1.4.32 while Debian stable only ships 1.4.31. The patch is simple, however, and easy to integrate if you're willing to build your own package.
-
-Download the patch from http://redmine.lighttpd.net/attachments/download/1370/patch.patch
-
-Make sure you have the build tools you need::
-
- apt-get build-dep lighttpd
- apt-get install quilt patch devscripts
-
-Patch the package source::
-
- apt-get source lighttpd
- cd lighttpd-1.4.31
- export QUILT_PATCHES=debian/patches # This tells quilt to put the patch in the right spot
- quilt new http-patch.patch
- quilt add src/connections.c src/keyvalue.c src/keyvalue.h # Make quilt watch the files we'll be changing
- patch -p1 -i /patch/to/downloaded/patch.patch
- quilt refresh
-
-Increment the package version with ``dch -i``. This will open the changelog with a new entry. You can save as-is or add info to it. The important bit is that the version is bumped so apt will not try to "upgrade" back to Debian's version.
-
-Then build with ``debuild`` and install the .debs for any Lighttpd packages you already have installed.
+See :doc:`configuration_lighttpd`
Yaws Configuration
******************
-This should be in your **yaws_server.conf**. In the configuration file, the
-**dir_listings = false** is important and also the redirect from **/data**
-to somewhere else, because files will be saved in this directory and it
-should not be accessible from the outside. A configuration file would look
-like this
-
-.. code-block:: xml
-
- <server owncloud.myserver.com/>
- port = 80
- listen = 0.0.0.0
- docroot = /var/www/owncloud/src
- allowed_scripts = php
- php_handler = <cgi, /usr/local/bin/php-cgi>
- errormod_404 = yaws_404_to_index_php
- access_log = false
- dir_listings = false
- <redirect>
- /data == /
- </redirect>
- </server>
-
-The Apache :file:`.htaccess` that comes with ownCloud is configured to
-redirect requests to non-existent pages. To emulate that behaviour, you
-need a custom error handler for yaws. See this
-`github gist for further instructions`_ on how to create and compile that error
-handler.
+See :doc:`configuration_yaws`
Hiawatha Configuration
**********************
-Add ``WebDAVapp = yes`` to the ownCloud virtual host. Users accessing
-WebDAV from MacOS will also need to add ``AllowDotFiles = yes``.
-
-Disable access to data folder::
-
- UrlToolkit {
- ToolkitID = denyData
- Match ^/data DenyAccess
- }
-
-
-
-Microsoft Internet Information Server (IIS)
-*******************************************
-
-See :doc:`installation_windows` for further instructions.
-
-Install Wizard
-~~~~~~~~~~~~~~
-
-The last thing to do is to click through the installation wizard.
-
-Here are some guidelines for the values to enter there if following the
-Ubuntu-Apache-MySQL walk-through:
-
-* Make sure to click the "Advanced" Button to see the database settings
-
-* Choose MySQL as Database backend (you might not be presented with any other
- choice if you haven't installed any other database systems).
-* As Database host, enter ``localhost``.
-* As Database user enter ``root``.
-* As Database password, enter the password you entered during installation of the
- MySQL server package.
-* As Database name, enter an arbitrary name as you see fit
-
-Continue by following the :doc:`installation_wizard`.
-
-.. _PHP PPA: https://launchpad.net/~ondrej/+archive/php5
-.. _ownCloud Installation Page: http://owncloud.org/install
-.. _options for free SSL certificates: https://www.sslshopper.com/article-free-ssl-certificates-from-a-free-certificate-authority.html
-.. _github gist for further instructions: https://gist.github.com/2200407
-.. _Nginx HTTP SSL Module documentation: http://wiki.nginx.org/HttpSslModule
+See :doc:`configuration_hiawatha.rst`
\ No newline at end of file
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-owncloud/owncloud-doc.git
More information about the Pkg-owncloud-commits
mailing list