This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-08-17
Channels
- # announcements (8)
- # atom-editor (8)
- # aws (1)
- # babashka (96)
- # beginners (128)
- # calva (7)
- # cider (12)
- # cljsrn (1)
- # clojure (75)
- # clojure-europe (28)
- # clojure-hamburg (2)
- # clojure-italy (7)
- # clojure-nl (7)
- # clojure-norway (3)
- # clojure-uk (13)
- # clojurescript (26)
- # conjure (2)
- # cursive (18)
- # data-science (7)
- # datalog (21)
- # datomic (9)
- # duct (15)
- # expound (29)
- # figwheel-main (14)
- # fulcro (59)
- # helix (4)
- # jobs (2)
- # kaocha (19)
- # leiningen (15)
- # luminus (4)
- # malli (57)
- # meander (2)
- # off-topic (2)
- # pathom (12)
- # pedestal (8)
- # re-frame (53)
- # reitit (9)
- # remote-jobs (1)
- # shadow-cljs (64)
- # spacemacs (1)
- # specter (2)
- # tools-deps (12)
- # tree-sitter (2)
- # vim (11)
- # xtdb (17)
[datomic cloud] Trying to update my development solo stack to the latest version. Following the instructions from the documentation (as I understand them), I click “update” on the nested CF stack for “compute” … however, I am presented with a warning: > It is recommended to update through the root stack > Updating a nested stack may result in an unstable state where the nested stack is out-of-sync with its root stack. Is this something I should worry about, it’s not mentioned in the documentation (I’m I updating the wrong stack?)
Don't know the answer to your specific question but in the future I recommend always deploying storage and compute as separate stacks.
@U018P5YRB8U you should split your stack before you upgrade
okay thanks, it wasn’t clear to me if a solo stack needed to be split at all (because these docs seemed to be specifically for production deployments)
great, thanks for the responsiveness!