> How do you keep it secure with such ancient software? What happens when it goes down and you don’t have backups? Only 3 ports are open: 80 443 <another for s

> How do you keep it secure with such ancient software? What happens when it goes down and you don’t have backups? Only 3 ports are open: 80 443 <another for ssh that isn't 20> The nginx is just a proxy to the frontend and a file cache, I'm confident I could rebuild it in under an hour even without access to what is there today. Also confident that if it's compromised it can't do much real harm, I will nuke it. The django is just a thin front end that calls an API, I'm confident that when it gets compromised it can't do further damage as it has no direct access to the DB. And TBH, if/when it dies it will be a kick up the butt to reimplementing this in Go (I've about 60% of that already done but I only look at it once a year for a few evenings) > I can’t imagine a service that’s both unimportant and has so many users. So many questions. It's a platform with 300 forums on it. And I guess if it goes down I discover either the users didn't care (no big loss) or the users really care (and perhaps now the donations would be sufficient to cover the eng time for me to get someone to complete the frontend rewrite in Go). The whole thing is provided for free, and I figure people get what they pay for. I used to feel very emotionally attached, but now I'm quite YOLO about it. I believe these things should be ephemeral, if it turns out it has run it's time then so be it.