I'd have some questions about #nextcloud. I'm running a nextcloud on my internal net (no direct internet access) and am wondering is it still the right solution to migrate onto a new hardware?
I'm asking, because I'm not feeling very comfortable with it, because I'm not really understanding it. I'm more a unix like person - keep it simple.
I'm using so far these nextcloud-like services:
- contacts and calendar integrated into linux and android clients
- lufi for filesharing
- occasionally file syncing, but I'm also using #syncthing (the nextcloud client on android sometimes does not work like I'd expect)
- am trying atm #memories which seems to have all features I'd like to have to migrate our families pictures from a synology nas
So for me it seems that it is #calendar, #contacts and maybe #memories.
If I'd break #nextcloud I'd break all of these applications. So I'm thinking if I could just use a bunch of applications like #lufi and #syncthing to migrate to instead of using the nextcloud framework.
I'd be happy about comments on this line of thought, motivations and arguments to keep using nextcloud and insight, practical experiences and reasons to migrate to other projects and drop nextcloud.
Should I
@me I'm still dippingy toes in using Nextcloud and for me part of the charm of is the multi user aspect. If I set stuff up for me it's relatively straight forward to also set it up for family members who are less tech savvy. An app like Syncthing is a technical marvel but also requires a nerdy brain to setup properly, both conceptually and practically.
So it (like often) very much depends on your requirements now and how they may evolve. Does that change anything for you?
@hermankopinga@mastodon.social Hey, thanks! Sounds like what I've been doing so far: doesn't feed a use case? Use something else.
But yes, being able to give out accounts sounds nice to me and I'm doing that already for other services for friends and family.
@me I've really loved the fixes for small stuff that makes managing a collection of smaller tools hard in the long run. (Backup emails, great docs, active community, good updates)
I recognize the downsides of a tightly connected large system. Still on the fence about it myself. Ironically partly because of how painful it is to get away from Google.
Still similarly held back like you: Committing to a more powerful server to use more of the features, feels very enterprise and not very unix-y.
@hermankopinga@mastodon.social
Committing to a more powerful server to use more of the features, feels very enterprise and not very unix-y.
Yes, that is a concern for me, too. I'm thinking into this direction:
- reachable is my yunohost (RockPro64 SBC) which runs nginx to connect to
- nextcloud-aio fpm on a system that can master memories and its features
- if there's more power I'd need I'd look into running containers spread over multiple small machines (I have a collection of SBCs)
@me You're a Unix guy. The way to look at #nextcloud is that it's a web app that uses php, a database and file storage.
#nextcloud does a decent job separating configuration and data. I loaded it "bare metal" on my existing system and it's been pretty good. There haven't been any hiccups I wasn't able to solve by reading the logs.
That said, occasionally #nextcloud apps stop being developed and get left behind. It's disappointing, but livable so far.
@jimbolaya@social.linux.pizza I already looked a bit into #NextcloudAIO - the new #docker based all-in-one solution to roll it out. Do you use that? What do you think about it?
@me Heh, I'm pretty old school and I'm hesitant to deploy something like #nextcloud as a container. Too many moving parts.
I've read good things about AIO, but I don't have experience with it.
I do have containers for other things like #matrix, and #jellyfin.
Well, I'll give it a try: https://forum.yunohost.org/t/nextcloud-aio-yunohost/36056.
#yunohost should provide the nginx (and let's encrypt certificate) and I'll look at nextcloud-aio (again) and see how I like it.
@jimbolaya@social.linux.pizza @hermankopinga@mastodon.social