It’s about half an year I want to move my blog away from Heroku. It’s the best PaaS I ever used but the free plan has a huge limit: the dynos idle. In a previous post i talked about how to use Heroku to build a reverse proxy in front of AppFog to avoid theirs custom domain limit but the idle problem is still there. My blog has less than 100 visits per day and almost every visitor has to wait 5-10 seconds to view home page because dynos are always idle.
Today I decided to move to another platform suggested by my friend @dani_viga: OpenShift. It’s a PaaS similar to Heroku which use Git to control revision and has a similar scaling system. And the free plan hasn’t the idle problem and it’s 10 times faster!
I created a new application using the following cartridge: PHP 5.3, MySQL 5.1 (I’d like to use MariaDB but cartridge is still in development and I couldn’t install it) and phpMyAdmin 3.4. They require a Git repo to setup application and provide a WordPress template to start. I used it as template moving code of my blog into
The hard part was to migrate my PostgreSQL database into the new MySQL. To start I removed PG4WP plugin following installation instruction in reverse order.
Then I exported my PostgreSQL database using
heroku db:pull command. It’s based on taps and is really useful. I had some problems with my local installation of MySQL because taps has no options about packet size and character set so you must set them as default. I added a few line to
# enlarged, before was 1M
max_allowed_packet = 10M
# default to utf-8
At the end of the pull my local database contains a exact copy of the Heroku one and I can dump to a SQL file and import into the new MySQL cartridge using phpMyAdmin.
The only problem I had was about SSL certificate. The free plan doesn’t offer SSL certificate for custom domain so I have to remove the use of HTTPS for the login. You can do in the
Now my blog runs on OpenShift and by now seems incredibly faster 😀
I talked about AppFog in a previous post listing a number of advantages compared to Heroku. At the end of March 2013 AppFog removed support for custom domains on the free plan. Supported domains are limited to
*.af.cm. This is a huge problem if you are using AppFog to host small websites who rely on the free plan. People aren’t happy.
Their solution is to use the “small” plan for 20$/month!! Many housing provider offer a SSD VPS for 20$/month. 240$/year for a little website is too much. I planned to host a small blog on AppFog and when I faced the problem I was very sad.
After some hours spent on Google I found this: https://github.com/yukinoraru/heroku-http-reverse-proxy. Is a scaffold to use Rack Reverse Proxy on Heroku.
You can use an Heroku app as entry point and route all requests to AppFog application. Performances are not so bad as you can think and everything seems works fine.
A few months ago I migrated my personal website (a single page with a bunch of links served by Sinatra) from Heroku to AppFog. I did it because Heroku service has one big limitation: you can’t point a root domain to a Heroku app. Actually there are some workarounds to do it but Heroku discourage them.
AppFog is quite different from Heroku. It allows you to point your root domain to their app (see blog post and docs about that). It doesn’t use GIT for deploy, it uses a command line tool called
af who transfers your code from e to the cloud and perform management operations (actually really similar to Heroku toolbelt).
Setup is done using one of the available Jumpstart, a ready-to-go scaffold for your needs. There are jumpstarts for Rails, Sinatra, Django, WordPress and more. In addition you can choose several add-ons (many of those are also available on Heroku). The free plan offers you 2GB of memory with no limits. It’s enough for personal use.
Another advantage is the lack of idle. Heroku Dynos goes idle if you app isn’t accessed for a while. My site has 5-6 accesses per day so it’s idle for each request… AppFog seems not affected by this problem, probably works in a different way.
If you website is small and has low traffic my advise is to use AppFog.