
If you’re worried about that possibility, then you should mitigate against it. I’m not saying everybody should do it… all I’m saying is that rejecting the idea out of hand is not necessary.

If you’re worried about that possibility, then you should mitigate against it. I’m not saying everybody should do it… all I’m saying is that rejecting the idea out of hand is not necessary.

I don’t feel like I’m risking anything… I feel like I have an understanding of the attack vectors and I’ve mitigated those to a level that’s acceptable to me.
Risk tolerance is something we all have to judge for ourselves.

I actually started on a VPS… I moved off because I was pegging the RAM and adding more to my plan was quite expensive. Performance is MUCH better on my home server with plenty of RAM.

I don’t get this perspective. A reverse proxy pointing at containerized applications gives you plenty of buffer between the scary internet and your personal files. Don’t bind mount your entire host file system to the container, and only open/forward the ports you need.
There are things you have to get right, but there’s no reason to discard the idea altogether.

I find myself commenting three questions on any post about a new application somebody developed.
Personally, I wouldn’t mind if all new app posts were required to answer these questions for their post. It doesn’t discriminate, it just asks them to lay their cards on the table for everyone to see. The community can judge from there.
Welcome fellow instance owner!