dont

joined 8 months ago
[–] dont 5 points 2 weeks ago

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

[–] dont 3 points 1 month ago

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.

[–] dont 1 points 1 month ago

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

[–] dont 7 points 1 month ago (5 children)

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

[–] dont 1 points 2 months ago

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

[–] dont 3 points 2 months ago

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?

[–] dont 10 points 2 months ago

Heracles 🤬 It's Heracles, for crying out loud...

[–] dont 9 points 3 months ago

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

[–] dont 2 points 3 months ago

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

[–] dont 2 points 3 months ago

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.

[–] dont 1 points 3 months ago* (last edited 3 months ago) (2 children)

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

[–] dont 2 points 3 months ago

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

39
submitted 3 months ago by dont to c/selfhosted
 

I'm afraid this is going to attract the "why use podman when docker exists"-folks, so let me put this under the supposition that you're already sold on (considering) using podman for whatever reason. (For me, it has been the existence of pods, to be used in situations where pods make sense, but in a non-redundant, single-node setup.)

Now, I was trying to understand the purpose of quadlets and, frankly, I don't get it. It seems to me that as soon as I want a pod with more than one container, what I'll be writing is effectively a kubernetes configuration plus some systemd unit-like file, whereas with podman compose I just have the (arguably) simpler compose file and a systemd file (which works for all pod setups).

I would get that it's sort of simpler, more streamlined and possibly more stable using quadlets to let systemd manage single containers instead of putting podman run commands in systemd service files. Is that all there is to it, or do people utilise quadlets as a kind of lightweight almost-kubernetes distro which leverages systemd in a supposedly reasonable way? (Why would you want to do that if lightweight, fully compliant kubernetes distros are a thing, nowadays?)

Am I missing or misunderstanding something?

3
submitted 8 months ago* (last edited 8 months ago) by dont to c/mikrotik
 

I have just ordered a CCR2004-1G-2XS-PCIe to be used as the firewall of a single server (and its IPMI) that's going to end up in a data center for colocation. I would appreciate a sanity check and perhaps some hints as I haven't had any prior experience with mikrotik and, of course, no experience at all with such a wild thing as a computer in a computer over pcie.

My plan is to manage the router over ssh over the internet with certificates and then open the api / web-configurator / perhaps windows-thinyg only on localhost. Moreover, I was planning to use it as an ssh proxy for managing the server as well as accessing the server IPMI.

I intend to use the pcie-connection for the communication between the server and the router and just connect the IPMI and either physical port.

I have a (hopefully compatible) RJ45 1.25 G transceiver. Since the transceiver is a potential point of failure and loosing IPMI is worse than loosing the only online connection, I guess it makes more sense to connect to the data center via the RJ45-port and the server IPMI via the transceiver. (The data center connection is gigabit copper.) Makes sense? Or is there something about the RJ45-port that should be considered?

I plan to manually forward ports to the server as needed. I do not intend to use the router as some sort of reverse proxy, the server will deal with that.

Moreover, I want to do a site2site wireguard vpn-connection to my homelab to also enable me to manage the router and server without the ssh-jump.

Are there any obstacles I am overlooking or is this plan sound? Is there something more to consider or does anyone have any further suggestions or a better idea?

view more: next ›