Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Nextcloud Hub 26 Spring: Built together, designed for the future

nextcloud.com

Post reply on HN
Print view View original

61–70 of 103 posts

Re: Nextcloud Hub 26 Spring: Built together, designed for the future

#61

Post by bisby »

blendergeek wrote: post #11

Nextcloud has the most confusing versioning of any software I have ever used. Nextcloud Hub 26 is Nextcloud 34 and follows Nextcloud Hub 9 which is Nextcloud 33. And I could be off on those exact numbers.

When numbers are confusing, it's usually just a recalibration.

Hub 9 aligns with cloud 33. But they are switching Hub to a dated numbering scheme because it's intended to be timestamped. It's not "Hub 26" its "Hub 26 Spring" -- it's not a version number, it's a time.

The underlying Nextcloud keeps an incremental semver release version so it can be based on features rather than timeline. Because the Nextcloud version and Hub version aren't tied to each other.

This would be like saying that iPhones have a confusing naming scheme because iPhone 17 uses iOS 27 and has 2 different numbers. If next year's iPhone was called "iPhone 2027" and used "iOS 29", we'd still understand that.

Re: Nextcloud Hub 26 Spring: Built together, designed for the future

#62

Post by snailmailman »

lgcmo wrote: post #50
drnick1 wrote: post #18

Nextcloud is great, I self-host an instance at home. I mostly use the calendar, address book, and file sharing with links a la Google Drive. It's probably heavier and slower than it should be for what it does, but it works. Just like Home Assistant, it is a "must have" tool for self-hosters.

What's your experience like? Lot's of people say that's a mess to maintain and too broken to actively use. I often doubt if that's due to actual problems, or mix with that and bad decisions on the setup. Is dockering, keeping the data handling itself outside of it and a few other easy (or not so much) precautions enough to have a somewhat smoother sailing? Also, how much time do you need to keep things from failing a…

They have an “all in one” container that supposedly works out of the box.

I didn’t want to give it access to the docker socket, with the ability to spawn its own containers. So instead I just use the nextcloud container directly. (With several other containers, like DB, reverse proxy, collabora, etc) It’s a mess to configure, hence their recommendation to use their “all in one” setup. All sorts of weird defaults with documentation that says “this is the default but you should absolutely change it to do X instead so that it performs better”. Things like setting up a service to generate thumbnails, setting up redis, etc.

Once configured though, it mostly just works. You can’t let it auto update between major versions, but you probably should be doing that anyway. There are usually breaking changes and you have to manually run a command or two between major updates. That doesn’t happen too frequently though.

I can’t speak to the quality of the all-in-one setup. It’s likely easier than what I did - but also what’s the point of putting it in docker and also giving it control of docker? Seems to defeat the point of containerization.

Re: Nextcloud Hub 26 Spring: Built together, designed for the future

#63

Post by margalabargala »

theK wrote: post #60
0fflineuser wrote: post #56

Earlier quoted context omitted.

Host it in your home an use a vpn to connect to your home network when you are outside, that way it isn't exposed to the internet but you can still access it.

Yup, that's the way it has to be. And thanks to the autocomplete on steroids we call Ai nowadays it actually has become way easyier to do such a thing.

Kinda like how once chemistry gets complicated enough we call it biology, LLMs have become complicated/versatile enough that it's no longer useful to call them autocomplete.

Re: Nextcloud Hub 26 Spring: Built together, designed for the future

#64

Post by zerkten »

NaiveBayesian wrote: post #49

I love nextcloud and have been using it for years. However recently I've considered taking my instance offline or at least behind a VPN because even if only 10% is true of what AI folks are claiming about LLMs finding exploits left and right, it seems super risky to be hosting your private data on nextcloud. How do you folks deal with these massively increased threats to self-hosted open source apps?

Putting everything behind a VPN seems like the solution selfhosters have landed on. That way you have some control over how quickly you have to respond.

Re: Nextcloud Hub 26 Spring: Built together, designed for the future

#65

Post by 3lpsy »

NaiveBayesian wrote: post #49

