#First of all set up the [[LAMP]] stack as described in the corresponding Wiki article.

#First of all set up the [[LAMP]] stack as described in the corresponding Wiki article.

#Install the {{AUR|owncloud}} package as described in [[AUR#Installing_packages]].

#Install the {{AUR|owncloud}} package as described in [[AUR#Installing_packages]].

−

#Add the following lines into '''/etc/httpd/conf/httpd.conf''':

+

#Add the following lines into '''/etc/httpd/conf/httpd.conf''' (php5 should have been configured during the LAMP stack setup):

Include /etc/httpd/conf/extra/owncloud.conf

Include /etc/httpd/conf/extra/owncloud.conf

LoadModule php5_module modules/libphp5.so

LoadModule php5_module modules/libphp5.so

Line 24:

Line 24:

mysqli.so

mysqli.so

pdo_mysql.so

pdo_mysql.so

−

now restart the apache server with:

+

now [[Daemons#Restarting|restart]] httpd (Apache)

−

# rc.d restart httpd

and open [http://localhost http://localhost] in your browser. You should now be able to create a user account and follow the installation wizard.

and open [http://localhost http://localhost] in your browser. You should now be able to create a user account and follow the installation wizard.

Line 77:

Line 76:

* Add some [[LAMP#SSL|SSL encryption]] to your connection!

* Add some [[LAMP#SSL|SSL encryption]] to your connection!

+

+

== Nginx + uwsgi_php alternative ==

+

+

You can avoid the use of Apache, and run owncloud in it's own process by using the [https://aur.archlinux.org/packages.php?ID=63798 wsgi_php] application server. uWSGI itself has a wealth of features to limit the resource use, and to harden the security of the application, and by being a separate process it can run under its own user.

Depending on which database backend you are going to use uncomment either one of the following extensions in /etc/php/php.ini

sqlite.so
sqlite3.so
pdo_sqlite.so

OR

mysql.so
mysqli.so
pdo_mysql.so

now restart httpd (Apache)
and open http://localhost in your browser. You should now be able to create a user account and follow the installation wizard.

Custom configurations

Filesize Limitations

With the default configuration ownCloud only allows the upload of filesizes less than 2MB.
This can be changed by changing the following line in /etc/php/php.ini to your liking.

As of version 4.0 this is no longer necessary! The maximum upload size is now set via the ownCloud gui

upload_max_filesize = 2M

As of version 4.5, upload limits are set in /usr/share/webapps/owncloud/.htaccess. This won't work if PHP is set up to run as CGI, so you need to change the limits in /etc/php/php.ini. You also need to change open_basedir.

Running owncloud in a subdirectory

By including the default owncloud.conf in httpd.conf, owncloud will take control of port 80 and your localhost domain. If you would like to have owncloud run in a subdirectory, then skip the 'Include /etc/httpd/conf/extra/owncloud.conf' line altogether and just use a symbolic link like so:

ln -s /usr/share/webapps/owncloud/ /srv/http/

Filling ownCloud with data

Small Files

Always use WebDAV or the web interface to add new files to your ownCloud. Otherwise they will not show up correctly, as they do not get indexed right.

Nginx + uwsgi_php alternative

You can avoid the use of Apache, and run owncloud in it's own process by using the wsgi_php application server. uWSGI itself has a wealth of features to limit the resource use, and to harden the security of the application, and by being a separate process it can run under its own user.