Which project is actually bigger however is not clear.
Shows pretty clearly that ownCloud and Nextcloud dwarf the competition, and it also seems pretty clear that since its inception, interest in Nextcloud has been growing fast and today has actually more Google searches than ownCloud. To see what’s happening in this market, let’s take a brief look at this Google Trends graph of interest in the top four packages over the past 5 years: Google Trends In the open source private cloud space, there are several options, such as ownCloud, Nextcloud, Seafile, Syncthing and Pydio as well as smaller players such as SparkleShare. But this all increases the complexity and did not have time nor experience to set it up that way.Interested in finding the private cloud package that will work for you? It should also be possible to inject the SSL certificates using a mounted volume. Best would be to be able to replace the ownCloud container with one with a higher version. I’m aware that this way of using Docker containers isn’t suitable. Write down instructions for easy maintenance for updating OC and also updating the container’s Debian packages.
#Qnap owncloud update#
See if there’s a way to update the PHP on QNAP OS to explore the alternative without dockerįix container crashes with SIG_WINCH whenever we open the terminal in “Docker container station”, might need some package updates Or find a trustworthy database container that also runs on ARM Test ownCloud web updater in that OC containerĬheck if QNAP app store has a mariadb database to which the container could connect to Is the OC container volume part of QNAP RAID / backup ? Not too happy to manually configure all devices manually to Supports NAT loop or setup a local DNS server on the NAS. Missing NAT loop problem on router: either replace the router with one that
#Qnap owncloud how to#
How to do updates ? we cannot replace the OC container as we modified it. Then setup OC, edited config.php to add both the external domain and internal NAS domain in trusted_domains. On the Apache there => https worked from outside Installed certbot for Let’s encrypt for Debian 9 using a tutorial, it automatically setup SSL In Container station, used "Terminal " mode to connect to the OC container We added dummy user/password/host as these are not Out that Speedport router does not have NAT loopback so had to test from anotherĭomain name was already registered, the provider has an https “update URL” which we pasted into the Struggled a while because IP address was not accessible from inside. (fun fact that Speedport did not let us use fixed IPs for portįorwarding, had to select the target from a dropdown) Setup port forwarding on Speedport router from outside to QNAP: 80->8083,Ĥ43->8082. Set up port mapping with fixed port on docker host to OC container:Ĩ082->443, 8083->80 in the container station UI. Sqlite and no migration to MariaDB possible currently. We decided to go with SQlite for now but am worried about future deprecation of None of the official Mariadb or MySQL containers would run on ARM.
It turns out docker containers don’t all run on ARM. Decided against creating phpinfo.Ĭonsidering docker: we installed “QNAP container station”įound official ownCloud docker from ownCloud GmbH: owncloud/server => after installing, could not boot it: “exec user process caused ‘exec format error’”. Probably PHP only works with Apache2, no CLI. ( this post mentions libxml)ĭid not find PHP version as we could not find the “php” command. Later version but remembered seeing that QNAP has an old PHP version or other dependency issues.
#Qnap owncloud code#
Thought about updating the source code in /home/Q*/owncloud/owncloud to a
Installed ownCloud from the QNAP app store / package manager: it’s outdated ownCloud 8.0.3. Steps we went through Installing ownCloud The goal is to be able to maintain this ownCloud instance with minimal effort and minimal knowledge of command line. This is a report of an attempt to setup ownCloud 10.0.10 on a QNAP NAS.