Skip to content

Response v0.1.1 🎉

Compare
Choose a tag to compare
@milesbxf milesbxf released this 15 Aug 13:07
adf193e

We've been working on a ton of improvements and new features for Response. Some of the highlights:

  • We restructured Response to work as a standalone Django app you can import into your own Django projects
  • Response is now published on PyPI
  • We now have tests running on Travis CI (#59)
  • We've done some internal refactoring - in particular, we've improved the way we handle errors from the Slack API, making debugging much easier (#83)
  • We've started working on improving the REST API (#95)

This is quite a big change (for the better) in how Response can be integrated and deployed. Previously, Response was a standalone Django project in itself. This meant that users (including Monzo) had to keep a private fork up-to-date with upstream, pulling in changes and resolving merge conflicts 😞

Unfortunately we had to temporarily remove a few features, including:

  • Escalation to Pagerduty
  • Updating the statuspage
  • Custom workflows

After consideration, we think we implemented these in the wrong way in the earlier editions - they were very hardcoded in and difficult to customise. Here's an issue tracking adding these back in: #125

This change vastly improves the workflow. You can now set up your own Django project (even using the tutorial), install Response from PyPI, and import it as a Django app. You'll then be able to customize Django to your needs (e.g. adding SSO/Oauth). Full instructions are in the README, and there's an example demo project which shows how to use Response.

Unfortunately

We'll be continuing to push out patch releases regularly - it's likely there will be breaking changes while we get settled on a stable API, but we'll do our best to keep you informed when these happen.

Above all, thanks to all our early users for their patience and feedback - please keep raising issues and PRs. We're really excited about where we can take this tool ❤️