The config files should be in the volume you mounted in your NPM container. Probably /data/cong.d/. You can either edit them like normal nginx configuration files (NPM just runs normal nginx in the background), or you can copy them to a standard nginx instance.
Looks like most of that install script is just creating a letsenceypt cert for you. If it's not working, you can probably just create one yourself or use a wildcard cert if you already have one.
The rest is just an nginx instance being used to proxy a connection. If you're already using NPM, anyway, you might as well just use that. No reason to run extra instances.
Or start with the signal one and add your other proxy config files to that.
"Nice" is entirely subjective. I think my site is nice, but someone else might think it's garbage.
I use Hugo to generate my site. It's not wysiwyg, but it supports markdown for pages, which is even simpler than html. It also has a live server mode, where you can see changes immediately.
The community has a created whole gallery of themes (templates) that you can use. It might be worth looking through the gallery to see if you think any of them look "nice" to you.
But if Lemmy was just seen as a federated message board, it wouldn't have nearly the users that it does. It's popularity rocketed (compared to the rest of the Fediverse) specifically because it takes so much of it's style from Reddit.
Interesting! Not something I've encountered, but I suppose that's what makes the Fediverse special! We can all control how we want to interact with things.
Another vote for purelymail, here, @Gobbel2000@programming.dev. Easy to set up and I've got full dmarc/dkim/spf. You can pay the flat $10/yr, or you can pay- for-what-you-use. I don't send a lot of attachments, personally, so my estimated bill is like $4.50.
I've mentioned this before, but I'll say it again: I like the concept, but I can't help but feel that the presentation has been consistently poor.
The earlier releases left a sour taste for some by highlighting connections to cryptocurrency, and now it's literally being rebanded to "bitsocial"? With Bitcoin being the widest known cryptocurrency in the world, it's definitely not alleviating the concerns that this is some sort of cryptoscam.
My only question, which I feel wasn't clearly explained in the video, is whether he did any extra work on the Windows machines. He explains his "fresh install" mythology for the Linux tests, I don't recall him explicitly saying that he did the same for the Windows machines.
I'd be surprised if Windows actually ships with the newest drivers for the newer cards. For apples to apples, either run both OSes out of the box, or get proper driver's both.
You can show your personal support for something by upvoting it or your opposition to something by downvoting it, but if you don't want to take a stance on something at all, you don't have to.
It's an entirely optional mechanic. You can fully utilize Lemmy to view, post, and comment without ever voting if you don't want to.
As far as I'm aware, the votes don't really matter, anyway. Lemmy doesn't seem to use karma the way that Reddit does. i.e. I've never seen a post removed because the user didn't have enough karma, etc.
I have two domains through Cloudflare. They don't mark up to price at all, so they're basically the lowest price you'll find that isn't a gimmick.
I pay $6.50 for one and $10.46 for the other. Privacy is free and by default.
No harm in getting your domain from them. Just beware that when you create a DNS entry, they default to proxying the incoming connections. It is super easy to turn that "feature" off, you just have to remember to do it whenever you create a new record.
ufw is just a fancy frontend for iptables, but hasn't been updated for nftables, yet.
Firewalld is an option that supports both, and if you happen to be running cockpit as well, the cockpit-firewall plugin provides a simple GUI for the whole thing.
He does refer to the pi as a gateway, so you would be right about it coming before the router. In that case, the pi would be the device handling NAT and forwarding ports.
So I think he's describing it accurately... it's just not a common setup to see these days.
I have my reverse proxy in a cluster, so it'll survive one of the nodes going offline. My router is still a SPoF, though, as is my modem. Not to mention the physical stuff, like a tree falling on the cable lines.
For a home environment, there's realistically always going to be a couple SPoFs, you can just move it around a bit.
You'll need a single DNS request, known as a "bootstrap" request. Your ISP will see a single DNS request to Google or Cloudflare or whatever, then everything after that will just look like normal https traffic.
That said, if your ISP is blocking and denying ALL dns requests for some reason (making the bootstrap request impossible), then you could still define the address locally. At that point, though, the ISP is likely blocking the IP addresses, too, so resolving the address is a bit moot.
The config files should be in the volume you mounted in your NPM container. Probably /data/cong.d/. You can either edit them like normal nginx configuration files (NPM just runs normal nginx in the background), or you can copy them to a standard nginx instance.