Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on Feb 26, 2015
  1. James Mead
Commits on Feb 24, 2015
  1. James Mead
  2. James Mead
Commits on Feb 23, 2015
  1. Chris Roos

    Remove our office address

    chrisroos authored
    Explain that we're between offices but still available for a cuppa.
  2. James Mead

    Move wiki page about checking annual accounts to wiki.

    floehopper authored
    This is a copy of the content from the original wiki page [1],
    however I've had to tweak the formatting slightly to deal with
    our crazy CSS. In particular our styles don't work well for *nested*
    bullet points.
    
    [1]: https://github.com/freerange/business/wiki/Checking-our-Annual-Accounts
  3. James Mead
  4. James Mead

    Add a package.json c.f. Gemfile for node modules.

    floehopper authored
    This makes the dependency on less.js more explicit.
  5. Chris Roos

    Update our availability

    chrisroos authored
    We're imagining spending the majority of the next two or three weeks searching
    for new office space.
Commits on Feb 19, 2015
  1. James Mead
  2. Chris Roos

    Add links for week 318

    chrisroos authored
  3. James Mead

    Links for week 318.

    floehopper authored
Commits on Feb 17, 2015
  1. Chris Roos
  2. Chris Roos

    Add notes for week 317

    chrisroos authored
Commits on Feb 16, 2015
  1. James Mead

    Fix #29.

    floehopper authored
    The `String#first` method mysteriously disappeared in [1], so we have to use
    the `String#[]` method instead.
    
    [1]: 5e93fcf
  2. James Mead

    Use Airbrake::Rack instead of Rack::MailExceptions.

    floehopper authored
    This commit replaces the `Rack::MailExceptions` middleware with
    `Airbrake::Rack` for the reporting of exceptions.
    
    We're already using Airbrake to report exceptions from our `video` and
    `webhooks` apps to our instance of Errbit running on Heroku. So it makes sense
    to bring this app into line.
    
    Errbit makes it easier to manage exceptions when they occur e.g. commenting on
    them and marking them as resolved. Errbit notifies us by email of any
    exceptions, so none of the original behaviour is lost.
  3. Chris Roos
  4. Chris Roos

    Tidy up Show and Tell 9 notes

    chrisroos authored
    * Add headings
    
    * Tidy up final paragraph about books
  5. James Mead

    Fix typo/semantics.

    floehopper authored
  6. Chris Roos
Commits on Feb 13, 2015
  1. James Mead

    Add notes for week 316.

    floehopper authored
Commits on Feb 4, 2015
  1. James Mead

    Add links for week 316.

    floehopper authored
  2. Chris Roos

    Add notes for week 315

    chrisroos authored
Commits on Jan 30, 2015
  1. James Mead

    Added notes for week 314.

    floehopper authored
Commits on Jan 25, 2015
  1. James Mead
Commits on Jan 21, 2015
  1. James Mead

    Added notes for week 313.

    floehopper authored
Commits on Jan 12, 2015
  1. James Mead

    Added links for week 313.

    floehopper authored
  2. James Mead
  3. James Mead

    Added notes for week 312.

    floehopper authored
Commits on Jan 4, 2015
  1. James Mead
  2. James Mead

    Handle invalid parameter errors.

    floehopper authored
    We were seeing exceptions like the one below in production which were resulting
    in 500 Internal Server Error responses which the `Rack::MailExceptions`
    correctly emails us about:
    
        A ArgumentError occured: invalid %-encoding (<%MYTEST)
    
        ===================================================================
        Request Body:
        ===================================================================
    
          <%MYTEST=REquEst("autoshell"):EvaL(MYTEST)%>
    
    I was able to reproduce the problem using a command like this on my local
    development environment:
    
        curl -v -XPUT --data "<%MYTEST=REquEst("autoshell"):EvaL(MYTEST)%>" "http://localhost:9292/"
    
    Upgrading Rack to v1.6.0 means that this type of request now raises a more
    specific exception: `Rack::Utils::InvalidParameterError`. Rails handles [1]
    this more specific exception and responds with a "400 Bad Request" response.
    
    I've attempted to reproduce similar behaviour using some custom Rack
    middleware loosely based on the `rack-robustness` middleware gem [2]. I've
    inserted this middleware just in front of the `Rack::MailExceptions`
    middleware so that the app responds with a "400 Bad Request" response instead
    of emailing us with about a "500 Internal Server Error".
    
    @chrisroos: I'm not sure this is the best solution and it does feel as if we're
    reinventing the wheel a bit. It makes me wonder again whether we'd be better
    off with a Rails app! But this solution does mean that we won't continually be
    bothered with emails about such exception emails.
    
    [1]: rails/rails@75eaefc
    [2]: https://github.com/blambeau/rack-robustness
Commits on Dec 22, 2014
  1. James Mead

    Publish notes for week 309.

    floehopper authored
  2. James Mead
Commits on Dec 17, 2014
  1. James Mead
  2. James Mead
  3. James Mead
Something went wrong with that request. Please try again.