#Unofficial morrowind patch changes software

It has been updated to the latest available version, fixing a lot of nasty security issues. too much, weвЂ™re using Nexus Repository OSS to act as a caching proxy. Since weвЂ™re automatically building OpenMW on every commit using GitLabвЂ™s continuous integration to avoid hammering NuGet, Chocolatey, Debian and co. Our nginx config was overhauled and factorized to make our servicesвЂ™ configurations more uniform: same modern TLS parameters, usage of http2, same Cloudflare configuration, more efficient serving of big files for, etc. We lowered the process priority of the backups, which fixed the issue and appeased our monitoring. Also, since this information is available to everyone, you can check for yourself if ' is down for everyone, or is it just me'? This uncovered an issue with our backup system: in the middle of the night (European time) our backups are kicking in, and were doing some heavy compression operations which result in a massive slowdown of the website, generating timeouts. WeвЂ™ve set up a status page at /status, thanks to UptimeRobot, to monitor all of our services and to get notified in case one of them goes down. It also allowed us to make use of aggressive caching which significantly improves its performances and makes it way less taxing resource-wise. Switching our old wiki to read-only allowed us to disable a ton of features. So we made our wiki read-only and available at and moved the content to GitLabвЂ™s wiki, reducing the maintenance cost of our MediaWiki.

Now that OpenMW is slowly reaching feature parity with MorrowindвЂ™s original engine, most of the information on the wiki is no longer being updated.

#Unofficial morrowind patch changes software

WeвЂ™ve long been using MediaWiki (the same wiki software used by Wikipedia itself!) to document everything, along with a plugin to bridge accounts between the forum and the wiki. Moreover, we stepped up our anti-spam game: the forum should be kept tidy now with less human intervention necessary, and weвЂ™re now reporting spammers to Stop Forum Spam. We also switched to MySQL for the search engine which reduces the database table and makes the search not only better but also faster. So not a lot has changed on this side except that we upgraded it to the latest available major version, granting us a minor performance boost and improved security. WeвЂ™ve been using phpBB for the forums even before we had our blog, and itвЂ™s been working great. Any help to make this happen is more than welcome! Forum Our plan for the future is to move away from WordPress to take advantage of GitLab Pages to run a static website instead. On the backend side, we cleaned the database up by removing comments (which had been turned off years ago), post revisions, unnecessary users, and much more, reducing the size of our database by 60%.ДЄll those small changes lead to a significant improvement of loading times: from around 9 seconds to 1 second! Speaking of tracking: we also removed Google Analytics, which we werenвЂ™t using anyway. If you have a look at the sidebar, youвЂ™ll notice a handful of badges: GitHub, GitLab, Discord, matrix, Twitter, Reddit вЂ“ all without a single line of JavaScript, as in, no tracking. Moreover, since more and more people are browsing the web via their phones, we are more than happy that vtastek took the time to make the blog responsive, so that it looks great on mobile as well!

Jetpack because our posts are written in Markdown.

Polylang, since WordPress doesnвЂ™t support internationalization by default and some of our blogposts are translated into a couple of languages.

Also, no need to fetch your pitchforks if youвЂ™re using Tor or a VPN: we configured Cloudflare to not annoy you, so itвЂ™s only used as a CDN/cache.

our Cloudflare integration, since our server is not super powerful and weвЂ™ve been slashdotвЂ™ed before.

Ten years using WordPress and still kicking! But it was time to clean up the dust a bit.ДЇirst of all, we removed unnecessary plugins like akismet and its friends to only keep: We took some time this year to overhaul, simplify and awesomify our web presence and infrastructure.