To access things outside of your LAN (for example from your phone while at the grocery store), each service gets a DuckDNS entry. “service.myduckdns.com” or whatever.

Your phone will look for service.myduckdns.com on port 443, because you’ll have https:// certificates and that all happens on port 443.

When that request eventually gets to your router and is trying to penetrate your firewall, you’ll need 443 open and forwarded to your Debian machine.

So yes, you have it right.

Also forward port 80.

That question is a little bit out of the scope of a forum like this. A question like that would better be answered by the nginx documentation. Sometimes the project documentation might have a blurb about nginx configuration specific for that project. For example, Immich.

For the most part, you only have to reference the nginx documentation. I’ve never looked at the Immich config above until now, and my Immich server works great.

I’ve had a reverse proxy for years, but the config files are very foreign to me because I use Nginx-Proxy-Manager. NPM makes nginx usable for dummies like me, at the expense of gaining a deeper understanding of how it works. I’m ok with that, but you might feel differently.

I’m not up to date on the current market, but I have Ikea blinds that are battery operated which I control from HA. The batteries are rechargeable, and the batteries themselves have micro-USB ports for charging.

One option would be to buy these, see what kind of charging port they come with these days, and try to make some physical modifications to jam a USB connector in there. From there, you just have to figure out the solar part. A lot of solar charge controllers have USB ports which should work to charge the battery, but they are clunky and you’d have to mount it on the wall probably.

For what it’s worth, the batteries in these shades last quite a long time… Looking at one of them, I last charged it in September 2024, and it’s still at 72%. It goes up/down at least once a day I’d say.

GOOD point

Yes, I agree. Maybe that will happen, or maybe it won’t.

That’s not quite how a pool of money works.

Once you fill the gas tank in a motorcycle, you can’t pick which molecules of gas go towards acceleration and which ones go towards idling at a red light.

Are we to assume you think this is an apology?

There are other options… Lemmy development could stop and plenty of people would keep using it in its current atate. Maybe it’d even continue to grow.

Or maybe the developers quit and another team steps in? Open source projects are never fully tied to a single developer team.

The low server cost doesn’t change anything for me. I’m just a person who won’t donate if any amount goes towards keeping that place running under the current admins.

Some fraction of my donation would go towards the $30. Any amount of money going from me to .ml, be it $10 or $.00001, is too much.

I know $30 is “not much”, but the amount doesn’t change my principles.

For someone like me who wants to see Lemmy be a place that’s owned by users, run by users, and moderated sensibly, what should I do? I have a problem with supporting the lemmy.ml instance.

Looks like you can add these sensors. Verify on the product page, though. I only just looked at the WS-5000.

I agree with Ambient Weather. Spend as much as you’re comfortable with. Make sure it has a WiFi base station. I’m using this integration installed through HACS. It’s solid.

For remote access, wireguard is great. You can access stuff via their internal addresses.

One of the few podcasts I listen to sometimes. Wishing them well and thanks for all of the hard work.

There are various ways to use it, yeah.

I’m a fan of Dockge. Nice simplicity, easy to update container stacks, etc. etc.

That’s exactly how I’d use it. It’d have a time delay, too.

Also, completely unrelated, but it’s odd seeing a totally normal, non-tankie user from lemmy.ml.

It looks like the hEX refresh is the same price from that vendor.

RB5009 is better but more expensive. There’s a PoE version that can power your WiFi APs in the future.

I also question the decision to put OpenWrt on it. RouterOS is solid. There’s a learning curve, but it’s worth it if you’re a nerd.

A while back, the docker installation instructions just had “lemmy:latest” as which version to pull. The Lemmy devs aren’t the brightest, and the beta versions are included as “latest”. Now the instructions have you put the specific version to pull, like “0.19.10”.

I wonder if that’s what happened?

I already have this set up and it works well. Sometimes I turn the TV off and stay in the room on my laptop for a while, and the lights turn off. It’s easy enough to turn them back on but I’m wondering if mmWave could help.