Installing Owncloud On CentOS 7 Server
I transitioning an owncloud installation from a C6 server to a new C7 server and used yum install owncloud to install it on the C7 server. I expected /var/www/owncloud to be generated but alas not. Quick Googling just showed examples of installing from the latest owncloud repository but not using yum.
Have I missed something obvious when using yum to install?
7 thoughts on - Installing Owncloud On CentOS 7 Server
Am 19.06.20 um 01:08 schrieb H:
Hi,
the files are in a different directory. See the .conf files under
/etc/httpd/conf.d/owncloud*
First connection is allowed only from localhost.
After finishing the wizard you can enable access by typing ln -s
/etc/httpd/conf.d/owncloud-access.conf.avail
/etc/httpd/conf.d/z-owncloud-access.conf
You find that information in the file owncloud.conf under /etc/httpd/conf.d/
Cheers
Juergen
Am 19.06.2020 um 01:08 schrieb H:
rpm -qlv
shows you what you have installed into which locations on the system. Would have answered your question wihout googling from random resources.
Alexander
Thank you, it installed to /usr/share, not what I expected. I may go with nextcloud instead, though.
Btw, the link I am following on the net, https://computingforgeeks.com/install-nextcloud-on-CentOS-with-php-apache-mariadb/, for installing nextcloud is installing it to /var/www/html/nextcloud whereas some links I saw for owncloud installed it to /var/www/owncloud, ie one level higher. BTW, I have php 7.2 from SCL, not using Remi’s repo as used in the link.
Are there any (security) arguments for using one or the other location?
Am 19.06.2020 um 17:28 schrieb H:
What’s wrong with /usr/share/? It is a valid path and used by many web applications provided with or for EL systems.
Alexander
For external access? I have some other webapps installed in /var/www, ie at the same level as html, and then multiple websites under /var/www/html so I would like to stick with that tree.
Am 19.06.2020 um 20:08 schrieb H:
I don’t understand that question. Yes, for web service offerings under your domain to the public.
You can do what you want. But if you install through the package manager keep the packages healthy. There is no need to move the content around. You should be familier with “DocumentRoot” and “Alias” instructions for Apache. Nginx can serve from there as well.
SELinux should know too.
# semanage fcontext -l | grep /usr/share | grep httpd
Alexander