Dan Allan
Dan Allan
Let's leave it open to track our progress. Would you enumerate the blank entries here? Then we can ask for external help.
Somewhat tangentially, we should also factor lifecycle management of the S3 buckets into our decisions about operating costs.
> Note we have no AWS credits at the moment Goes to show that I only partially keep up with Slack, and apparently with the passage of time! > automatic...
Summary of conversation on call: Given current cost constraints, stick with manually-managed Redis but document the process. Maybe someday move that process into Ansible. Stick with RDS.
Sounds useful to me, but likely a post-v0.1 concern.
attn @Mr0grog @lightandluck @ambergman
Yes, prior to any interaction with an analyst. The Versionista hash function is already an example of a Cluster, which makes me think we can and should build the idea...
> I’m also a little worried we are trying to push more concepts into our storage/database than belong. That point is well-taken. It's a balance between locking ourselves into assumptions...
@Mr0grog More thoughts on the "Changes" table: We can maintain all the information I am advocating for without actually having a Changes table. Would it be better to make Diffs...
Sure we'll continue conversation there.