Tim Alby c1c23e4bee record last author id on document flush ... This is a multi-steps process: * get a update's `user_id` from the metadata * store the `user_id` (`lastUpdatedBy`) and current date (`lastUpdatedAt`) for the document in Redis on every updates * fetch `lastUpdatedAt` and `lastUpdatedBy` from Redis on document flush * send the data to web to be persisted in Mongo		2019-05-02 11:10:02 +01:00
..
acceptance/coffee	record last author id on document flush	2019-05-02 11:10:02 +01:00
cluster_failover/coffee	Add scripts for testing cluster failover scenarios	2017-05-04 11:14:17 +01:00
stress/coffee	Improve consistency of stress test script	2016-06-21 14:31:20 +01:00
unit/coffee	record last author id on document flush	2019-05-02 11:10:02 +01:00