How To Install ownCloud 7 on CentOS 6.5

Want to support HowtoForge? Become a subscriber!
 
Submitted by howtoforge (Contact Author) (Forums) on Tue, 2014-08-05 10:07. :: CentOS | Linux | Web Server | Apache | Storage

How To Install ownCloud 7 on CentOS 6.5

Version 1.0
Author: Srijan Kishore
Last edited 29/July/2014

This document describes how to install and configure ownCloud 7 on CentOS 6.5. I will also connect to the ownCloud Server's data with Ubuntu 14.04 desktop and windows 7 machine. ownCloud provides access to your data through a web interface or WebDAV while providing a platform to easily view, sync and share across devices—all under your control. ownCloud’s open architecture is extensible via a simple but powerful API for applications and plugins and works with any storage.


1 Preliminary Note

This tutorial is based on CentOS 6.5 server, so you should set up a basic CentOS 6.5 server installation before you continue with this tutorial. The system should have a static IP address. I use 192.168.0.100 as my IP address in this tutorial and server1.example.com as the hostname. Again I have  192.168.0.101 as IP address of Ubuntu 14.04 Desktop and server2.example.com as the hostname. I will be using the user=srijan for the installation and configuration. I will also show the ownCloud sharing options with windows machine, so I have working Windows 7 machine too.

 

2 Installation of ownCloud 7

ownCloud is a web application that can store and serve content from a centralized location, much like Dropbox. The difference is that ownCloud 7 allows you to host the serving software on your own machines, taking the trust issues out of putting your personal data someone else's server.

We will first download the release key associated with the ownCloud software:

cd /etc/yum.repos.d/
wget http://download.opensuse.org/repositories/isv:ownCloud:community/CentOS_CentOS-6/isv:ownCloud:community.repo

Then we need to add epel repository too:

rpm -ivh http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm

Finally, update the package database and install ownCloud:

yum install owncloud

ownCloud will install Apache with its dependency, if it doesn't get installed automatically manually install httpd:

yum install httpd

Apache must restart at every boot so we will add it to chkconfig as:

chkconfig --levels 235 httpd on
/etc/init.d/httpd start

Further we need to allow SELINUX with apache at http and https as follows:

setup

Click to enlarge


Select Firewall configuration:

Click to enlarge

Select Cutomize:

Click to enlarge


Allow for Secure WWW (HTTPS) and WWW (HTTP) further save and exit:

Click to enlarge


3 ownCloud 7 configuration on CentOS 6.5

Further we need to install Mysql to get the configurations as follows:

yum install mysql-server

chkconfig --levels 235 mysqld on
/etc/init.d/mysqld start

We will be configuring our ownCloud server to take advantage of the more robust MySQL database instead of the SQLite default implementation. To do so, we must configure MySQL first as:

mysql_secure_installation

[root@server1 ~]# mysql_secure_installation

NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MySQL
SERVERS IN PRODUCTION USE! PLEASE READ EACH STEP CAREFULLY!

In order to log into MySQL to secure it, we'll need the current
password for the root user. If you've just installed MySQL, and
you haven't set the root password yet, the password will be blank,
so you should just press enter here.

Enter current password for root (enter for none):
OK, successfully used password, moving on...

Setting the root password ensures that nobody can log into the MySQL
root user without the proper authorisation.

Set root password? [Y/n] <-- ENTER
New password: <-- yourrootsqlpassword
Re-enter new password: <-- yourrootsqlpassword
Password updated successfully!
Reloading privilege tables..
... Success!

By default, a MySQL installation has an anonymous user, allowing anyone
to log into MySQL without having to have a user account created for
them. This is intended only for testing, and to make the installation
go a bit smoother. You should remove them before moving into a
production environment.

Remove anonymous users? [Y/n] <-- ENTER
... Success!

Normally, root should only be allowed to connect from 'localhost'. This
ensures that someone cannot guess at the root password from the network.

Disallow root login remotely? [Y/n] <-- ENTER
... Success!

By default, MySQL comes with a database named 'test' that anyone can
access. This is also intended only for testing, and should be removed
before moving into a production environment.

Remove test database and access to it? [Y/n] <-- ENTER
- Dropping test database...
... Success!
- Removing privileges on test database...
... Success!

Reloading the privilege tables will ensure that all changes made so far
will take effect immediately.

Reload privilege tables now? [Y/n] <-- ENTER
... Success!

Cleaning up...

 

All done! If you've completed all of the above steps, your MySQL
installation should now be secure.

Thanks for using MySQL!

Now moving towards the Mysql prompt:

mysql -u root -p

Put the Mysql password which you selected before, & create a database for ownCloud in Mysql prompt:

CREATE DATABASE owncloud;

Assign privileges to a new MySQL user to handle database operations for ownCloud:

GRANT ALL ON owncloud.* to 'owncloud'@'localhost' IDENTIFIED BY 'database_password';

exit

Now, if you go to your IP address or domain name followed by "/owncloud" in your browser, you will see a page that looks like this:

Click to enlarge


Click on Storage & database:

Click to enlarge



Now select MySQL/MariaDB and create an admin account as in my case I have choosen owncloud as my admin account and a desired password for that user:

Click to enlarge


In the lower tab below the MySQL/MariaDB give the entry of the username=owncloud password=database_password databasename=owncloud.

Then press Finish setup.

Click to enlarge


Click to enlarge



Please do not use the comment function to ask for help! If you need help, please use our forum.
Comments will be published after administrator approval.