r/NextCloud

There are challenges around 32bit support, and while we added a warning to the setup checks in 2023 that 32bit support would be dropped, it's time to make a real decision. So, we are seeking input!

The short version

We still kind of support 32bit, but in practice it isn't working well. Meanwhile, maintaining it is blocking improvements to performance, security and scalability that our (overwhelmingly 64bit) users would benefit from. Unless some volunteers step up to maintain 32bit support and find workarounds for the issues below, we think we should phase it out, with the coming release the last one that maintains the current (limited) level of support.

32bit support is disappearing everywhere

• 32bit support breaks hard after 2038, and PHP itself will likely drop 32bit support well before that. A proposal to add PHP language features that would help 32bit was denied years ago, with maintainers citing that PHP itself would drop 32bit "soon anyway".
• many of the libraries we depend on are dropping or have dropped 32bit support already, leaving us unable to update for some, or keeping patches on top for others.
• Most of the Linux distributions no longer support it either, neither do many third party apps and nextcloud packages.
• 32bit affects Raspberry Pi 1 and 2. The popular NextcloudPi project supports Pi's only starting at the RaspberryPi 3B (which has 64 bit support).

We have recently invested quite some time and effort on fixing issues from our automated test coverage, work we will continue to put in to at least keep 32bit tests working.

We know that 32bit does still matter to some people: there are certainly still users running Nextcloud on Raspberry Pi 1/2, other dev boards, older NAS devices, and older routers. That's why we've kept it going this long, even though most contributors and customers have no need for it.

But we've had a warning about the state of 32bit support in the setup screen since 2023, and we think it's time to move on.

The cost of keeping it "supported"

Our current work to keep 32bit alive comes at a real cost.

• We're stuck on older versions of dependencies that still work on 32bit (e.g. maennchen/zipstream), and can't upgrade to versions with fixes.
• It blocks adoption of new tech we need, like snowflake IDs: PHP auto-converts big ints to floats on 32bit, losing precision; using them as strings instead just means PHP auto-converts them back to ints when used as array indices, breaking things either way.
• A number of performance optimizations can't be applied because they would break on 32bit.
• And of course, the time we spend fixing 32bit test issues can't be spend elsewhere.

Without intervention, this situation is getting worse as libraries are no longer maintained. This means more work spend on working around that instead of other bug fixes and improvements. Bringing 32bit support back up to a good level would already be a lot of work, and will become harder and harder.

What we're proposing

We're open to volunteers who want to keep 32bit alive: help find workarounds for the issues above, improve the current state of support, and help us figure out how to keep it working longer. But to be clear, this won't be easy.

If nobody steps up, we'll make the current reality official:

• Starting with release 35 (Nextcloud Hub 2026 Summer), we'll add a warning that 32bit is unsupported going forward. We'll still aim to make 2026 Summer work correctly on 32bit, as the last officially supported release.
• We will not immediately break 32bit support. To give a few months discuss and maybe change the plan, we will only really start merging library updates and apply improvements for performance starting near the end of the year.
• Note that the Nextcloud Hub 2026 Summer release will get security updates for one year, until about October 2027.

That gives people still on 32bit hardware a bit over a year to move to another platform. In the meantime, our 64bit users will finally benefit from scalability and performance improvements that 32bit support has been blocking.

Interested in helping maintain 32bit support? Let us know here and on github, we'd love to hear your thoughts.

I have finally got to a stable release of my Nextcloud(nxt) extension for N8N.

At first I was going to make a workflow to back up my workflows in Nextcloud by running a scheduled flow to push them. Instead, I decided to make a fully bidirectional mirror between Nextcloud and N8N so that the workflows feel truly native like just a file in your drive.

This let's you bind some tag in n8n to some folder in Nextcloud and then the JSON of the workflow is mirrored into Nextcloud. Now my backups are realtime and event driven. If I lose everything in n8n, I reinstall and reconnect to nxt, click a button, all my flows are loaded right back in.

My vision is to treat n8n workflows like any other file on a filesystem. So these files use `*.n8n` extension, proper mimetypes, fully managed DAV metadata, text editor, and an open in n8n option.

