ownCloud OCIS
Installation - Summary
In the example below "owncloud" is the name of the subdomain that must already be registered in DNS.
Substitute your server's subdomain in DEFAULT_SUB_DOMAIN and email in the echo
commands below.
In the case where your server is intended to be your domain's root, provide an empty string instead.
Omit the OWNCLOUD_ADMIN_PASSWORD if you want to use the random password generated by ocis init. (Provide your own admin password, not the one in this example.)
After providing these defaults run the yum
commands as detailed below.
echo "pbase.foundation@gmail.com" > /root/DEFAULT_EMAIL_ADDRESS.txtecho "owncloud" > /root/DEFAULT_SUB_DOMAIN.txtecho "MYpwHERE" > /root/OWNCLOUD_ADMIN_PASSWORD.txtyum -y install https://pbase-foundation.com/pbase-repo.rpmyum -y install pbase-preconfig-owncloudyum -y install pbase-owncloud
Installation - Step by Step
Here is how to install an instance of the ownCloud OCIS file-sync and share platform.
It assumes your host is registered in DNS on a "owncloud" subdomain
like owncloud.myexample.com
and the installer will use Let's Encrypt to setup HTTPS.
Step 1: Provide your subdomain and admin email address by using the echo commands below
to create a text file under the /root directory for each value.
For example:
echo "owncloud" > /root/DEFAULT_SUB_DOMAIN.txt
echo "myaddress@myemailprovider.com" > /root/DEFAULT_EMAIL_ADDRESS.txt
Step 2: Install the pbase-repo package with the command:
yum -y install https://pbase-foundation.com/pbase-repo.rpm
... when it runs, its output will point out the file pbase_repo.json that now holds copies of the defaults.
Step 3: Install the ownCloud OCIS dependencies and pre-configuration package with the command:
yum -y install pbase-preconfig-owncloud
Step 4: Install the pbase-owncloud package with the command:
yum -y install pbase-owncloud
... it will take a few minutes for the installer to complete this step as it downloads and builds the dependencies used by ownCloud.
It will use Let's Encrypt to generate a certificate for HTTPS connections.
When the pbase-owncloud
package completes you should have a full working instance
of ownCloud OCIS ready to be administered at https://owncloud.myexample.com
depending on your domain name.
The admin user's password will be displayed in the log. Open the URL, login as admin and complete the first-time setup of your instance.
Extras
You should secure your server ports with pbase-firewall-enable
and lock down SSH access with the pbase-ssh-fail2ban
package.
If your server doesn't already have NTP/Chrony already running
you should sync your clocks with the pbase-timesync-enable
package.
yum -y install pbase-firewall-enableyum -y install pbase-ssh-fail2banyum -y install pbase-timesync-enable
Compatibility: EL8 only
Version 1.0 of the pbase-owncloud package works with Red Hat EL8/EL9, Fedora and Amazon Linux 2.
Configuration Options
The first step of the installer is the pbase-repo
package.
It creates the module-config.d directory to hold customizable configuration option files:
/usr/local/pbase-data/admin-only/module-config.d/
The pbase-repo creates this file: pbase_repo.json
it must be edited to set the defaultEmailAddress field with your email.
{"pbase_repo": {"defaultEmailAddress": "myaddress@myexample.com","defaultDesktopUsername": "","defaultSmtpPassword": "","defaultSubDomain": ""}}
The third step of the install is the preconfig-owncloud
package.
It places another default option file under
the /usr/local/pbase-data/admin-only/module-config.d/
directory.
This is the ownCloud configuration options file: pbase_owncloud.json
These defaults are appropriate for most use cases.
It assumes a subdomain of 'owncloud'.
If your subdomain is something else edit the urlSubDomain field to specify it.
{"pbase_owncloud" : {"autoOcisInit": true,"enableAutoRenew": true,"executeCertbotCmd": true,"downloadUrl": "https://download.owncloud.com/ocis/ocis/stable/2.0.0/ocis-2.0.0-linux-amd64","urlSubDomain": "owncloud","emailAddress": "yoursysadmin@yourrealmail.com","ocisUsername": "ocis","adminPassword": ""}}
Subdomain name
Your server's subdomain is defined in initial step of filling the /root/DEFAULT_SUB_DOMAIN.txt
file.
The value in this file is copied to the urlSubDomain
field in the JSON preconfig
pbase_owncloud.json
file created in step three of the install.
The steps shown above assumes the 'owncloud' subdomain is configured in DNS.
The other option is to have ownCloud for your root domain.
In this case, simply set the DEFAULT_SUB_DOMAIN file to an empty string with:
echo "" > /root/DEFAULT_SUB_DOMAIN.txt
... or omit it
which sets the preconfig files' urlSubDomain
fields to an empty string.
Source code of this RPM
This is the RPM .spec file containing the code that is executed by the pbase-owncloud installer. https://github.com/marklangbehn/pbase-rpm-installer/blob/master/applications/pbase-owncloud/rpmbuild/SPECS/pbase-owncloud.spec
More about ownCloud OCIS
Learn about the ownCloud OCIS at:
https://owncloud.dev/ocis/
"OCIS: ownCloud Infinite Scale, the modern file-sync and share platform..."