I love nextcloud and have been using it for years. However recently I've considered taking my instance offline or at least behind a VPN because even if only 10% is true of what AI folks are claiming about LLMs finding exploits left and right, it seems super risky to be hosting your private data on nextcloud. How do you folks deal with these massively increased threats to self-hosted open source apps?

I host my entire homelab in my home and use tailscale to access it. You just connect your nextcloud instance to tailscale. Then you connect each client to tailscale. Works on iOS and android (and of course any desktop). When you're on you're home network (LAN), tailscale _should_ use the LAN IP for routing. And then when away, you'll route over derp servers usually.

You could also use tailscale for auth, but i like to enforce separate authentication so that you have to be authenticated to the tailnet and have to go through the normal authentication to app.

Re: Nextcloud Hub 26 Spring: Built together, designed for the future

#66

Post by cahaya »

NaiveBayesian wrote: post #49

I love nextcloud and have been using it for years. However recently I've considered taking my instance offline or at least behind a VPN because even if only 10% is true of what AI folks are claiming about LLMs finding exploits left and right, it seems super risky to be hosting your private data on nextcloud. How do you folks deal with these massively increased threats to self-hosted open source apps?

Same. Solving it by moving complex and sensitive data to an offline desktop app https://document.bot that support offline (self hosted) AI models (and optionally EU/ US AI providers). However, it doesn't integrate yet with shared (org) drives.

Re: Nextcloud Hub 26 Spring: Built together, designed for the future

#67

Post by bityard »

3lpsy wrote: post #65
NaiveBayesian wrote: post #49

I love nextcloud and have been using it for years. However recently I've considered taking my instance offline or at least behind a VPN because even if only 10% is true of what AI folks are claiming about LLMs finding exploits left and right, it seems super risky to be hosting your private data on nextcloud. How do you folks deal with these massively increased threats to self-hosted open source apps?

I host my entire homelab in my home and use tailscale to access it. You just connect your nextcloud instance to tailscale. Then you connect each client to tailscale. Works on iOS and android (and of course any desktop). When you're on you're home network (LAN), tailscale _should_ use the LAN IP for routing. And then when away, you'll route over derp servers usually. You could also use tailscale for auth, but i like t…

That works okay if you are the only user.

I use quite a few Nextcloud features where access via tailscale is either inconvenient or impossible. My whole family uses the calendar on their phones and other devices, which means they would have to either learn about VPNs, or I would be the one managing all their devices for them. (Neither are likely to happen.)

I also often share individual files or folders with external contacts as a more private alternative to dropbox or google drive.

Re: Nextcloud Hub 26 Spring: Built together, designed for the future

#69

Post by bityard »

vitally3643 wrote: post #44
imalerba wrote: post #36

I left nextcloud because how slow it felt even on my beefy server. I switched to opencloud.eu, it might have less features but it's just what I needed

Seriously. I ran it on a server with two Xeon CPUs and 128GB of RAM. The web interface took minutes to do anything. Browsing a large photo library was just completely unworkable (and that was before they ripped out all the sorting and filtering features from the photo library). My instance killed itself somehow, likely a failed auto update. I was, of course, using the default docker setup with the watchtower instance…

I'm not sure how you are holding it, but I ran Nextcloud on a VPS with under 1GB RAM for many years, now it's on a 12GB RAM cloud instance and is only using a few GB of RAM last time I checked.

Re: Nextcloud Hub 26 Spring: Built together, designed for the future

#70

Post by bityard »

fundatus wrote: post #16

I love Nextcloud but I feel like they should really completely redo their UI. It just doesn't look like something from this decade.

Wha-huh?

This is the decade where every company bought into flat design, monochrome, chonky whitespace, extremely radiused corners everywhere. Pulling up my instance, Nextcloud apes that to a tee. You'd be hard-pressed to find any "modern" UI trend that they haven't shoe-horned into their design somehow.

The _did_ completely redo their UI a few years back, and for the worse in my opinion. The Calendar in particular is far less usable and (and much more buggy) than it was around the time it was forked from OwnCloud.

Post reply on HN