This is fully bidirectional. You can rename in nxt or n8n, either way is reflected. Change tags in both and both sides get the same tags. You can even make edits in JSON from the nxt editor or simply click to open the file in n8n itself to make edits.

There are so so many little details I covered in this. So here are links if you want to know more.

It is fully published on Nextcloud market: https://apps.nextcloud.com/apps/n8n_sync

Check out nitty gritty details in Github: https://github.com/kubed-io/nextcloud-n8n

Project was built following strict BDD Spec driven dev: https://github.com/kubed-io/nextcloud-n8n/tree/main/features

Then the whole damn story narrated by Claude: https://github.com/kubed-io/nextcloud-n8n/tree/main/saga

I've put months into this so that the end result is extra high quality. It's very well tested and smooth as butter. I released a new `v1` yesterday and am very excited to share with the world finally. Please do post some bug tickets if you come across any, I'm quite motivated to polish this until you can see your face in it.

Hope ya'll enjoy!

I love how much you can run through Nextcloud, but I always wished the whole thing felt like one proper native app instead of a mix of browser tabs, separate clients and different interfaces.

So I started building Nextcloud Native!

It is an independent open source client for desktop and Android. The idea is to connect your Nextcloud account once and get native interfaces for your files and installed apps. No WebViews and no shortcuts that just send you back to the browser.

It is still a new alpha, but there is already quite a lot to try. Files, Photos, Memories, Talk, Notes, Calendar, Contacts, Tasks, Mail, Music, Cookbook, Deck, Tables and more all have native interfaces at different levels of completeness.

On desktop, it is also more than a sync tray. There is a complete app with native workspaces, folder sync and operating system file integration. Windows gets Cloud Files placeholders in File Explorer, while Linux has folder sync and a virtual filesystem mount.

There is an Android app too, with native mobile layouts, system file access, offline files, folder sync, media backup and background transfers.

I only started the project recently, and I am still the only contributor. I am sharing it now because I would really like other Nextcloud users to try it, break it, suggest improvements and maybe help build it!

If you use Linux, Windows or Android and feel like testing an early build, I would love to hear what works and what does not. Contributions are also very welcome, whether you work with Kotlin, Compose, DAV, Nextcloud apps, design, accessibility, documentation or testing.

Website: https://nc-native.obiente.dev

GitHub: https://github.com/Obiente/nc-native

Testing releases: https://github.com/Obiente/nc-native/releases

Roadmap: https://nc-native.obiente.dev/roadmap/

What part of Nextcloud would you most like to have as a proper native experience?

EDIT:
Thank you all so much for your lovely support and kind words<3
And thank you for the 400 UPVOTES!! And the 120+ STARS?!!!

Edit: the good souls at the Nextcloud Community forum were able to solve this. Turns out that sudo clears the environment unless you use -E option. So after running the export command, you have to call occ with sudo -E -u www-data php occ

I'm currently implementing some server hardening steps and, following https://docs.nextcloud.com/server/latest/admin_manual/installation/harden_server.html#place-config-directory-outside-of-the-web-root, I've placed my config directory outside of the web root in /etc/nextcloud. Site is up and running, but what I haven't figured out yet is how to set the config dir in the shell environment. The documentation just gives this command:

export NEXTCLOUD_CONFIG_DIR=/etc/nextcloud

but doesn't specify where to run it. Can anybody help?

System config is:

• Nextcloud Hub 26 Spring (34.0.3)
• Linux 6.12.47+rpt-rpi-v8 aarch64
• PHP 8.3.17
• mysql 11.7.2

Many thanks!

Hi everyone,

I've been chipping away at this on and off for quite a while now, and I figured it was time to actually show it to someone instead of just pushing commits into the void.

FerrumPix is a desktop photo application for Linux, Windows and macOS: a library with a viewer, a fairly extensive editor with AI functions,Immich and Nextcloud Memories support.

Repo: https://github.com/Bitpainter75/FerrumPix

My motivation behind it:

