tool

WSL is actually pretty OK now, it’s lightyears ahead of what it was. You can even run systemd in it now.

That certainly makes me feel better for letting the Magic Smoke out.

I don’t think it became easier at all until it was forked off into Xorg and they started making dramatic improvements.

I think it was trial and error for hours at least.

It certainly was until I discovered the monitor I hadn’t fried had the modelines printed on a sticker on the back…

So I’m not the only one who fried a monitor trying to get X11 working…

and how hard it was to get x11 working

Oh good God. If you really want to test someone’s resolve, sit them down at an old computer with a CRT and no Internet and have them configure X11 from scratch. Seeing that default X11 crosshatch background for the first time was practically orgasmic after the bullshit I went through to make it work.

That’s one of those traumatizing experiences I’d completely blocked from my memory until I read your comment.

Traumatizing experience #2 that just came back to me was getting a winmodem working and connected to my ISP via minicom.

At work/for business, you can’t beat Veeam. It’s the gold standard and there is literally nothing better.

At home, Duplicity. Set it up once and then just let it go, and it supports a million different backup targets you can ship your backups off to, including the local filesystem. Has auto-aging/removal rules, easy restores, incrementals, etc. Encrypts by default too.

I’ve been using vscode since it was released and I never knew that was an option. Thank you!

docker (while you don’t need it to host things, it makes your life 10x easier)

…until you have a single extra space character hiding 20 lines into your compose file and the whole thing falls over the next time you try to bring the containers up.

Lint your code and configs every time!

Make sure the postfix container is connected to the lemmyexternalproxy network.

Make sure the networks section at the top of your docker compose file looks like this:

Gotcha. I understand your opinion, but they seem pretty confident about their ability to continue to deliver.

And also, never get into bed with Oracle. I quit a job once when they started seriously sniffing Oracle’s panties. Oracle has hostages, not customers.

Look in to Rocky Linux. It was started by the original developer of CentOS the day Red Hat announced that CentOS would be moving upstream of RHEL. They’ve already put out an announcement saying that it’s essentially going to be business as usual for them.

Fedora isn’t the testing distribution for RHEL, CentOS is. Fedora is upstream of CentOS and could be viewed as the bleeding edge in that regard. CentOS used to be downstream of RHEL, but that changed a few years ago when IBM did its first shitty thing at Red Hat. The tree is like:

Fedora (Top of code stream, “unstable” from a business perspective)

|

|

v

CentOS (midstream, much less frequent feature updates)

|

|

v

RHEL (end of stream, stable/predictable/reliable/etc)

And I couldn’t disagree more about RHEL adding little value. You’re not going to run a server on Fedora for something you want/need to rely on, and especially rely on not to change much/cause breaking changes. That’s what RHEL is for and it is the gold standard in that regard.

And that’s not even mentioning the fact that Red Hat support is some of the absolute best in the world. Motherfuckers will write a bespoke kernel module for you if that’s what it takes to fix your issue. Not sure if that’s still true after the IBM takeover though, but that was my experience with them before that.

Oh my God, thank you for this. I would give you “Lemmy Gold” If I could.

I’m seriously missing the ability to jump to the current/next/previous parent comment. I make heavy use of that and only Jerboa has it right now, I think.

Liftoff is great, has a lot of potential too. Devs in their Matrix room are cool.

You’re welcome! Docker/Docker Compose are a great tools once your wrap your brain around them and why containers are ephemeral, etc. Docker’s docs could really use improvement though, you never know if what you’re looking for is in the section that’s dedicated to to that feature, or if the only mention of it is buried deep in the 10th sentence of the 20th paragraph on a completely different page that has absolutely nothing to do with what you’re looking for.

Docker at this depth is a bit new to me. Curious. Why does it need to be bound to the lemmyinternal and lemmyexternalproxy nets, and not just internal?

Because the “lemmyinternal” network is set as an internal type network in the Docker compose file, which is exactly what it sounds like: internal-only. Postfix wouldn’t have a way to egress to the WAN if not connected to the “lemmyexternal” network, so the initial connection step to send the mail from the “lemmy” container would work, but postfix sending it would fail, as it doesn’t have a route out to the Internet.

It’s because the postfix docker container is not connected to a docker network that has access to the “lemmy” or “lemmy-ui” container, it’s being connected to the “default” docker network. I submitted a pull request for it here that should fix it.

To make it work in the meantime:

1. cd into the Lemmy install directory and run docker compose down

2. Edit docker-compose.yml in the same directory, and in the postfix section, put this just below the postfix: line:

    networks:
      - lemmyinternal
      - lemmyexternalproxy
   

3. Run docker compose up -d

The indentation of that code is very important. Your postfix section should look like this when it’s done:

That should connect the “postfix” container in to a docker network that can communicate with the “lemmy” and “lemmy” UI containers. There’s another bug in the default config that doesn’t assign a hostname to all the containers, but it doesn’t always manifest all the time. You can fix that by making sure each service has a hostname assigned to it, like hostname: lemmy, hostname: lemmy-ui, hostname: postfix etc in the respective service’s section of the service: section of the docker compose file.

Ok. I’ll give it a try some time this weekend, thanks for the tip. Hopefully I can contribute in the future.