I have Frigate running with a reverse proxy, a coral, etc. I just use the internal Intel GPU on my CPU and it works with a 1080p and a not-quite-4k stream (4MP maybe?). It’s no sweat for the hardware.

GPU is only used to detect motion, and you can even configure a lower resolution sub-stream from your cameras to reduce that load, but I don’t think you’ll need to.

Once motion is detected, Frigate fires up the coral to determine what is there. A car, dog, person, etc.

I have everything get recorded with no processing to a single WD Purple, the biggest I could afford. It holds months of video before rewriting over old stuff.

I have Amcrest cameras which are rebranded Dahua I think. I’m relatively happy with them, but I’ve always dreamed of owning Axis cameras, though they are a bit pricey. My cameras are on a VLAN that can’t access the internet.

Hope that helps.

I’m not an expert, but I think we need more information.

Removed by mod

Removed by mod

I use apps on my phone, but have no clue how to troubleshoot them. I have programs on my computer that I hardly know how to use, let alone know the inner workings of. How is running things in Docker any different? Why put down people who have an interest in running things themselves?

I know you’re just trying to answer the above question of “why do it the hard way”, but it struck me as a little condescending. Sorry if I’m reading too much into it!

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.

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.

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.

I’m not smart, can you tell me if having it behind a reverse proxy with certs and everything fixes any of these flaws?

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

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?