This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-10-25
Channels
- # announcements (1)
- # architecture (3)
- # beginners (31)
- # calva (61)
- # cider (1)
- # clojure (43)
- # clojure-dev (17)
- # clojure-europe (85)
- # clojure-uk (8)
- # clojurescript (31)
- # cryogen (2)
- # cursive (7)
- # data-science (12)
- # datalog (1)
- # datomic (4)
- # defnpodcast (1)
- # figwheel-main (11)
- # fulcro (32)
- # hoplon (1)
- # leiningen (1)
- # malli (47)
- # pedestal (1)
- # rdf (2)
- # re-frame (11)
- # reagent (4)
- # reitit (7)
- # shadow-cljs (22)
- # vrac (8)
- # xtdb (2)
Hi all, I am building an app that serves a reagent-based client, the app must run as a docker container even during development of the client so I am trying to enable a figwheel workflow while the client is served from my docker container but so far I haven’t been able to set this upp correctly, any idea on how to accomplish this?
@amorokh what have you tried, what didn't work? This should just work pretty much :)
@dominicm sorry, I really didn’t state my problem correctly.. besides running in a docker container I also need to package the entire thing in an uberjar so what I am trying to do is to “compile” the client with figwheel to produce output that can be packaged into the jar-file and then served (the reason for the uberjar is a restricted runtime env where I am not able to connect to internet or to write to the filesystem), so I guess that my real problem is: how do I produce a figwheel-enabled client that can be packaged into a jar-file? please let me know if I’m thinking about this the wrong way..