Quote:
Originally Posted by DaFace
The good news is that (as noted above), there are migration tools that should make SOME of the transition a little easier. But as you alluded to, there are endless little snags you tend to run into along the way, and it doesn't help that this isn't even a "pure" install of vB 3.8 - it's been upgraded like 10 times starting with 2.1 (I think), so there's all sorts of shitty code lying around that could cause issues along the way.
In the end, it's entirely possible that Kyle will choose to just migrate to a new server and keep vB 3.8 as is. It's old, and it's shitty, but in theory just getting onto a new box that keeps the db on an SSD would take care of most of our issues, so if that's the easy path forward compared to starting from scratch on new software, it is what it is.
|
If we just set up a new server from scratch, Xenforo or whatever, and had a cutover day where everybody is redirected to that new setup, isn't that enough? We could keep the old vBulletin 3.8 thing up under a different URL, and reference it as needed, but lock out all new posts. The old DB would stop growing, and the new server would be all new tech stack whatever and hopefully buy another 30 years. Maybe this has been proposed and shot down. I realize even this is still a project, but seems like one that is about as lightweight as could be hoped for.