I love the simplicity of this, I really do, but I don't consider this SSO. It may be if you're a single user, but even then, many things I'm hosting have their own authentication layer and allow offloading only to some oidc-/oauth or ldap-provider.

Deployment of NC on kubernetes/docker (and maintenance thereof) is super scary. They copy config files around in dockerfile, e.g., it's a hell of a mess. (And not just docker: I have one instance running on an old-fashioned webhosting with only ftp access and I have to manually edit .ini and apache config after each update since they're being overwritten.) As the documentation of OCIS is growing and it gets more features, I might actually change even the larger instances, but for now I must consider it as not feature complete (since people have expectations from nextcloud that aren't met by ocis and its extensions). Moreover, I have more trust in the long term openness of nextcloud as opposed to owncloud, for historical reasons.

I've spent a few minutes with it so far, still looking out for some documentation. I couldn't find a way to mount storage either way so far. Could be done with an nfs or smb share on the vm, being accessed by the phone with an appropriate app, perhaps. Also, I couldn't pass through usb, which is a real bummer...

No Doubt on the happy side? Have you listened to the lyrics?

I use GrapheneOS because it works better for me, but considering their personnel and how they're operating, I still would also trust Calyx. Was clearly the best choice for my fairphone back then.

This has been on X Files, quarantine those people! 👻

The answer is patriarchy and if you think this is her trashing him instead society pressuring her, then check your privilege.

For those of you speaking German: Hast du enen Scherzkeks gefrühstückt?

Kubrick's version of The Shining. Most likely, I would feel differently had I not read the novel first, but the reduction of the story to a Nicholson-show pisses me off to the point where I cannot enjoy it for what it is. I'd rather endure the over four hours of less brilliant screenplay of the 1997 version.

The soundtrack though... (Makes the BS tolerable for me)

Not sure if this is sarcasm, but I sure hope so...

😂 haha, nice one. Is it simple or semi-simple?

I am considering switching as well, for similar reasons. What has been holding me back (besides missing time to plan and do the migration) is thst I don't quite trust ownCloud any more, and due to a lack of documentation, I would want to run it in parallel for some time to get the hang of it before migrating the other users (which adds to the time constraint).

I'll most likely deploy using their helm chart – does anyone have any real-world experience with it?

Finally, I can give it a star, being only on gitlab and not on github

Thanks, the bootstrapping idea was not mentioned in the comments, yet. And your blog looks promising, will have a more through look soon.

Nice, thanks, again! I overlooked the dependency instructions in the container service file, which is why I wondered how the heck podman figures out the dependencies. It makes a lot of sense to do it like this, now that I think of it.

Awesome, so, essentially, you create a name.pod file like so:

 undefined

    
[Unit]
Description=Pod Description

[Pod]
# stuff like PublishPort or networking


  

and join every container into the pod through the following line in the .container files: Pod=name.pod

and I presume this all gets started via systemctl --user start name.service and systemd/podman figures out somehow which containers will have to be created and joined into the pod, or do they all have to be started individually?

(Either way, I find the documentation of this feature lacking. When I tested this stuff myself, I'll look into improving it.)

I've wondered myself and asked here https://lemmy.world/post/20435712 – got some very reasonable answers

Thank you, I think the "less heavy than managing a local micro-k8s cluster"-part was a great portion of what I was missing here.