Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> I set up 3 instances (two production and one staging) and thought I was a boss. [..] Lesson learned: don't use anything but Heroku until you have to.

Did he really need 3 instances? Or even a separate staging environment?



Thanks for the comment! Obviously 3 instances were too much. But the point remains that if you're running a low traffic Rails app it's a lot cheaper (free) to host on Heroku than it is on EC2. And if you're running at the scale that DomainPolish was that makes all the difference in terms of take home profit.


But, OTOH, you learned how to use EC2 while still making a profit. So not entirely bad.


True. Pretty expensive tutorial at $1,000 though ;)


Welll.. :) Actually, low traffic EC2 instances are also free (albeit probably harder to set up): http://aws.amazon.com/free/


free for a year


I was looking at Heroku as well for hosting some MVPs and I was wondering how good they are for hosting Python. Any ideas ? Naively, I'd hope they're as good as hosting Rails.


I wish I could help you but I've only ever used them for Rails. I have used GAE for Python and had a pretty good experience. I think that's also free at the beginning.


I was wondering about GAE as well. After the pricing change, it looked like it got horribly expensive. Any comments on how a side-project would do on the free plan ?


I've been using it for Python with Bottle. Been pretty good so far. Anything specific you were looking for?


Just wandering how far you can go on the free plan with Python vs Rails. Looking for that for side projects.


Web frontend-wise, there isn't much difference, so it depends on your framework. But I can't find a Python equivalent of HireFire or the likes to keep worker dynos count down. I haven't gotten around to write one yet.


A couple of Linode instances would've been way cheaper IMO.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: