This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-05-30
Channels
- # announcements (3)
- # aws (5)
- # beginners (71)
- # boot (7)
- # calva (74)
- # cider (6)
- # clj-kondo (2)
- # cljs-dev (5)
- # clojars (6)
- # clojure (84)
- # clojure-dev (7)
- # clojure-europe (1)
- # clojure-italy (23)
- # clojure-nl (43)
- # clojure-sanfrancisco (1)
- # clojure-spec (4)
- # clojure-uk (173)
- # clojurebridge (1)
- # clojurescript (14)
- # cursive (44)
- # datomic (9)
- # duct (2)
- # emacs (2)
- # fulcro (4)
- # graalvm (4)
- # graphql (27)
- # hoplon (6)
- # keechma (50)
- # off-topic (3)
- # other-languages (8)
- # pathom (2)
- # pedestal (14)
- # planck (5)
- # re-frame (3)
- # reitit (6)
- # ring (2)
- # robots (2)
- # spacemacs (9)
- # tools-deps (15)
- # vim (44)
I’m trying to get a mental model on how to hook up CI with cljs with Ions. Does Ions push rely on a Git (& .gitignore) if uname is specified or is it more a snapshot on what’s in the directory?
What about the existing providers is failing to meet your needs? Does pedestal.ions library not work for some reason?
@kardan
I do
clj -A:cljsbuild ## outputs app.js
aws s3 cp app.js
echo $CURRENT_COMMIT > resources/js-ref
git commit ...
clj -A:ions ...
I have made progress, I'm not writing my own provider but I do need an interceptor for BufferedInputStream.
The Datomic Cloud schema change docs (https://docs.datomic.com/cloud/schema/schema-change.html#changing-db-ident) include this caveat:
> We don't recommend repurposing an old :db/ident
, but if you find you need to re-use the name for a different purpose, you can define the name again as described in attribute-definition. This repurposed :db/ident
will cease to point to the entity it was previously pointing to and ident will return the newly installed entity instead.
Are there any known issues with re-use other than bad practice?