This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-07-31
Channels
- # beginners (9)
- # boot (38)
- # cider (7)
- # cljs-dev (181)
- # cljsrn (49)
- # clojure (136)
- # clojure-italy (44)
- # clojure-losangeles (1)
- # clojure-news (1)
- # clojure-russia (3)
- # clojure-sanfrancisco (1)
- # clojure-serbia (2)
- # clojure-spec (28)
- # clojure-uk (41)
- # clojure-ukraine (1)
- # clojurescript (103)
- # core-async (6)
- # core-logic (46)
- # cursive (5)
- # data-science (8)
- # datascript (6)
- # datomic (5)
- # emacs (35)
- # events (3)
- # jobs (2)
- # jobs-rus (2)
- # juxt (6)
- # lumo (7)
- # off-topic (101)
- # om (6)
- # onyx (6)
- # parinfer (38)
- # pedestal (5)
- # perun (1)
- # planck (4)
- # protorepl (4)
- # re-frame (62)
- # reagent (20)
- # remote-jobs (1)
- # ring-swagger (1)
- # spacemacs (16)
- # unrepl (43)
- # vim (13)
@souenzzo oh, too long stack trace, there is was… and works with the latest core.async, thanks!
So, the Pedestal/AWS Lambda example ...how is one meant to run that with Datomic Pro, exactly? I have tried everything I can think of to make CodeStar aware of the Datomic repo and my login/pw for it and so far all my builds have failed at the step where the datomic-pro-<ver>
jar is sought.
Is it kosher to push that up in the repo and just copy it into /root/.m2/repository
in an install
step? Is there a working example of a combination of settings.xml
and some project file (Boot or Lein) that is known to work?
I really want to have a production-ready Lambda service and this last step is killing me 😄