HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
nextcloud
server
PHP2016–2025
nextcloud / server

server

☁️ Nextcloud server, a safe home for all your data

24Distinct people
24Mentions
1Explicit recommenders
37.5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

☁️ Nextcloud server, a safe home for all your data

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

> Written in old PHP and there is work underway to do a complete rewrite in Golang Wow [1], how cool would that be. I love that NextCloud exists and I plan to use it and call…

guerrilla used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 7:56:55 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year24 dated mentions

Observed mentions: 2016-06-02 16:17:37 UTC to 2025-05-07 15:28:46 UTC.

02462016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 7 mentions; 1 submissions, 6 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC202
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC101
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC716
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC404
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC202
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC404
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC202

What Hacker News says

4 sources
guerrilla·Aug 30, 2021Recommendation phrase
> Written in old PHP and there is work underway to do a complete rewrite in Golang Wow [1], how cool would that be. I love that NextCloud exists and I plan to use it and call me biased but god I hate to be running some PHP. I used to maintain a vulnerability database and I don't think I can ever trust a PHP project again at this point. Maybe things have changed but you'd find it very difficult to convince me. 1. https://github.com/nextcloud/server/issues/16726
In The open calendar, task and note space is a mess
Based on the github issue https://github.com/nextcloud/server/issues/21370 I don't see anything unusual for such a large project. They have thousands of issues open, merge dozens of PRs per day. I wouldn't expect one can fix a bug in a complex project in only a couple of hours. When I submitted PRs to large projects I needed hours just to get the test suite running, read the contributor guidelines, provide test cases, all for a couple of lines of changes.
In Ask HN: Open-source cloud storage written Ruby on Rails
I understand the -1, but you have to understand that to a user the choice is sometimes between: 1. Create crappy bug report and move on quickly to get things done or: 2. Do not create a bug report and move on immediately, to get things done I try to file whenever I can but when it's getting late and I want to go to bed I choose option 1 sometimes. Maybe I should choose option 2? For example, take the Nextcloud bug filing template on GitHub [0]. It's quite a long read but sure, worth the effort for free software I agree (Nextcloud is my favorite project, my life is in there, on my server)! However, I may not know exactly where these things are: ``` #### Web server error log <details> <summary>Web server error log</summary> ``` Insert your webserver log here ``` </details> #### Nextcloud log (data/n
Read the rest
extcloud.log) <details> <summary>Nextcloud log</summary> ``` Insert your Nextcloud log here ``` </details> #### Browser log <details> <summary>Browser log</summary> ``` Insert your browser log here, this could for example include: a) The javascript console log b) The network log c) ... ``` They also want config.php, contents of `sudo -u www-data php occ app:list`, ask you to do this: Login as admin user into your Nextcloud and access http://example.com/index.php/settings/integrity/failed Also all versions: ### Server configuration \*Operating system:\* \*Web server:\* \*Database:\* \*PHP version:\* \*Nextcloud version:\* (see Nextcloud admin page) \*Updated from an older Nextcloud/ownCloud or fresh install:\* Moreover, I'm quite afraid to put my domain names or even more sensitive info onto a public website if I just copy and paste. All I'm saying is that a big button that generates everything a dev needs with sensitive stuff redacted (which should be doable here and yes maybe I should make a PR for that) will make the experience a lot nicer for the reporter and the dev. As said, the Geyser MC project [1] can do exactly this and to me it is a game changer, the whole process was fast and pleasant and it was easy to test the automated builds they made in the branch based on my issue and report back in context on GitHub. Pasting the JSON their report feature generates into their Discord channel together with your question and their ability to just !docs/something point you to relevant docs with a small command feels like magic. I found the whole process inspirational. I love all FOSS devs. You are my heroes. [0]: https://github.com/nextcloud/server/issues/new?assignees=&la... [1] https://github.com/GeyserMC/Geyser
In Signal community: Reminder: Please be nice

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.