This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-08-19
Channels
- # beginners (59)
- # calva (20)
- # cider (25)
- # clj-kondo (12)
- # cljdoc (3)
- # cljsrn (15)
- # clojure (104)
- # clojure-europe (4)
- # clojure-italy (10)
- # clojure-nl (3)
- # clojure-spec (14)
- # clojure-uk (13)
- # clojurescript (33)
- # code-reviews (26)
- # core-async (1)
- # cursive (5)
- # data-science (3)
- # datomic (8)
- # emacs (3)
- # fulcro (5)
- # graphql (3)
- # hoplon (1)
- # jobs-discuss (4)
- # kaocha (14)
- # nyc (1)
- # off-topic (33)
- # pathom (4)
- # pedestal (2)
- # quil (1)
- # re-frame (5)
- # reagent (10)
- # reitit (6)
- # rewrite-clj (3)
- # shadow-cljs (173)
- # specter (7)
- # sql (4)
- # vim (58)
- # yada (3)
@chrisjswanson I recently succeeded at this but ran into several small issues with it. Granted, i'm trying to deploy via ions and that was where the issues were.
@joe.lane if you'd care to share details, I'm quite curious. Did you end up having to write a custom intercepter to add the datomic connection to the chain? Or modify the vase code to let it handle datomic cloud connection Uris?
Thanks man, good to have that insight, I'd appreciate it
Yes but probably not to deploy vase, just custom query functions. Vase would likely go on k8s or lambda directly. But I'm still exploring, so I'm also really curious how it ended up working for you on ions
If I could just deploy vase straight as an ion that would be pretty nice