This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-10-07
Channels
- # babashka (30)
- # beginners (49)
- # calva (22)
- # cider (9)
- # clara (2)
- # clj-commons (1)
- # cljdoc (1)
- # clojars (7)
- # clojure (153)
- # clojure-australia (2)
- # clojure-europe (45)
- # clojure-italy (3)
- # clojure-losangeles (1)
- # clojure-nl (17)
- # clojure-portugal (3)
- # clojure-uk (6)
- # clojurescript (21)
- # conjure (4)
- # copenhagen-clojurians (5)
- # cryogen (3)
- # cursive (19)
- # datahike (14)
- # datascript (4)
- # datomic (9)
- # events (5)
- # fulcro (23)
- # graalvm (1)
- # gratitude (4)
- # helix (2)
- # holy-lambda (5)
- # improve-getting-started (2)
- # jobs (10)
- # kaocha (1)
- # leiningen (1)
- # liquid (8)
- # membrane (81)
- # off-topic (88)
- # polylith (29)
- # quil (1)
- # reitit (2)
- # remote-jobs (8)
- # reveal (8)
- # sci (1)
- # shadow-cljs (14)
- # specter (4)
- # sql (5)
- # tools-build (11)
- # tools-deps (5)
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.
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>" ?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.
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
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