The price rboem problem is that the log file is inside the container in the www folder.

Edit: typo

I’ve read the article and I couldn’t see any implication of Seagate. I’m not saying anything about your story, shame on Seagate, but I don’t see what that has to do with the scandal in the article.

ChatGPT summary:
The podcast episode “Byebye Raspberry Pi” discusses the evolving role of Raspberry Pi devices in 2025. The host evaluates self-hosting options, the growing appeal of thin clients over Raspberry Pi due to cost and performance, and the use of containers for flexible testing environments. They also touch on repurposing older hardware and share personal experiences with self-hosting and audio editing. The episode covers modern alternatives to Raspberry Pi, such as x86 computers, and invites audience feedback on their use of devices for hosting services. The discussion includes tips on managing disk space and remote access with WireGuard.

Oh, I really didn’t know that. Thanks

No no, what I meant is that if I connect to your server without the certificate installed don’t I just get the warning and I can still get through?

Beside the fact that you would like to understand if you’ve done everything properly (that’s good, but I can’t help you here), a VPN on a smartphone can be always active. Mine is always on and I’ve never noticed any battery problem. If you prefer something simpler there’s Tailscale.

I don’t know much about certificates, but doesn’t that just alert the browser that the certificate is not trusted and you can decide if keep going or not?

Good question, I’m interested too. Personally I use this kind of mapping

volumes:
  - /var/docker/contanier_name/data:/data

because it helps me with backups, while I keep all the docker-compose.yaml in /home/user/docker-compose/container_name so I can mess with the compose folder whithout worrying too much about what’s inside of it 🙈