We keep running out of disk space, and overall performance is sometimes unsatisfactory. As such, there will be some downtime in the coming days, as services on the vault are migrated piece by piece to newer hardware. The new setup will provide a much more modern CPU, plenty of free disk space on faster disks, a lot more RAM, and the option to add a SSD accelerator, if the need for it arises once everything is said and done.
Process
If you’re seeing “Error 503 (Service is migrating to new hardware)” coming up when visiting any of the vault pages, that’s why. I have to take down each component to ensure data consistency, move said data (quite a bit, in some cases), test on the new setup, and update DNS once it’s back up. This can take many hours for the biggest components, so patience will be needed.
Some of the software can be a bit finicky. I’ll be taking this slow over the coming days, and use the opportunity to improve some aspects of that. I’m still evaluating the new setup, so I don’t expect this to start immediately.
If you see issues on already migrated services, or have questions, please post here!
If you are able to allow us to delete “previous revisions” of our own modules, I could probably free up a ton of space for my own module: The Scroll | The Neverwinter Vault
Possibly not a great deal of space in the grand scheme of things, but being able to manage our own content (at least the very old stuff) may go some way of helping reduce some?
Say 1GB a revision, with 35 approx per page and 29 pages of revisions: around 1TB data perhaps?
P.S. I would like the option to keep some of the older revisions (just in case).
Yes, this would be good. Like ideally I would prefer to keep just the major releases, but until I reach the next release, it would still be good to be able to give people the minor interim releases, without having to feel bad that I’m hogging a bunch of space.
I agree that project and version management also needs quite a bit of love. This current effort is mainly focused on moving everything over safely though, and while doing so, optimising the hosting aspects of the software.
Any procedural changes on the CMS (or even a better replacement for it …?) must follow at a later date.
I saw that too. But then opening the forum again logged me in. Overall, SSO with Drupal was a mistake. Now it’ll be hard to get rid of unless we make every single user set a new password here. Still mulling that over - in the interim, will fix the redirect at some point (probably when the rest of Drupal migrates …)
One very, very minor thing. New version of Discourse? The only thing is the vertically aligned controls that you get when you click on your avatar appears to have some new controls but not one of the control’s icons has a tooltip. Trying to figure it out, I’m not sure what they’re supposed to do (especially the “Rubik’s cube” at the bottom of new controls).
They have tooltips for me, just takes a moment to show. Discourse is rolling out a new main menu/sidebar thing that’s coming with version 3.2. This is part of that already, I think.
But maybe I have the wrong link?
