The really hilarious thing to me is that the NextPush app (unified push provider that can be run on your nextcloud server) is unsupported by nextcloud talk. But it is supported by a bunch of other competing applications.

Nextcloud AIO is not the only way to run Nextcloud in docker. For example you can use the Nextcloud docker repository and docker-compose for which there are many examples. I’ve been running Nextcloud this way for many years now without any un-recoverable issues, and no issues at all that weren’t caused by me. Upgrading is also very easy since you simply increment the version in docker-compose.yml and restart the service.

That said the NixOS suggestion from @StrawberryPigtails@lemmy.sdf.org looks really neat and I may try that out soon my self since I’ve never played with NixOS before and it seems like a good excuse to do so.

But can it sneekily destroy the cables under my desk? And does it sometimes just stop and look at you to think “I could destroy you… if only I was a little bit bigger”.

I think this one https://github.com/nextcloud/desktop/issues/5369 is probably the more relevant, and also open, issue. However even in that issue people claim you can choose not to. The argument is only that it suggests restarting explorer and also rebooting and that this is annoying. So you never get a prompt, it just dies?

I agree though that the amount of time where it was force rebooting is pretty bad, and it looks like the rollout of the patch was mishandled. I also should probably admit that I’ve never touched the windows client, my environment is entirely Linux and Android. The Linux client even with file manager integration doesn’t require restarts of anything.

I mentioned the client in there (4th paragraph), but mine was more of a general rant on the overall low effort that seems to have been put in to figuring out what the actual problem was. And that it is relatively common among people in the self hosting community to assume that Nextcloud is a lot simpler than it is. It’s a huge cloud suite consisting of many applications, clients, plugins, proxies, caching, database, etc. You need to have a pretty good understanding of how it all works, and how to investigate a problem, and ideally you should be testing before upgrades. Large organizations often even test endpoint applications like the desktop client and push out only tested versions to users via policy or some kind of endpoint management.

I can’t really draw many conclusions from the very little information provided in this post, but I suspect OPs windows machine is not in an entirely stable state, which is what is causing some of these update issues.

And, I put some of the blame for Nextcloud under-representing it’s complexity on Nextcloud’s marketing and AIO. You absolutely can install it without understanding anything, and that’s a little dangerous in my opinion because it is actually quite complex and you will probably end up breaking it at some point and need to dig in to fix it.

Ok, I’m prepared to be downvoted today so here goes.

Nextcloud is an enterprise cloud suite. The one you run in docker on your rpi (or whatever) is the same one that is run at a company, albeit with more high availability and redundancy, but the same application, proxies, caching, db, etc. Nothing is stopping you from running the stable channel and testing your upgrades, or even rolling out specific stable client versions to your devices.

Said companies often have teams (more than one person) to run it, stage upgrades, automated testing, automated backups, monitoring, etc. They go to work and do just that, maybe not every day but at least a couple times a week their focus is Nextcloud and only Nextcloud.

What many people in the self hosting community do is spin up docker, without ever having touched docker before, and try to run Nextcloud, forget that it exists, and then upgrade it a year later across multiple versions without maintaining the database. Then they obsess about how fast an app loads by refreshing it a whole bunch, and then complain on internet forums that it sucks. This, like many posts, doesn’t have a specific problem for us to help with, no logs or stack traces have been posted, and the subject of the complaint shows just how terrible your understanding of application security is.

So, while there is legitimate criticism of some of Nextcloud’s design choices, this isn’t it. And at the risk of sounding a little gatekeepy, if you post “nextcloud updates break everything” with no context you probably should spend some time gaining a better understanding of how internet facing services work and make an attempt to fix the problem (probably misconfiguration, and in this desktop client case probably a heap of un-updated local software installed alongside the client), which I’m sure people would find if they did the bare minimum of reading a few log files or any of the other things that come with being an application admin.

Not sure why all the downvotes, I use the note to self function for exactly this type of thing all the time. Though to be fair signal is both on my phone and on my computer basically all the time because I use it to talk to everyone too…

EDIT: oh, it’s downvoted because this is the selfhosted community…

Yeah that’s fair. I’ve been running it since about 2018 and never found it too difficult, but messing around with Linux is my hobby so I admit that I enjoy the problem solving aspect. It’s certainly not something you set and forget.

I suggested it here mostly because this particular plugin is both actively developed and quite good in my opinion but it would only be a viable solution if you already use Nextcloud. I’m in no way suggesting OP should install it just for this.

So Nextcloud has a shockingly good 3d model viewer with a long list of supported formats https://apps.nextcloud.com/apps/files_3dmodelviewer . Here’s a quick demo video I made: https://vimeo.com/865805210?share=copy

Unfortunately Nextcloud is a whole can of worms and not just an application you install on your desktop. But it does to all the things you asked for so, worth mentioning I guess? Tagging, sorting, and search are just features of it’s general file management though, they are not really stl specific in any way.

Quick list of supported formats from the github page

3dm 	Rhino 	
3ds 	Autodesk 3D Studio 	
3mf 	3D Manufacturing Format 	
bim 	dotbim 	
brep/brp 	Boundary Representation 	
dae 	Collada 	
fbx 	Filmbox 	
fcstd 	FreeCAD Standard File Format 	
glb 	GL Transmission Format 	binary
gltf 	GL Transmission Format 	separate and embedded
ifc 	International Foundation Class 	no XML or compressed
iges/igs 	Initial Graphics Exchange Specification 	
obj 	Wavefront 	with mtl and textures
off 	Object File Format 	
ply 	Polygon File Format 	
step/stp 	Standard for Exchange of Product Model Data 	
stl 	Stereolithography Standard Tesselation/Triangle Language 	ASCII and Binary
wrl 	Virtual Reality Modeling Language 	superseded by X3D