21–30 of 39 posts
For instance, if I have two runs of a test, that produce different outputs, can I merge the data back together at the end?
If not, then this is only capturing one aspect of git -- the archiving of snapshots of the state of the data.
If this is like git, does that mean that you can merge two different branches of data? For instance, if I have two runs of a test, that produce different outputs, can I merge the data back together at the end? If not, then this is only capturing one aspect of git -- the archiving of snapshots of the state of the data.
We are exploring it. We have some thoughts on higher level understanding of data that might make it possible.
But definitely starting with the basics, as you said.
Earlier quoted context omitted.
I have seen a growth of such "vcs-like" databases, but I think the preponderance remains SQL stores like MySQL/MSSQL/Postegres or NoSQL like Mongo/Cassandra/Redis/Couch/etc. For those - or anything that has its own model of storage or processing and, in the end, is backed by filesystem-type storage, dotmesh provides a really nice solution. I haven't used Relaxo itself, but personally, I like the fact that independent…
Relaxo actually grew out of Couch DB. Relaxo used to be a couch query server ( https://github.com/ioquatix/relaxo-query-server - not so useful any more) and ruby front end ( https://github.com/ioquatix/relaxo-model - still useful). But I got frustrated with the direction of couchdb 2.x so I rewrote it to do everything in-process and use git as the document store. It organically grew from that. Unless you are operatin…
I was a happy couch 1.x user, but moved away with 2.0. Nothing specific about it, just needs and timing.
Learn about architecture, use cases (tutorials) & lots more: https://docs.dotmesh.com
"$ dm cluster init dm: command not found"
1. The first thing I thought when I saw this is "How is this secure?". You're wanting to store the most sensitive information a business has - credentials + production DB. I took a look around the site + Google and couldn't find anything about security. Client side encryption of data seems like it would be good to make people comfortable with storing their data at dothub. I'm not sure if there is any use case for dothub having unencrypted data (at least not yet)?
2. "Application states" is quite a vague term, when I saw that I thought it was referring to capturing the state of a running process. "A git-like CLI for application states" is not a very compelling pitch. As others have noted, for all but the most masochistic of users, "a git-like CLI" is a negative point.
The benefit you're offering is "Snapshot production data to be able to replay in development" and "Snapshot failed CI builds to debug later". I'd recommend putting those up-front and in bold. A more compelling tagline (to me) is "Dotmesh - version control and snapshots for your production data".
This looks really cool! A few thoughts: 1. The first thing I thought when I saw this is "How is this secure?". You're wanting to store the most sensitive information a business has - credentials + production DB. I took a look around the site + Google and couldn't find anything about security. Client side encryption of data seems like it would be good to make people comfortable with storing their data at dothub. I'm n…
1. We mention encryption in the docs FAQ https://docs.dotmesh.com/faq/#what-do-you-encrypt -- where did you look for it? Maybe we can make it easier to find. Noted about this being a priority.
2. Thanks for proposing the updated tagline! I'll run it past the team ;-) we'll certainly develop more messaging and use cases around production data as we develop the project beyond 0.1 :-)
This sounds really cool way to manage the lifecycle of software. Will try it out. Though my first experience after trying the live hosted tutorial at https://dotmesh.com/try-dotmesh/ "$ dm cluster init dm: command not found"
Awesome. I literally started writing a small tool for managing state yesterday, because we really do need smarter ways to move application datasets around.