Maybe he's #winning?

ya think?

I've never tried it but I like the idea of it. I've been having a protein shake instead of breakfast for years, so this isn't much of a departure.

If I were to try it, it would be the lower carb versions like the black edition, and also without sweeteners.

The only lingering doubt I have is that it's arguably ultra-processed (and this applies to my protein shake as well). Even if the individual ingredients aren't bad, have our bodies evolved to ingest food like this without long term side effects? I guess time will tell.

There are 2 reverse proxies involved. One is Nginx which is used to front both the Lemmy UI and the Lemmy backend. That's what the 'proxy' container in the docker compose file is for. It seems to be a required component of the application stack as different request types to the same host FQDN are sent to different backends ('upstreams' in network speak). You could use Caddy here instead if you wanted, which is the point of this page: https://join-lemmy.org/docs/administration/caddy.html. However, that config doesn't work for the latest version of Caddy (you'll get an error about stuff being outside of the site block).

The other one (could either be Nginx again or Caddy or anything else you want instead) is to front the whole thing and provide TLS termination using Letsencrypt. This bit is explained here: https://join-lemmy.org/docs/administration/install_docker.html#reverse-proxy--webserver

I am not telling you to quit I'm not telling you to know more. I was merely suggesting that the devs put out the minimal required documentation for an experienced admin to get it up and running, while also suggesting a way to not waste money.

Sorry it came out wrong.

Do you have a local device you can try all this on first so you're not wasting money?

I agree the guides aren't great, but they assume you have some experience doing this stuff.

Nevermind that, is there a way to block any post with 'AI' in the title?

I used to do all this, but then I gave up and started paying for NextDNS. It's like having your own Piholes in the cloud. It's like £18/year and is way more reliable than self hosting, especially for something as crucial as DNS for your home. It also has excellent parental controls if you need that, multiple profiles, good logging and analytics and a decent looking privacy policy.

Sure, it's not as fun as self-hosting but it's better then getting shouted at every time someone's app stops working because of some glitch in your setup.

I'm currently trying to get Lemmy working on Azure Container Apps and Azure Postgres Flexible Server. I've got it all deployed, but I'm having some issues with the reverse proxy.

Regarding the 'best' choice - well it depends on what you mean by 'best'. AKS will be the most flexible and ACI will probably be the simplest (if it will even work for Lemmy - I haven't looked at ACI in years). Container Apps will probably be somewhere in the middle. Container Apps is just an abstraction over Kubernetes, so in theory you should get the scalability and flexibility of k8s without the overhead of managing a cluster.

I got Lemmy up and running on my home Rapberry Pi microk8s cluster pretty easily, so it will work fine on AKS for sure.

I'm looking at Container Apps just as a pet project because I've been waiting for a product like this for years. Kubernetes is awesome, but has always been too complicated for the average software developer to use. It needs a layer of abstraction and that's what Container Apps is. So anyways I figured running Lemmy on it would be a good way to test drive it.

As I said though, I've run into some issues and am almost at the point where I was going to ask for help. If anyone's interested, I can post links to my Github repos with my Terraform code and all that.

If you make the bread yourself (i.e. with a breadmaker) it's dirt cheap. I buy flour and yeast in bulk and it costs bugger all per loaf.

You could maybe argue bread isn't healthy because it's technically a processed food (flour, carbs, etc.), but as others have pointed out moderation is key.