From ArchWiki
(Redirected from Talk:Owncloud)
Jump to navigation Jump to search

Possible merge with owncloud

[[Moved from Talk:Nextcloud -- Rdeckard (talk) 13:41, 7 January 2017 (UTC)

I'm thinking many of the installation and configuration steps are identical between Nextcloud and Owncloud. We could possibly merge these two articles. There is some good info here that may be missing at Owncloud. I think unless there are drastic differences they should be combined. We could note any differences in the main article. -- Rdeckard (talk) 01:52, 5 January 2017 (UTC)

Good idea. Are you offering to take point? Graysky (talk) 01:58, 7 January 2017 (UTC)
Sure. It actually looks like many of the sections are identical (were copied). I'll work on it. -- Rdeckard (talk) 13:00, 7 January 2017 (UTC)
Wait, shouldn't we create a new page merging the content, then setup redirects from 'owncloud' and 'nextcloud' to that new page? To me, the unified page would would allow for either package to be installed from one read without having all the clicking between pages like I see you have started to do. Graysky (talk) 13:22, 7 January 2017 (UTC)
Right. That was temporary until I got everything merged piece-by-piece. It all now goes to ownCloud where both programs are treated. -- Rdeckard (talk) 13:36, 7 January 2017 (UTC)
OK, if you're finished, I might take a look at further refining the unified page, but I don't want to deal with potential content collisions if we are both editing simultaneously :) Graysky (talk) 13:42, 7 January 2017 (UTC)
Go for it! I'm done with it for the morning. Thanks! -- Rdeckard (talk) 13:44, 7 January 2017 (UTC)
I Realize I am a bit late on this, but the fact that Nextcloud forked from ownCloud, wouldn't it have been advantageous to keep them separate as we don't know how long the install processes will remain the same / similiar? --TheFlyingFool (talk) 13:57, 25 January 2017 (UTC)
We may have to revisit this again. But for now the setup and configuration are nearly the same. Personally I think the owncloud/nextcloud manuals do a great job with the details, so we should refer to them more often. If and when the installation process here diverges, we'll consider splitting again. -- Rdeckard (talk) 13:50, 31 January 2017 (UTC)

Switch to cron from AJAX

The ownCloud 9.1 Server Administration Manual on "Defining Background Jobs" states cron as the preferred method for executing regular tasks. It also states that AJAX is "...the default option. Unfortunately, however, it is also the least reliable." The downside being AJAX requires regular visits to the page to trigger the background job. --Koopa (talk) 21:37, 7 February 2017 (UTC)

Versions of nextcloud from 12 and up suggests that both cron and systemd can be used, and I see no point in even mentioning cron, since it's a whole software piece that's missing from arch by default, and adding it to this article contributes nothing. Systemd should be used by default with Arch to integrate well with other parts of the OS, and not to confuse users with multiple scheduling tools. NeoTheFox (talk) 10:53, 28 August 2017 (UTC)

Uploaded file size limitation

The article is missing raising file size limitation. Current max file size with the provided configs seems to be 512MB - 2GB depending on what you use to upload.

This seems to be set in /usr/share/webapps/nextcloud/.user.ini for the web side, /tmp needs to be as big as all concurrent file uploads, and possibly more.

Documentation is here:

Am planning to figure this out and add it to the article sometimes in the future, but if someone does it before me I won't be mad.

C0rn3j (talk) 10:51, 2 October 2017 (UTC)

Cron, file scan and preview timers

I have changed the AUR repository from `nextcloud-systemd-cron` to `nextcloud-systemd-timers`. I did this change, because I have also included timers for periodic file scans and preview generation. If there is interest, I can add some lines about these timers to the Nextcloud Wiki article.

—This unsigned comment is by Dschrempf (talk) 09:34, 28 November 2018‎. Please sign your posts with ~~~~!

I have changed [1]. It sure is helpful, if you add a little about what is included. --Indigo (talk) 18:40, 28 November 2018 (UTC)


I believe the INI file [2] included on this page has issues (at least it did for me). Those issues are resolved with a one-line addition to the bottom:

env = front_controller_active=true

The issue being that the Nginx configuration provided throughout this page includes the following block:

location = / {
    rewrite ^ /index.php;

But this causes conflicts with the PHP-side's own URL rewriting. Adding the front_controller_active environment variable clears this up.

Djmoch (talk) 03:56, 31 December 2018 (UTC)

nginx section: dead link

the nginx section has a tip section for a config template to work with Lets encrypt. that link is broken. the github repo seems restructured/deleted..

—This unsigned comment is by MrWhite (talk) 22:53, 7 December 2019‎. Please sign your posts with ~~~~!

Please use Template:Dead link to mark broken links. -- Lahwaacz (talk) 08:04, 8 December 2019 (UTC)
Removed in Special:PermanentLink/614531 Tlvince (talk) 12:00, 20 May 2020 (UTC)

Add disclaimer for possible disadvantages of setting up nextcloud on a rolling-release OS

Dear administrators,

I would like to propose adding a disclaimer to the wiki about the possible disadvantages of setting up nextcloud on a rolling-release OS like Arch linux. I have a nextcloud server that became dysfunctional after a recent update from php 7.3 to 7.4, since nextcloud doesn't upgrade as fast as a rolling release OS does. Trying to downgrade to php 7.3 was not possible either, due to several dependencies failing to allow that. Please don't get me wrong, I do believe that Arch linux's rolling-release feature is one of its strengths but when it is not matched with the same agility in the development of other software packages, it may become a problem, like in the case described above.

Thank you for your consideration.

Hakova Hakova (talk) 17:16, 21 December 2019 (UTC)

Update Collabora section to include HTTPS for Docker container

It appears the Docker image for the Collabora section uses in the nginx and Apache examples, but the default Docker image now ships listening with HTTPS, eg. or you get Bad Gateway errors from php-fpm.

—This unsigned comment is by Chetwisniewski (talk) 22:04, 29 March 2020‎. Please sign your posts with ~~~~!

Recent Pacman hook removal

The most recent edit removed Pacman hook section because it's been already in the package. But the hook installation line is commented out in PKGBUILD, so it's not installed by default. Is it reasonable to remove the hook section in spite of not installing the hook file itself? And why is the hook installation line in PKGBUILD commented out in the first place?

Ynakao (talk) 11:11, 13 June 2020 (UTC)

Reverted. -- Lahwaacz (talk) 11:19, 13 June 2020 (UTC)

AndyRTR (talk) 14:27, 13 June 2020 (UTC) Sorry for the removal. I had the hook also probably manually installed long ago and missed that's not actually in the pkg. Opened

the "Make sure that session.save_path is configured." bit could use explanation

I actually still do not know how to configure this.

—This unsigned comment is by Zuntik (talk) 16:01, 21 September 2020 (UTC). Please sign your posts with ~~~~!