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:

[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.

Understood, thanks, but if I may ask, just to be sure: It seems to me that without interacting with the kubernetes layer, I’m not getting pods, only standalone containers, correct? (Not that I’m afraid of writing kube configuration, as others have inferred incorrectly. At this point, I’m mostly curious how this configuration would be looking, because I couldn’t find any examples.)

Thank you for those very convincing points. I think I’ll give it a try at some point. It seems to me that what you’re getting in return for writing quadlet configuration in addition to the kubernetes style pod/container config is that you don’t need to maintain an independent kubernetes distro since podman and systemd take care of it and allow for system-native management. This makes a lot of sense.