Fork me on GitHub
#datomic
<
2017-04-23
>
jimmy03:04:09

hi guys, is using #db/fn with conformity the correct way to run data migration in datomic ?

val_waeselynck08:04:57

@nxqd I cannot speak for "the correct way", but yes, it's a pretty effective one. There's nothing magical to it, this blog post may help you understand how it all works: http://vvvvalvalval.github.io/posts/2016-07-24-datomic-web-app-a-practical-guide.html#data_migrations. Shameless plug: equivalent functionality is also provided in Datofu, with some built-in generic db functions to help you write migrations, see here (https://github.com/vvvvalvalval/datofu#managing-data-schema-evolutions).

deg12:04:45

I want to move my toy Vase app to a permanent DB, rather than the default in-memory. I've installed the Datomic Starter version, but am not sure what to do next. I've found a variety of docs that each seem to have 80% of what I need, but there are enough redundancies and contradictions that I don't see a clear path forward. I'm initially interested in doing a dev configuration, but also want to be able to configure for production pretty soon.

marshall14:04:01

After that, prod storage setup is covered here http://docs.datomic.com/storage.html

deg14:04:26

Thanks! I'll go through that carefully in a bit. I see one question already: that doc describes specifying the access key and secret as parameters to client/connect. But, Vase uses a datomic-Url instead. What is the syntax for passing in the parameters there? I found major hints in http://docs.datomic.com/javadoc/datomic/Peer.html#connect-java.lang.Object-, but none that seemed to match this case exactly. 😞

marshall14:04:49

Secret and access key are used by peer server and client, not by peers

marshall14:04:15

Peer access is secured via access to storage

marshall14:04:58

I.e. sql user and pw or IAM role access control to ddb

deg15:04:06

@marshall Ok, thanks. I'll work through the docs and will moan back if I hit any snags. Probably won't get to this until tomorrow.