

you already have a cloud flare tunnel, so you can add a new entry for a domain and point it to another service. cloud flare handles the encryption. for docker, I have my reverse proxy on port 80 doing the routing and the docker route is http://localhost/


that’s quite a long compose file.
the way that I use cloud flare is with tunnels since my ISP blocks my ports. I have cloudflared running that connects to the cloudflare tunnel, which has a map of domain name to a service name, which is how services are accessed externally.
tailscale connects to tail scales main service and that’s how I access internal systems. at least that’s how I’m running it.


tailscale is a vpn. you don’t need cloudflare for it. you do need to set up the tail scale container with your credentials from tail scale, which they have guides for. after that, log in on your machine and click the connect toggle and you’re in.
the exit node is if you want to look like you’re at your host computer.


what an experience! thank you for sharing :)


I’ll include mine to show that it’s not unusual to support them! it’s my favorite and most used self hosted project



I actually just wrote about today’s fun experience! https://gotosocial.michaeldileo.org/@mdileo/statuses/01K7YKQ9584YBY1QTYQ8RMW7SS


not for LLMs. I have a 16GB and even what I can fit in there just isn’t really enough to be useful. It can still do things and quickly enough, but I can’t fit models that large enough to be useful.
I also don’t know if your GPU is compatible with ROCM or not.


i had to do a particular command to get the AMD GPU properly available in docker. i can’t find that if you need


cloudflare happened first and I haven’t been bothered to change it yet


I switched to it because the ISP blocked ports 80/443. It was good and things actually got a bit faster with them handling SSL certs.
but one thing to note is that the free tier has a 100MB file limit. I got around some of that by using the tail scale vpn with a custom domain entry to point to the local network.
I did these changes (wire guard to tail scale, dns to tunnels, etc) at different times, which is why things aren’t very consistent.


if you’re on your home network the address will be the IP address and, if you’re not using a reverse proxy, the port the app runs on.
with reverse proxy: http/s://192.168.8.2 or whatever without: http/s://<IP address>:3000 or whatever the port is


filled! I’m looking forward to the results!


the ISP blocked my ports and cloudflare got me around it. I’ll accept the compromise ;)
it isn’t, I’m hosting a private gitea instance on a home computer.