Why? You might ask yourself. Isn’t it just better to upgrade the web application and save yourself the trouble of all the security issues? True, but sometimes it’s just not possible or feasible. The other day I helped a friend of mine migreate from a VPS he got in 2008 to a brand new FreeBSD 11 droplet on DigitalOcean. His customer has still not updated their site, and they were paying the same rate they’ve been paying since 2008. So it was better and cheaper to move them to a new VPS even though we kept the same code. At least the OS and all other components in the stack were updated.
Quick one here, if you run into the following error when trying to download a go package using Babun
go get -u -v github.com/cosiner/argv github.com/cosiner/argv (download) # cd .; git clone https://github.com/cosiner/argv C:\Users\Mohammad Al-Shami\go\src\github.com\cosiner\argv Cloning into 'C:\Users\Mohammad Al-Shami\go\src\github.com\cosiner\argv'... fatal: Invalid path '/cygdrive/c/Users/Mohammad Al-Shami/Desktop/go/C:\Users\Mohammad Al-Shami\go\src\github.com\cosiner\argv': No such file or directory package github.com/cosiner/argv: exit status 128
So I got a call from one of our developers telling me one of our Moodle development sites was not working. This particular Moodle instance was configured to use an Oracle backend since that’s what the customer has. Upon checking I got a “Bad Gateway” error.
I was thinking of a way to make my laptop a bit more secure and started looking into alternative firewalls for Windows. I came across TinyWall which is an alternative front end to the Windows firewall so it’s not as intrusive as the other options. Everything was working well till I tried to pull a git repository from Babun and I got an the following error
So while I was writing my previous post I realized that Google Analytics was being called from the localhost server. I also had lots of grief with Disqus back when I migrated to Hexo; It filled my account with posts related to localhost. I wonder why Disqus built it this way.
I hard-coded the Disqus URL in my theme (Both Hexo and Hugo) but then realized I can’t do the same for Google Analytics. I needed a way to disable it altogether. The fix turned out to be quite simple.