Tuesday, August 21, 2012

Heroku Weirdness

I love Heroku.  I love the ease and simplicity.  But today, as in right now at 4am, I have been dealing with this horrible issue for HOURS.  I was having tons of problems with any heroku db tasks that I was trying to execute.  I couldn't migrate nor could I check the version.  And everytime I ran those commands, the console would hang.  It made no sense!  I tried all sorts of random things that I don't even want to get into.  Finally out of desperation, I upgraded my heroku cli.  And not from the friendly heroku update (which wasn't working for me), but from actually installing it from

FINALLY that worked.  The problem was that the heroku command was out of date and whatever magic incantation it was issuing, was different between my version (2.26.0) and the latest (2.30.3).  ARG!!!  I guess I would have expected a message like, "Your version of the heroku cli is out of date, please update it."

So I'm posting this in hopes that if someone out there encounters this, they'll save hours of banging their head on the desk.

Alright before I go quick review of heroku commands:

Migrate:          heroku run rake db:migrate
Reset:            heroku pg:reset
Check Version:    heroku run rake db:version

Check Status
ps:               heroku ps
logs:             heroku logs
scale (2 web and 1 worker): heroku ps:scale web=2 worker=1

Restart app:      heroku restart
Restart worker 1: heroku restart worker.1

There are a bunch more but those are the ones I use more often so hopefully it'll help you out as a quick reference.

Friday, August 17, 2012

Eclipse Aspectj Classpath

Just ran into this, the aspectj maven dependency was being ignored and not added to the classpath in eclipse after I ran: mvn eclipse:eclipse Silly problem with an easy solution: maven-eclipse-plugin 2.7 none

Tuesday, August 7, 2012


Not sure if I mentioned this post, but I always find myself going back to it to reconfigure Console2.