This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-05-07
Channels
- # beginners (71)
- # boot (25)
- # cider (204)
- # clara (18)
- # cljs-dev (10)
- # cljsrn (64)
- # clojure (50)
- # clojure-dev (2)
- # clojure-dusseldorf (1)
- # clojure-india (5)
- # clojure-italy (1)
- # clojure-nl (21)
- # clojure-poland (65)
- # clojure-spec (41)
- # clojure-uk (10)
- # clojurescript (4)
- # core-async (5)
- # cursive (2)
- # datomic (17)
- # duct (8)
- # emacs (8)
- # fulcro (1)
- # graphql (21)
- # hoplon (2)
- # javascript (3)
- # lumo (25)
- # mount (5)
- # off-topic (5)
- # onyx (3)
- # portkey (6)
- # re-frame (15)
- # reagent (5)
- # rum (1)
- # shadow-cljs (198)
- # spacemacs (19)
- # specter (2)
how do I refresh only cljs part of a duct project?
Are ragtime migrations supposed to be perfomed when running the uberjar? I see the are run in dev
environment (executing (dev)
& (go)
in the REPL), but not when I create the uberjar and run the standalone version of it.
Migrations are not run automatically (i.e., they do not derive from :duct/daemon
) in “production” (anything outside of the REPL dev workflow)
@dadair I had a suspicion that they didn't, but as it's not documented anywhere I wanted to confirm it. Thanks a lot!
@iarenaza The reasoning behind it is that web servers are frequently load balanced, and migrations can contain instructions that databases don’t like running concurrently.
It needs to be better documented, however.
By default, the uberjar will only run keys that inherit from :duct/daemon
.