tatham

Disclaimer: I'm a Principal Consultant with Readify.

I'm not familiar with this particular project, however I'd like to clarify a bit based on our engagement focus. Organisations like SEEK engage us to help improve development team process, with tooling on the side to support it.

While the case study talks about them engaging us to help with source control, it doesn't talk about an inability to get something like Git, Hg or SVN working. Instead, it talks to them getting some external advise about effecting an organisational change in their development teams. We also likely brought experience/scripts to help migrate their history from whichever ageing system they were in.

TL;DR: The SEEK devs wouldn't need us to come and help them just install an SCM and leave.

Suggestions?

Heroku was a lot simpler than us spinning up (or paying for) a VPS. The other technologies were mostly just for fun.

Nice catch. Seems we need to improve our regex. In our view, only three digit codes are valid.

The 300 series is not well supported. Most people don't even know that 307 exists - they always use 302.

You're still getting a 418 response there, just not the right status description.

Varnish is certainly stuffing us up a bit. There's a note about this at the bottom of the page.

If I did this again, I wouldn't deploy it to Heroku for this reason.

Nice! :)

Mostly, we wanted to play with some tech and we came across the domain name httpstat.us which we just thought was cool.

This will get you 80% of the way there, but some status codes require certain response headers too. We return these too.

You're correct - it was all one big experiment so we threw way more technologies at it than we had to.

http://isitbeerti.me was another experiment of ours on the .NET platform