Posts tagged with "google-compute-engine"
Last time I wrote about my adventures with moving comments engine from Disqus to Remark42. This is a continuation of that story. While I liked pretty much everything about Remark42, one thing that did not work out for me was spam protection. Remark42 does not have, or at least it did not have a proper automated spam protection mechanism in place at the time I tried it out. With the default WordPress comments engine, you could add Akismet for spam protection. I could not figure out any way to install spam filters in Remark42. The only way would be to hold the comments for approval. Then I have to approve each comment manually. This would be too much work for me. Not that I get a lot of comments on the blog, but still, why should a human take care of such things when an automated system could do it for me?...continue reading
After having used Disqus as the comments engine for my Jekyll website for a week or so, I started to dislike it quite a bit due to several reasons. One of which is the requirement of creating an account with Disqus even if the user is logged in via one of the social logins such as Google or Twitter account. The other issue is the privacy aspect with Disqus. Seems like it is tracking too much information about the users. So I decided to use Remark42 instead. The only problem however is that I need to run a server to host it. It defeats the whole purpose of me going absolutely serverless. But I don’t have a choice since some of my readers want comments section....continue reading
If you read my previous post on Jekyll, you already know why I switched from WordPress to Jekyll. In continuation of that post I want to explain how I migrated to Jekyll. For those who are not interested in the software side of things should skip this post. Wordpress offers a lot of features out of the box, like search engine and comments engine. So all I have to do is write posts and users can search and comment on them. This works because Wordpress is dynamic and runs a DB to store data. However since Jekyll is static, one needs to figure out a way to make things work....continue reading
The past few days have been quite busy, so I have not been regular with my posts. One of the reasons was because of the migration of my blog from WordPress to Jekyll. This post is going to be a bit technical, so for those who are not interested in software should probably skip this one. I have been using WordPress to publish my blog. My WordPress has been running on a Google Compute Engine instance since I started the blog. But I have been wanting to move away from WordPress for a long time. So I decided to go with static web pages. Unfortunately the process was not quite easy because WordPress offers so many things out of the box. Doing all that work manually was some work, but it was well worth it....continue reading
A few days ago, I decided to update my Google Compute Engine instance which was running an older Debian version. This was the same instance that is hosting this WordPress blog, so I had to be careful not to break anything lest I lose all the data and/or the service can be down. This post is a recount of my journey through the update process because I found some interesting things about Google Compute Engine (GCE) and how things can break if you are not careful and how things can go very smoothly if you plan properly....continue reading