The process isolation is very useful but they've got a point, why we should run million lines of code until we get to the point to run a single web server? Have we ever asked our self why the operating system which its only responsibility is running a web-server should take 300 seconds to boot?
Unfortunately there isn't much doc, but it's not that hard to set up. Take a look at run.sh file and config directory. Andrew Gerrand has a init script[1] in his fork for it which might be useful.
Just an introduction: Currently I'm using runsit as an alternative for supervisord and I'm happy with it so far. Stdout and stderror of the processes can be queried with a very simple HTTP interface.
Runsit watches a config directory for any changes and applies them immediately. Config files are in json format.
Do you mind if I ask couple of technical questions?
- How did you cope with the traffic from HN?
- The image resize service you implemented (photo.pixomize.com) is so simple and clean I want to know how did you implemented it? is it implemented from scratch?
What I like about photo.pixomize.com is the simplicity in the URL and how you can simply create thumbnail and download it and it's pretty fast.
There are lot's of image resize services out there which do the exact same thing as a SaaS.
https://ocw.mit.edu/resources/res-6-011-the-art-of-insight-i...