ownCloud packaging notes ======================== Start ------ After installation you should be able to access the login/configuration page at the following URL: http://localhost/owncloud/ or http://localhost/ If not, make sure your webserver is running properly. Webserver --------- Currently ownCloud in Fedora supports httpd (Apache) and nginx. You must install at least one webserver subpackage (owncloud-). These packages include additional configuration files for the webservers. Remote access is disabled by default. To enable access from any host for Apache **AFTER** you complete the initial setup process, do this: ln -s /etc/httpd/conf.d/owncloud-access.conf.avail /etc/httpd/conf.d/z-owncloud-access.conf If you wish to adjust any of the settings it is recommended that you create a new configuration file that will override owncloud.conf, rather than editing it, so future changes to the packaged file will be respected on your server. If you do not do this, please be careful to check for changes in the packaged configuration file (especially on major ownCloud upgrades) and merge into your modified configuration as appropriate. Database -------- You can choose between three databases: MySQL, PostgreSQL and SQLite. For each of them there is an ownCloud subpackage (owncloud-). You are required to install at least one of them. The packages only ensure the necessary requirements to communicate with a database server of that type are installed, they do not require the database server package itself, as you may wish to use a remote database server. If you wish to use a local one, you must ensure it is installed and configured. For larger installs you should use MySQL or PostgreSQL. If you choose MySQL or PostgreSQL, keep in mind that you must create a database and user for ownCloud manually, before you can finish the setup process. The README.postgresql and README.mysql files provide more details and help with this. Configuration ------------- You can find the main configuration file at '/etc/owncloud/config.php'. Until you first access the server it will be just a small stub containing settings that differ in this package from the upstream defaults. After you first access ownCloud, the initial setup process will populate it with some more settings. Other settings that can be provided in this file are documented at: https://doc.owncloud.org/server/9.1/admin_manual/configuration_server/config_sample_php_parameters.html User Data --------- The default data directory is '/var/lib/owncloud/data'. Every file that is uploaded by your users to ownCloud gets saved into this folder. Consider doing a backup of this directory, together with the database and the main configuration. Note that if you change this location, you must set appropriate ownership and SELinux context attributes. Logging ------- As specified by the configuration file, ownCloud sends messages to the system logger, which means in a standard Fedora configuration it will log to the systemd journal: try "journalctl -b -t ownCloud". You can also change the loglevel or switch to the built-in log mechanism of ownCloud. App Store --------- If you install additional third party apps using the built-in app store, you can find them in the directory '/var/lib/owncloud/apps'. This functionality is enabled by default. If this is moved then it's important to configure httpd/nginx appropriately for the correct /owncloud/apps-appstore path to alias to the new location. The app store URL is coded into the core php and does not need to be listed in config.php If there are any empty proxy entries in config.php this will prevent connectivity to the store. If not using a proxy it is important to remove any proxy entries from config.php, not just be "" Selinux Booleans ---------------- If you want to use external files (eg remote smb/cifs server) the httpd_can_network_connect selinux boolean should be toggled on. If you want to use libreoffice document conversion then the httpd_execmem should be toggled on and the unoconv package should be installed. Memory caching -------------- For performance reasons a memory cache should be configured. In larger installs redis may be required but as a basic lightweight alternative edit config.php as per upstream documentation and install ACPu via: dnf install 'php-pecl(apcu)' For further information see http://owncloud.org/ and http://doc.owncloud.org/ Scheduling Background Jobs -------------------------- The default behaviour is to use the AJAX webcron, however this is fairly inefficient and does not scale very well. It's recommended to set the option "Cron" to use the system scheduler and to enable the included systemd timer. systemctl enable --now owncloud-cron.timer