This site used to be in a Hostgator shared host which I had bought long before I understood how servers work. I didn’t bother changing it as it just worked and this was not the only site/app that was hosted there. (If I was to move, I wanted to move everything)
Lack of WordPress know-how was another problem. I have/had multiple WP sites including this one, and moving meant creating a multisite, configuring it to match the original URLs, while supporting other non-WP stuff as well. Also I didn’t want to migrate the blogs as static sites for different reasons.
Finally I’ve moved most of the stuff to a separate VPS in Vultr (thx to @gaveen for referring). The major motivation was TLS support. You had to pay additionally for TLS in Hostgator, which didn’t make sense as we have Let’s Encrypt.
The multisite is mostly working now, but I need to get images working properly (uploads
directories not properly configured for sub-sites), fix old thameera.com/files/...
links, set up rss2email and also see what else is broken đ.
Ghost, the much awaited blogging platform, is finally here. You need to sign up to download.
It only took me 5 minutes to download and have Ghost up and running. You download the file, run an npm install
(yes, it’s built on node.js), run sudo npm start
and bang! Ghost is ready. The interface is minimal and clean, you can write with markdown, and there’s a marketplace for themes. And there are guides on deploying Ghost on various platforms like Amazon EC2, Digital Ocean and Azure.
They are planning to run a hosted Ghost platform as well (like they do at wordpress.com for WordPress), and they’ll be rolling it out in the coming weeks.
Note that Ghost needs a node.js server running so you can’t host it like a static site in places like Dropbox or with most shared hosting providers. But you can use an Amazon Micro EC2 instance for free for one year. The database used is SQLite, so it won’t be practical to run this on Heroku.
From the wordpress.com Stats support page:
UPDATE: In September 2013 Google started to rapidly expand the number of searches that it encrypts, which results in a higher proportion of âUnknown search termsâ in your stats. According to some sources, this expansion will eventually result in encryption of all Google searches. This is being done for privacy reasons by Google when someone searches at Google.com, before a visitor arrives at your WordPress.com site. Therefore we donât have any way to unhide the search terms. We recognize this means a loss of stats information for you and we will look for other ways to show you how users arrived at your site.
Any blog owner would love to see the search terms leading to his blog, but I damn respect Google’s decision. Been using Google’s encrypted version for some time, but 99% of the people don’t know of its existence. And it seems now you don’t need to anymore.