This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-01-20
Channels
- # announcements (9)
- # aws-lambda (5)
- # babashka (26)
- # beginners (200)
- # bristol-clojurians (2)
- # calva (74)
- # cider (22)
- # clj-kondo (8)
- # cljsrn (1)
- # clojure (124)
- # clojure-australia (2)
- # clojure-europe (79)
- # clojure-spec (1)
- # clojure-uk (37)
- # clojurescript (87)
- # cloverage (1)
- # code-reviews (10)
- # conjure (41)
- # cursive (5)
- # datahike (2)
- # datascript (3)
- # datomic (11)
- # docker (4)
- # duct (1)
- # emacs (10)
- # events (1)
- # fulcro (3)
- # graalvm (1)
- # honeysql (3)
- # jobs (1)
- # malli (12)
- # meander (51)
- # off-topic (83)
- # pathom (28)
- # quil (3)
- # reagent (19)
- # reitit (3)
- # releases (1)
- # shadow-cljs (49)
- # spacemacs (2)
- # sql (5)
- # startup-in-a-month (1)
- # testing (1)
- # xtdb (8)
in the fulcro template repo it says it'll demo running a process for production at a later time. does fulcro do anything different for making a release build? if not, would questions about release builds belong in the shadow-cljs channel maybe?
So, the shadow release builds are pretty trivial, so there’s not much to say. The server-side stuff centers around things like the config file support, which can be included in the JAR or just put on filesystem (startup supports setting -Dconfig=/abs/path/config.edn
so you can deploy to a server that has a local config, for example. The other thing I mean by “production” is a bit of a misnomer. What I mean is “commercial” operation, where you need CI, deployment strategy, etc. The template has setup for CI practically in place, workspaces for development, etc. So, instead of it just being a bare-bones “make something appear” it has a lot of setup that usually takes days of dev.