This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-07-10
Channels
- # announcements (3)
- # beginners (67)
- # calva (4)
- # cider (3)
- # clj-kondo (58)
- # cljs-dev (4)
- # clojure (172)
- # clojure-berlin (4)
- # clojure-chicago (8)
- # clojure-europe (4)
- # clojure-greece (8)
- # clojure-italy (12)
- # clojure-nl (4)
- # clojure-spec (7)
- # clojure-uk (77)
- # clojurescript (13)
- # clojutre (16)
- # core-async (10)
- # cursive (3)
- # datomic (29)
- # figwheel-main (27)
- # fulcro (22)
- # garden (3)
- # jobs (2)
- # jobs-discuss (13)
- # juxt (5)
- # leiningen (14)
- # mount (4)
- # off-topic (28)
- # pathom (6)
- # pedestal (8)
- # portland-or (2)
- # re-frame (20)
- # remote-jobs (6)
- # shadow-cljs (13)
- # sql (74)
- # testing (17)
- # tools-deps (1)
- # vim (1)
- # xtdb (1)
Hi, I'm trying to follow the datomic tutorial and connect to a running datomic server. But the following code gives an exception Execution error (ExceptionInfo) at datomic.client.api.async/ares (async.clj:58). No subject alternative names present
error
(require [datomic.client.api :as dc]))
(def config {:server-type :peer-server
:access-key "myaccesskey"
:secret "mysecret"
:endpoint "127.0.0.1:8998"})
(defn connect! []
(let [client (dc/client config)]
(dc/connect client {:db-name "hello"})))
(connect!)
I'm using the latest version of datomic-pro-starter 0.9.5930
Maybe try localhost
instead of 127.0.0.1
?
I've tried latest versions of AdoptJDK's OpenJDK 11, 12, 8 with no success. Running on MacOS.
=> (pst)
ExceptionInfo No subject alternative names present {:cognitect.anomalies/category :cognitect.anomalies/fault, :cognitect.anomalies/message "No subject alternative names present", :cognitect.http-client/throwable #error {
:cause "No subject alternative names present"
:via
[{:type javax.net.ssl.SSLHandshakeException
:message "No subject alternative names present"
:at [sun.security.ssl.Alert createSSLException "Alert.java" 131]}
{:type java.security.cert.CertificateException
:message "No subject alternative names present"
:at [sun.security.util.HostnameChecker matchIP "HostnameChecker.java" 137]}]
I want to reference an entity with a tempid for :db/id
for different datoms. Is this possible?
if you talk about the same tempid in different datoms within a transaction, it will end up becoming the same entity when the transaction commits
@pvillegas12 [[:db/add TEMPID a v t] [:db/add something-else a TEMPID]]
So you can't upgrade a "solo" running Datomic stack? https://docs.datomic.com/cloud/operation/upgrading.html#first-upgrade > This upgrade process converts your Master Template Stack to the setup described in the Production Setup documentation.
I ask because i'm just currently using my setup to learn and i'm assuming the production setup is more expensive.
both of those would seem to be true, but the docs imply that you can upgrade from solo -> solo
upgrade the CTVersion
the goal here is to get the newer features
I am testing the latest release on a dev cluster before rolling it out to prod in a few days
so does "upgrading" in the docs i link refer to moving from solo->prod, and not changing template versions?
or put another way, if i just wanted the latest features for my solo topology. what would i do 🙂
@U0DJ4T5U1 if it’s your first upgrade, just follow the steps in https://docs.datomic.com/cloud/operation/upgrading.html#first-upgrade Storage template is the same for both Solo and Production as far as i know. Just choose Solo for the Compute template.
But your have to choose a larger instance, I assume overall this is more money per month
@U0DJ4T5U1 I did the "first upgrade ever" (stayed on solo), and my datomic set up currently consists of a t2.small and a t2.nano instance--I think this was the same as before, but I don't remember. What instances do you have right now? In any case, my monthly aws billing estimate is still the same (though I only upgraded ~1 week ago)
@U0DJ4T5U1 Maybe the language is overloaded when discussing "upgrading" (transitioning) from a solo topology to a production topology. If we use the word "upgrading" to mean getting latest features (version increment) it is absolutely possible to "version increment" a running solo system while keeping it a solo topology, i've done it a dozen times.
thanks everyone. i understand now that i can still choose the solot topology and have done so. Currently i'm not seeing the option to reuse existing storage as specified here: https://docs.datomic.com/cloud/operation/upgrading.html#first-upgrade