Awesome Self-Hosted

Looks like it’s mostly for live TV? I haven’t had cable in a long time, don’t really need to record things.

I like getting Bee-link boxes - they can be upgraded to 64gb RAM, have plenty of CPU, and can have two drives. I run Proxmox on them and make VMs that then run my services in docker.

There’s been a lot of talk about N100s as well. I haven’t looked into them much, but I assume they should be similar. Looks like their max memory is 16gb. I’d stick with Bee-link.

I’m in this comment.

And you can self host it!

How are you persisting Immich’s database?

I think you dropped this: \

I definitely trust Proton much more than I trust myself.

If you’re not paying for a service, you’re likely being monetized by watching ads or providing personal data to companies that don’t necessarily have your best interests at heart.

This is a bit out of date. Nowadays, you pay for the service and are monetized by watching ads and providing personal data to companies that definitely don’t have your best interests at heart.

Why would you need to continue using the self-signed certificates for the Cloudflare connection? Just use the valid certificate for all connections.

Damn, where’d you find that deal?

I mean, you don’t have to watch it.

Both. For physical documents, you add an ASN and store the document in a binder in ASN order.

You want to split your domain so it resolves to a private IP internally and a public IP externally. So, your internal DNS server should return internal IPs.

Good point!

Docker network pools are huge by default. I had to change this as well.

This article covers the issue and the solution in detail:
https://straz.to/2021-09-08-docker-address-pools/

If you just want the solution, skip to the section titled How to configure docker to allow >500 bridge networks. I think you’ll need to remake all your networks after making the change, if I remember correctly.

Here’s my config now:

$ sudo cat /etc/docker/daemon.json
{
  "default-address-pools": [
    { "base":"172.16.0.0/12", "size":24 },
    { "base":"172.17.0.0/12", "size":24 },
    { "base":"172.18.0.0/12", "size":24 },
    { "base":"172.19.0.0/12", "size":24 },
    { "base":"172.20.0.0/12", "size":24 },
    { "base":"172.21.0.0/12", "size":24 },
    { "base":"172.22.0.0/12", "size":24 },
    { "base":"172.23.0.0/12", "size":24 },
    { "base":"172.24.0.0/12", "size":24 },
    { "base":"172.25.0.0/12", "size":24 },
    { "base":"172.26.0.0/12", "size":24 },
    { "base":"172.27.0.0/12", "size":24 },
    { "base":"172.28.0.0/12", "size":24 },
    { "base":"172.29.0.0/12", "size":24 },
    { "base":"172.30.0.0/12", "size":24 },
    { "base":"172.31.0.0/12", "size":24 }
  ],
  "log-opts": {
    "max-size": "1g"
  }
}

I still need to get this back up after the database requirement took it down

Yes, that would work. Highly recommend installing docker and running in containers. (Except Tailscale, probably; that would be native.)

I’m on pfSense+, but I’ll be switching to opnSense eventually.

Oh, I assumed you could replace them. If it’s just remove, you’re 100% right.