This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-10-04
Channels
- # babashka (17)
- # beginners (82)
- # calva (42)
- # clj-commons (9)
- # cljdoc (2)
- # cljsrn (3)
- # clojure (142)
- # clojure-europe (12)
- # clojure-nl (1)
- # clojure-sg (1)
- # clojure-uk (14)
- # clojurescript (22)
- # community-development (3)
- # cryogen (12)
- # cursive (15)
- # data-science (13)
- # datomic (11)
- # deps-new (8)
- # emacs (3)
- # fulcro (31)
- # gratitude (7)
- # holy-lambda (8)
- # honeysql (6)
- # introduce-yourself (1)
- # jackdaw (11)
- # jobs-discuss (7)
- # kaocha (1)
- # malli (8)
- # other-languages (9)
- # pathom (14)
- # pedestal (1)
- # polylith (3)
- # portal (12)
- # re-frame (3)
- # react (3)
- # reagent (4)
- # releases (3)
- # reveal (7)
- # ring (11)
- # shadow-cljs (17)
- # specter (3)
- # sql (1)
- # timbre (2)
- # tools-deps (122)
- # xtdb (18)
Have you desired for Cryogen to autom. reload the page in the browser while you are editing locally? Soon it can do that: https://github.com/cryogen-project/cryogen/pull/242
Just tried to test out this branch. But having problems setting up the test. How do I get the template in the PR when using clj-new to create a new blog for testing? (I've stopped using lein).
FWIW, what I tried was to first git-clone the repo and switch to the auto-refresh-broswer
branch. Then, I ran clojure -Tclj-new create :template cryogen :name myname/myblog :force true
which worked (as normal). But then I tried clojure -Sdeps '{:deps {foo/bar {:local/root "cryogen"}}}' -Tclj-new create :template cryogen :name myname1/myblog :force true
and that did not work. I got the following: Error building classpath. Manifest type not detected when finding deps for foo/bar in coordinate #:local{:root "/Users/dorab/Projects/cryogen"}
I guess, because the cryogen project itself does not have a deps.edn
.?
perhaps generating pom via lein fixes it
@carmen or @yogthos could you be so kind and release https://github.com/cryogen-project/cryogen 0.6.4? While at it, would you consider forbidding pushes directly to master so that everything needs to go through a PR? (😅 ) BTW what do you think about some automation, as described here https://slipset.github.io/posts/deploying-to-clojars ? I am happy to help.
doing CI wouldn't be bad, maybe could have a release branch then, and when we check in there it builds and deploys from there
Yes, why not? Less trouble that way...