Website update!
After releasing the website at the end of last semester, DevOps has been working hard on fixing all problems that have come up. We have now fixed every single bug* in the bugs document created when we first released the website. So, as of this moment, there are no more bugs. None. It’s perfect. Any report of bugs going forward will be treated as user error. If you still decide you want to report a bug or request a new feature, you should do so by creating an issue on GitHub , as the bugs document is no longer being checked as actively as at the start of the semester. Addressing the server situation
For a while now, we’ve had a powerful server gathering dust in our storage room. Not anymore. After a long night of troubleshooting we managed to get our newest addition to the server rack, Netrunner, up and running! With 192GB of RAM, it’s 3 times more powerful** than our second most powerful server, with a measly 64GB. We’ve fitted it with new storage, replaced the mismatched PSU, and filled it with as much RAM as it can take. Now, the only thing remaining is to put it into the server rack where it belongs… and maybe also figure out what to use it for, but that’s a problem for future DevOps. As for Frukt, our other dead server, it still rests in the storage room, awaiting repair indefinitely.
Infrastructure modernization
Currently, the website’s code is only stored on GitHub. This is not a future proof solution, as we’re relying on third-party infrastructure. Our new and exciting project will solve this by transferring the code to an in-house solution which has been proven reliable by its age and still widespread*** usage. I am, of course, talking about copying our files onto 10 floppy disks. With a total of 14.4MB of storage, this will provide enough space for the website at its current state, around 10MB, and will continue to provide ample storage for years to come. The floppy disks and the accompanying floppy disk reader have already arrived at the workshop, so we look forward to getting started with the project soon.
Our decision was also partly inspired by the old website’s backup, which is a CD taped to the wall. I apologize in advance to the DevOps team 10 years from now, who must follow this tradition and store their new new website on 200,000 punch cards.
What’s next?
Aside from social arrangements and other mini-projects we might find along the way, our main goal right now is still developing the website, with plenty of features yet to come. We have weekly meetings where we continue development and feed our Wordle addiction. If you’re interested in joining DevOps, you should check out the applications page at the start of next semester. We’re losing a few members, so might have some spots opening up as well 👀
* Some still awaiting review
** The CPUs might be getting a bit old but the RAM makes up for it, right?
*** Debated, but sources like this still treat it as the default
Until next time,
The Democratic People's Republic of DevOps