This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-02-13
Channels
- # announcements (1)
- # babashka (28)
- # beginners (72)
- # biff (6)
- # calva (15)
- # clerk (14)
- # clj-otel (4)
- # cljdoc (4)
- # clojure (121)
- # clojure-europe (61)
- # clojure-nl (2)
- # clojure-norway (63)
- # clojure-uk (5)
- # datahike (35)
- # datalevin (37)
- # datomic (7)
- # emacs (2)
- # fulcro (6)
- # gratitude (1)
- # honeysql (2)
- # hyperfiddle (38)
- # malli (9)
- # matrix (24)
- # meander (4)
- # off-topic (10)
- # polylith (8)
- # reagent (2)
- # releases (1)
- # shadow-cljs (8)
- # spacemacs (4)
- # specter (1)
- # squint (5)
- # tools-deps (3)
In an undistributed datomic install using sql storage, is it possible to start the transactor from a local jar file declared in deps.edn? What I’m thinking is to copy datomic-transactor-pro-1.0.7075.jar to a lib directory under the project along with the needed database driver, declare the dependency like this in deps.edn
com.datomic/transactor {:local/root "lib/datomic-transactor-pro-1.0.7075.jar"
and then start it using the proper incantation, which I have yet to figure out.
Would this be a viable way to set up a system, or am I heading in a wrong direction?
the transactor also needs jars in the lib
directory on its classpath. You can do this, but your path would be reimplementing what the bin/transactor
shell script does as a deps-edn alias or something like that
For a light duty application, would this approach avoid starting the transactor in a separate java process? I’m not clear how the transactor properties would be passed into the transactor like this.