ddollar's comments

ddollar | 11 years ago | on: Tug: Use Docker for development

Hello everyone! We created tug as a tool to help people dockerize applications and run them during development.

Please keep in mind that this is a very alpha project still under heavy development. If you try it I'd love to hear how it goes and whether or not it's useful for you (you can reach me at [email protected] or find me on Freenode as ddollar).

ddollar | 12 years ago | on: Hk, The new Heroku Client written in Go

There are two reasons I rewrote Foreman in Go. You hit one of them square on the head. A single binary with no dependencies that can be cross-compiled on a Heroku dyno makes things much simpler.

Foreman was originally written in Ruby which ideally means it runs on any machine with a Ruby interpreter. When you get down to it, though, the differences in fork/exec between Ruby 1.8, 1.9, JRuby, Rubinius, etc make this a nightmare scenario of a different sort.

If you go to https://gobuild.herokuapp.com/ddollar/forego/master/darwin/a... you get a working program as a single binary in one step. Using bsdiff I can even ship binary diffs for fast upgrades (this is how `foreman update` works in the new version)

Oh and as a side effect the new Foreman is quite a lot faster to start up (Rubygems initialization is sloooooow)

ddollar | 14 years ago | on: The Heroku Toolbelt

Thanks for the feedback!

We made the script a link so you could check out what's going on before running it.

The heroku-toolbelt .deb actually depends on system git-core and ruby1.9.1 so we shouldn't be trampling anything.

ddollar | 14 years ago | on: Ask HN: Who is Hiring? (November 2011)

San Francisco, CA - Heroku

We're looking for an active member of the Node.js community to come own Node.js at Heroku. This position involves both contributing to the Node.js open-source community and working to reduce friction for Node.js users on Heroku.

If you're excited about the promise Node.js and the future of app deployment, come help us to shape it.

Full job description: http://heroku.theresumator.com/apply/gtoHxr/Build-Pack-Maint...

Email: [email protected] (please include a link to your Github account)

ddollar | 15 years ago | on: Run Your Own Piece of Heroku with Foreman

If you try the latest foreman it should be a lot better about killing things off now. See other comments in this thread about the SIGTERM-pause-SIGKILL approach.

ddollar | 15 years ago | on: Run Your Own Piece of Heroku with Foreman

You could also check out something like http://upstart.ubuntu.com/wiki/Stanzas#limit for use in your upstart scripts.

ddollar | 15 years ago | on: Run Your Own Piece of Heroku with Foreman

Yes. If you kill foreman with Ctrl-C (or killing its pid externally) it will send SIGTERM to all of the child processes, followed 3 seconds later by SIGKILL to any that haven't terminated yet.