ownCloud is a software suite that provides a location-independent storage area for data (cloud storage).
AUR.AUR is available in the
- First of all set up the LAMP stack as described in the corresponding Wiki article.
- Install the AUR#Installing_packages. AUR package as described in
- 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 LoadModule php5_module modules/libphp5.so Include conf/extra/php5_module.conf
Uncomment extensions in /etc/php/php.ini
gd.so xmlrpc.so zip.so iconv.so
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
mysql.so mysqli.so pdo_mysql.so
now restart the apache server with:
# rc.d restart httpd
and open http://localhost in your browser. You should now be able to create a user account and follow the installation wizard.
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.
upload_max_filesize = 512M post_max_size = 512M memory_limit = 512M open_basedir = /srv/http/:/home/:/tmp/:/usr/share/pear/:/usr/share/webapps/
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
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.
Consider installing and enabling php-apc to speed up WebDAV.
When using SABnzbd, you might want to set
in your sabnzbd.ini file, because ownCloud will scan the files as soon as they get uploaded, preventing SABnzbd from removing UNPACKING prefixes etc.
WebDAV isn't suitable for big files, because it fills up all the RAM and CPU.
With the current version, it looks like, there is no good way of copying huge amounts of data to your ownCloud.
Here's a Workaround:
copy the files directly to your ownCloud and do a full re-scan of your database (you could use the Re-scan filesystem add-on for example).
But beware that this will not work as easily in the future, when end-to-end encryption gets added to ownCloud (this is a planned feature).
- When using a subdomain (like cloud.example.xxx), make sure it is covered by your certificate. Otherwise, connection via the owncloud client or webdav might fail.
- If you are planning on using OwnCloud's sync-clients, make sure to have NTP installed and running on your OwnCloud server, otherwise the sync-clients will fail.
- Add some SSL encryption to your connection!