Quote:
Originally Posted by Bearcat
DaFace is the only mod with access to the database and 1) highly doubt he has access to fix anything at thay level, 2) he isn't even in IT and could probably walk circles around your IT adjacency, and 3) feel free to PM AC with your expert opinion of what's wrong, I'm sure he'd appreciate someone jumping in to fix this free thing you use on his dime.
|
From my perspective, the main issue is that we're on software that was written in 2008, and it's so old that we can't even be on the newer versions of PHP and MySQL, so even the backend kind of sucks.
It's compounded by the fact that it's really difficult to "right size" a server for our use case. It needs to be able to handle gameday traffic, but normal volume is only about 10% of that level, so we've got ad revenue* that's about 10% of what we'd need to support peak usage. So it's a lot of duct tape and bubble gum to keep us moving along.
But as you alluded to, I've never claimed to be some sort of IT guru. My only superpower is being willing to spend the time trying to fix things as best I can. AustinChief has far more knowledge than I do but far less time.
In the end, the "right" solution is almost certainly to move to a new server and new software, but 1) it's an astronomical amount of time to do that and 2) the "look and feel" of ChiefsPlanet would change dramatically in the process. We probably just need to rip off the bandaid, but that's easy to say when you're not the one who has to put the hours into it.
*As a note here, I don't actually have any visibility into our ad revenue and costs - that's all AustinChief's territory. I'm just guessing.