Most tools in this space tend to specialize in one area. A library app is great at organizing photos but offers little in the way of editing. A RAW converter is great for tone and color work, but stays purely parametric and never touches the pixels themselves. A pixel editor can do almost anything to an individual image, but usually has no library. And Immich and Nextcloud Memories are great as server-side solutions, but ultimately remain browser-based, without an editor or local file management.

FerrumPix tries to bridge that gap: browse, rate, and tag your photos, then open one in an editor that supports both non-destructive adjustments and actual pixel editing. Your own Immich server sits in the same navigation tree as your local folders.The app is aimed more at hobby photographers than at professional workflows, and it really doesn't care whether you throw RAW files at it or JPGs from your phone.

It's built with Avalonia UI and .NET 10. The whole thing started as a personal project: an application that looks and works exactly the way I always wished one would. It's free and open source for anyone who can make use of it.

For transparency: yes, I use AI as part of my development workflow. That said, a project like this still involves a huge amount of hands-on work, architecture, debugging, and decision-making. I'm putting a lot of time into it, along with plenty of my own ideas and a lot of passion for the project.

Current status:

The current version is 0.9.27. The core areas are far enough along that I use the app daily myself; the focus now is on stabilization, UX and performance rather than new features.

I'd be glad to hear any feedback.

I'm always looking for an shopping list app, but every time i look i just find suggestions like "use nextcloud todos" or "use a simple list.txt". Somewhere someone suggested https://github.com/appMini/todoMini that looks a bit like it could be what i expect - add stuff, being able to sort stuff and bein able to easy remove or add stuff.

https://help.nextcloud.com/t/einkaufsliste-reiseliste-teilen-via-smartphone/144291/ suggests some of this. I found myself https://apps.nextcloud.com/apps/inventory this but it seems to technical? Dunno. But this all would be rather complicated when having to share this with others. For example on a holiday with friends, what to buy.

Today i found https://apps.nextcloud.com/apps/shopping_list - someone tried this yet? Seems like a dedicated app and also suprisingly polished (see website https://shoppinglist.otherworld.dev/ ) but the apk for 0.4.0 is missing for example. F-Droid still missing. But it seems to help with my problems.

Being able to share it, drag to reorder, works still offline and a dedicated app for others. "Download this, enter this and lets go" (at least i hope :D )

Anyone tried already?

Hi everyone 👋

I've been working on LX Family Planner — a self-hosted family organizer that bundles the stuff families actually need into one app, instead of spreading it across five. It runs on Docker / Unraid / Umbrel / Proxmox / plain Node.js, MIT-licensed.

What it does:

• 📅 Shared calendars with reminders
• ✅ Tasks & chores with approval workflow for kids
• 🛒 Shopping lists (incl. Bring! integration)
• 🍝 Meal planning & recipes
• 💬 Family chat with optional guest invites
• 📁 Family files / media
• 👶 Child profiles with playful missions & rewards
• 🐾 Pet profiles (care & health only)
• 🔔 Notifications via Gotify / ntfy
• 🌐 DE + EN interface, Android app available

Why self-hosted: All data stays on your own server. Adults get a calm planning workspace, parents keep control over approvals/integrations, and there's role-based access so kids see what they should see.

Integrations: Nextcloud, Home Assistant, Bring!, Gotify, ntfy

Links:

• 🔗 GitHub: https://github.com/laxxx-lab/lx-family-planner
• 🌐 Live demo: https://familie.laxxx-lab.de/
• 🐳 Docker: docker pull ghcr.io/laxxx-lab/lx-family-planner:latest
• 📦 Also in: Unraid Community Applications, Umbrel App Store
• 📱 Android APK in the README

Quick start (Docker):

yaml

services:
  lx-family-planner:
    image: ghcr.io/laxxx-lab/lx-family-planner:latest
    ports:
      - "3001:3001"
    environment:
      - APP_SECRET=<32+ random chars, keep stable across updates>
      - REGISTRATION_MODE=first-family
    volumes:
      - ./data:/app/data
      - ./backups:/app/backups
    restart: unless-stopped

I'd love feedback — especially from anyone running a family setup on a homeserver. What's missing for your use case?

Thanks for checking it out! 🙌