The official documentation is always a good starting place.

You might like Lamda Island's content: https://lambdaisland.com/collections/react-reagent-re-frame

For server-side Clojure with ring and component, there is a basic guide here https://practical.li/clojure-web-services/projects/status-monitor-deps/ Or a slightly more involved guide here https://practical.li/clojure-web-services/projects/banking-on-clojure/ There are free videos on server side topics at https://www.youtube.com/playlist?list=PLpr9V-R8ZxiCe9p9tFk24ChNSpGfanUbT

I'm very grateful God bless you all

http://Jacekschae.comhttp://Jacekschae.comhttp://Jacekschae.comhas subscription based training

Thanks @U7ANZ2MTK I just checked there is a free reframe course

Question it seems I can't download and use it locally do you by any chance have the local files

Check his GitHub repo

I can't speak to how to do it with a Leiningen project but I can point you at one of my OSS projects to show how I do it for the Clojure CLI / deps.edn / build.clj: https://github.com/seancorfield/next-jdbc/tree/develop/.github/workflows (I haven't used Leiningen for over six years at this point).

Every time I push a commit to the main develop branch or merge a PR, the test-and-snapshot workflow runs to push a -SNAPSHOT JAR up to Clojars. Every time I tag a release on the main develop branch, the test-and-release workflow runs to push a full release JAR to Clojars. In both cases, the full test suite is run.

My HoneySQL project does the same thing (and includes matrix testing against different versions of Clojure)

Those also do matrix testing against different JVM versions and GraalVM versions.

Thanks, @U04V70XH6! And thank you for your service to the community! We haven't seen each other in person in years, but I want you to know how much I value you and your contributions to software engineering generally!

Would you be willing to comment on how the version is computed in build.clj? Is the major/minor manually maintained in build.clj in that private the-version fn?

Also, this is probably just me, but I strongly prefer squash on merge. Do you have any experience with how to cleanly do it from either the git flow or HubFlow extensions? The git log gets funny with how GitHub and HubFlow currently interact on merge to develop.

(defn- the-version [patch] (format "1.2.%s" patch))
(def version (the-version (b/git-count-revs nil)))
(def snapshot (the-version "999-SNAPSHOT"))

I have no exposure to "HubFlow" but I don't generally do squash on merge -- that loses the details of the commits from the branch, right? Since I delete branches on merge, I generally want that history merged as-is.

(I feel like I haven't seen anyone in person for years at this point and even for an introvert like me that's getting to be a bit much 🙂 )

If you wanted the most recent tag, rather than the commit count, you can use (b/git-process {:git-args "describe --tags --abbrev=0"}) -- although that's the whole git tag, not just the "patch" part, so you wouldn't need the-version to construct the string there.

And, yeah, I'm hard-coding the major.minor versions in the-version. I don't bump minor very often.