Fork me on GitHub
#datomic
<
2021-10-07
>
onetom01:10:40

Is there some established or off-the-shelf solution to "rename" a Datomic Cloud DB? I would be fine with downtime and I don't mind losing the :db/txInstant values either, so some kind of dump and restore operation would be perfectly suitable.

Benjamin12:10:13

Hi I'm trying to start a local ddb transactor and connect to it

~/datomic/datomic-pro-1.0.6316 $ ./bin/transactor ../ddb-template-local.properties
Starting datomic:<DB-NAME> ...
System started datomic:<DB-NAME>
(def cfg {:server-type :peer-server
          :access-key "myaccesskey"
          :secret "mysecret"
          :endpoint "localhost:8000"
          :validate-hostnames false})

(require '[datomic.client.api :as d])

(def client (d/client cfg))

(def conn (d/connect client {:db-name  "<DB-NAME>"}))
=> Unrecognized SSL message, plaintext connection?
do you know what I do wrong? How do I configure "<DB-NAME>" ?

favila12:10:08

The client api connects to a peer server not a transactor. The “DBNAME” in your client config is set to whatever you want in the command line args that start the peer server.

favila12:10:13

Your complete system should have at least four processes running if you are using on-prem with the client api: dynamodb local, transactor, peer-server, and the client application

Benjamin12:10:05

ah I see I don't have a peer server yet

favila12:10:52

if you’re using on-prem, you could cut this down to two: transactor with “dev” storage (transactor acts as storage too), and an application using the peer (vs client) api

Benjamin12:10:21

Ah do you mean something like this?: I already played around with that (it worked) now I'd like to make it work on aws

Benjamin12:10:55

now I have this error when I try to connect a peer to my transactor

Benjamin09:10:59

I went on to skip the local setup and made it work on aws now