3 ms·
In my experience Dotcloud has the advantage of giving you more control over your instances and the ability to SSH into them. But I had issues with the reliabili
by acjohnson55 14y ago
In my experience Dotcloud has the advantage of giving you more control over your instances and the ability to SSH into them. But I had issues with the reliability of deployment there. I used to love the sandbox, but I dropped Dotcloud as a provider after that was removed without a drop-in replacement. However, I still use them to serve Redis, and so far, it's way cheaper than using a dedicated Redis service.
I looked into AppFog, but it was not nearly customizable for my fairly intense Django app. I found too much of the configuration to be baked in.
On Heroku, I really like the ease of connecting third party services, and the fact that many of those services have free tiers. I love their New Relic pricing as well. I like that Foreman/Honcho make for a pretty awesome staging environment. What I don't like is the inability to directly connect to dynos.
So far, of the products I've tried, Heroku seems the closest to being fully baked, but it's still a ways away from hitting it out of the park. I'm really glad this question was brought up, even if it's quite frequently asked. There are so many players and the scene is so rapidly changing that information is constantly going out of date. It seems to me that what's really needed is some sort of ongoing comparison tool/site to track the whole PaaS scene.
- pearkes 14y ago> giving you more control over your instances and the ability to SSH into them. FWIW you can do: heroku run bash Which let's you mess around on a new dyno (not an existing one).
- edanm 14y agoDidn't know about this. What's the difference between a new dyno and an existing one? Why would they act differently?
- ncrit 14y agoThey don't act differently, its just a dyno separate from the web and other processes.
- vishal0123 14y agoThe changes you made by running 'heroku run bash' is temporary and can be reverted any time.
- acjohnson55 14y agoThat's good for things that change shared state, but you can't do anything that would alter a running dyno or interrogate its state, unless you built your own hooks or something. But building something like that would kind of obviate the perks of a NoOps system.
- fabiokung 14y ago`heroku run bash` is still the best option, but I've always wanted to ssh into heroku dynos myself, so I did this: https://github.com/fabiokung/heroku-ssh https://github.com/fabiokung/heroku-ssh
- bluedino 14y ago> giving you more control over your instances and the ability to SSH into them. I thought the point of Heroku was not having to SSH into your servers?
- acjohnson55 14y agoSure, and maybe one day they can make that need obsolete. I just don't think that day has arrived yet.