4 ms·
PHP is the exception, but most things are as deployable as Rails these days.
by neilmiddleton 14y ago
PHP is the exception, but most things are as deployable as Rails these days.
- WalterGR 14y agomost things are as deployable as Rails these days. I really, really don't want to seem dense. But I don't understand what that means. Let's forget about PHP, and consider Clojure. Reading http://blog.heroku.com/archives/2011/7/5/clojure_on_heroku/ http://blog.heroku.com/archives/2011/7/5/clojure_on_heroku/ I don't see the part that says SysAdmins are no longer needed. But maybe I am dense, and just don't get what Heroku offers...
- neilmiddleton 14y agoThe Heroku offering is about providing a stack that you don't need to know anything about in order to look after a decent application. You deploy with Git, give it the resources it needs and forget about it. You've no need to learn UNIX, or anything about packaging, or security, or networking and so on. You just need to care about your application. Saying this, there's lots of things deployable to Heroku right now, and even more via the Buildpacks system. Yes, at first Heroku was just Ruby, but those days are long gone, most modern platforms that run on UNIX are deployable to Heroku in just a few minutes.
- themgt 14y agoI'm not sure I understand what you mean. The process for deploying a Clojure app to Heroku is the same process as deploying a Ruby, Rails, python, PHP, node.js, scala, etc app. That's the basic win of the unified build/deployment/hosting process How would you get a clojure app deployed on EC2 or Linode without doing a lot more sysadmin work than Heroku?
- WalterGR 14y agoHow would you get a clojure app deployed on EC2 or Linode without doing a lot more sysadmin work than Heroku? Exactly, thanks. I thought Heroku was supposed to get rid of that "problem." Did I read it wrong?