Rob Brackett

> A few fields don't have a description as I wasn't sure what they meant… > > Versionista > - `diffWithPreviousDate` > - `diffWithFirstDate` These two fields are kind of...

Three other minor notes: - `hasContent` indicates whether Versionista stored any content, not whether the version actually had any. One of the drawbacks of Versionista is that it won’t store...

Hmmm, `hash` and `filePath` should not be a single object. Are there metadata files where they are? If so, we should correct those.

We have `source_metadata_versionista` documented in the DB docs; we should probably do the same for `source_metadata_web_monitoring`. Or we should document that info somewhere else. In any case, this still seems...

Note we have no AWS credits at the moment 😬, so we need to evaluate dollars on hand before concluding: > we are more crunched for developer-time than AWS credit...

Also also: I’m not at all hot on managing Postgres ourselves — automatic snapshots and backups and etc etc is worth *so much.* I don’t feel like Elasticache offers nearly...

> A documented and separately automated process (Ansible?) for deploying Redis on EC2 would be satisfactory, I think, for both the queue and the cache. Well, I do think it’s...

Update: credits issues resolved. Here’s my proposal for now: - Postgres Database: stick with RDS - Redis queues for DB workers: set up new Elasticache instance - Redis cache: maintain...

Side note: I need to re-deploy the cache machine in us-west-2. It’s currently in us-east-1 because that's where the API service was when it was Heroku-based. (#119)

#119 (shutting down the old cache and starting a new one in the right data center) is now done. All that’s left here is actually setting up Elasticache correctly.