Rabid is now Ackama

In September 2018, on the company’s 8th birthday, Rabid became Ackama - this was to reflect that fact that we work on large digital ecosystems, and given that nature is the largest ecosystem in the world we wanted a name that came from nature. Ackama, or Makamaka, is a small bushy tree with white flowers and red seeds. It’s found on the coast from Whangarei north.

Go to the Ackama blog

Brenda Wallace

What we did Last Summer -- A Fishy Tale

Last summer was glorious. Sunny and warm like a summer should be. And I got to do some Android programming.

The project was just the sort that Rabid seeks out: good for the world. A smartphone app that measures and contributes to sustainable fishing. The good folk at Terramoana had created an iPhone application for recreational fishers to record their catch. The glaring missing piece was an Android app.


Jevon Wright

Open Source is Powerful: A Walkthrough Extending Loomio with a Custom OAuth2 Provider

One of the great superpowers of using open source in your company is that, if you’re using software in your business, you have the power to change it yourself, without having to ask anyone for permission. Another is that, if your contribution is useful, you can contribute your changes back to the community - making the software more useful for everyone.

In this post, I’ll briefly be going over the process of extending the popular open source project Loomio to integrate with an existing Drupal solution.

Collabforge were keen to use Loomio but having a single login was a key requirement to get started. They asked Rabid to assist with a feature on the Loomio.


Rose Lu

Rails Girls is awesome and you should get involved in one

<3 <3 <3

Rails Girls is a global community that aims to up skill women in technology through free weekend introductory workshops in Ruby on Rails programming. All the events are volunteer run, and I had the honour of helping organise the third Rails Girls event in Wellington. The Rails Girls website has a page of guides that provide tasters for implementing basic website functionality with Rails, such as adding authentication and uploading images, and also has a guide to help you run a workshop.


Josh McArthur

Managing multiple Chef repositories

Knifing the Chef

A sidenote: I’ve used the terms ‘Chef’ and ‘Knife’ here fairly interchangably here, because on a workstation they kind of are. Chef is the actual framework where you store your configurations, data, etc., and Knife is the tool you use to actually interact with Chef. If you’re a Berkshelf user, you can add berks to the list of interchangable terms - Berkshelf will go ahead and use the same configuration as Knife will when you run it.

If you’re a typical user of Chef, you’re probably going one of two ways: you use chef-solo to manage all of your server setup needs, or you connect to a single Chef server and use the knife utility to interact with nodes, users, data bags and all the goodness that you can access going this route. This blog post deals with the third scenario - you connect to multiple Chef servers from your workstation, and need these to play nicely with one another. I use a multiple Chef servers regularly, both as part of my professional work at RabidTech, and with my own side projects.


Eoin Kelly

The Ember runloop

A deep dive into the motivations and benefits of the Ember runloop


This blog post is a snapsnot of the Ember Run-loop Handbook on Github. Ember is an evolving framework so the occasional care and feeding required to keep this document current will happen there.


You can get started with Ember application development without understanding the runloop. However at some point you will want to dig in and understand it properly so you can use it skillfully. It is my sincere hope that this handbook can be your guide.

We are about to take a deep dive into the Ember.js runloop. Together we will answer these questions:

  1. Why does Ember have this runloop thing?
  2. What is the runloop?
  3. How can we use it skillfully?