shiftymccool

I treat it like a junior dev, it gets the gist but may make mistakes and I work it into something usable.

I also like it to save keystrokes, like when I'm building an object, it knows the structure of that object, so it ends up being tab/enter/tab/enter/... Same process for creating converters between types.

I don't expect much from it, but it does save time and keystrokes

pre-internet definition of meme

Jesus wept

I did, best move ever

Don't have children

A+ my friend. Solve this one, and you solve most of the others.

However, eating animals isn't inherently bad on its own. It's the SCALE at which we do it. Animals have been eating animals since there were animals, and as long as there is a natural balance, this can be a good thing. Factory-farming for billions of humans is where it all falls apart (much earlier than that, actually)

You either care about ~~the future of humanity and their place on~~ Earth, or you don't.

I couldn't give less of a fuck of humans make it or not, but the Earth and its other inhabitants don't need to go down with the shitty ship humans built.

I agree with your overall point, though, but I think the main solution to the problem is simply to use a condom. Most of the rest will sort itself out or be much easier to solve after there are less of us.

When I turn off Wi-Fi, I'm not on the same network as my server, it's my carrier network so all the internet hops are expected.

The way it's working now is I have a domain (example.com) that is set up on cloudflare DNS. I added a tunnel in cloudflare zero trust, which generates certificates you add to your server to encrypt traffic from your server to cloudflare. I have added these to traefik to be served with my service url (service.example.com). Then, I added a route in cloudflare for service.example.com.

This works fine. But, what I've also done is add a local DNS entry for service.example.com so when I'm on my LAN, I access it without going out to the internet and back (seems like a waste). However, this is serving the origin server certs from cloudflare, which causes trust issues

I'm using docker for everything: traefik, cloudflared tunnel, and my services on the same hardware. The tunnel just runs, and it's configured on cloudflare zero trust to talk directly to the container:port over the docker network.

That's what I'm settling on. However, it's not just about trust, some of the services I'm exposing deal with moving files and I'm mostly interested in higher speeds associated with local transfers as well as not using up my internet data cap.

You're right, I'm using the cloudflare DNS challenge to get let's encrypt certs. I'm definitely hitting traefik. I'm testing by turning the Wi-Fi on my phone off/on and opening the page after. I get the same cert every time but it's not trusted when on Wi-Fi. This makes sense since it's the origin server cert which is meant to encrypt traffic between my server and cloudflare. To add more certainty, when Wi-Fi is on, a traceroute shows only one hop to my server and shows a bunch of hops when it's off.

Barring any Traefik tricks that allows me to accomplish what I'm after, I was thinking of going with your "third" option of just letting it use Cloudflare for everything but, I had to check with the experts first before just doing it.

I have some apps that complain or, in one case, flat out doesn't work if the cert is invalid. I've been working around it (sort of) but it would be nice to have it set up "correctly" for once. If routing all traffic through Cloudflare is the answer, so be it ¯_(ツ)_/¯

If I use the Cloudflare origin server certs, the browser shows insecure and the message is "certificate not trusted" which is the same message as self-signed, if I'm not mistaken. I'm not sure what other details are relevant as I'm still new-ish to the networking portion of this home server thing. I'm happy to answer any questions if you suspect something.

I'm not using self-signed anymore, I'm getting them from Cloudflare via DNS challenge