It is often the case that when we kick off long-running tasks that are monitored from the UI that it isn't enough for us to say only that we've started and that we are done. In order to make it more clear to users what is going on behind the scenes, we'd like to allow tasks to publish a list of steps and to notify callers (or whoever's listening), of how far along they are in completing those steps.

Yakkety steps should store an error so that we can tell which step errored and what the user error message is.

Typically, cache and backend clients for redis are booooooring. They really only allow use of set and get. But redis is exciting! It has lots of more powerful calls that can be used such as hset, hget, ladd, sadd, etc., that allow you to manipulate more sophisticated data types. It would be ever so much nicer if we could access that functionality by itself instead of getting our hands on the native client, first.

Everyone seems to have a version of an environment enabled config file. Let's see if we can do the same thing here in djenga, cheaply.

would like to have assert_not_equal . . . working on PR

(1) The encryption and decryption primitives are too hard to use. Let's switch to using key derivation, plus any old password for the key and
(2) update to mode GCM instead of mode CBC so that we can do decrypt + verify

Problem?

The current set of currency rounding options are insufficient. Additional options are needed for rounding up based on half amounts or rounding down, instead of always rounding up.