Fork me on GitHub

Anyone doing interesting things with Clojure CLI tools and deps.edn? I’ve been enjoying rebel readline, it’s a great command line REPL experience. Also enjoying clj-new and depstar from @seancorfield I have started using figwheel-main with deps.edn too, seems quite nice and clean. Starting to ge the hand of separate aliases and builds Any other things I should take a look at? I hope to find some time soon to finally look at edge by JUXT to understand how that works.


Just a pattern of usage that you might be interested in: We have a bunch of command line custom dev tools that we include in multiple projects via deps.edn. It means every developer can get the version locked tools without having to install them by hand.


oh also you’ve reminded me, I wrote a deps.edn tool to deploy jars to clojars or a private S3 repo (wagon)… as there was no way to do it with a pure clojure tool. It’s still in a private repo and I’ve been meaning to release it, but completely forgot.


ahhh man… I asked if anyone knew about one of those!


dunno when you wrote it, but I've been afk from slack 🙂


it’s not significantly different to what’s in deps-deploy by the looks of it


though i support pom templates too


what's a pom template? your own invention?


essentially injecting values into a selmer template to build the pom


ah, magic 😄


I think pom manipulation was outsourced to another library


the idea being that deps-deploy is hyper-focused on taking a jar+pom and sending it somewhere. How you create that pom is a separate concern.


it’s true - I wanted an easy solution.


(I don't think templating the pom is too common a concern either)

dominicm14:07:40 is pretty neat for the common version part though 🙂


> I don’t think templating the pom is too common a concern either It’s probably not common. One of my usecases was actually in a non clojure assets repo that we wanted to include as webjars in a downstream clojure project. The repo essentially had a common base of styles and different themes (extra css, and other assets e.g. logos etc). So we wanted to build multiple jars from one project with different asset names.


Incidentally it looks like deps-deploy wasn’t an option for me as it doesn’t work with private repos and S3 wagon. So I may strip out the pom-templating and push my tool… though tbh it might be better just to extend deps-deploy with the wagon code I have.


that would be cool 🙂


You already knew what I was going to badger you about 🙂


pack (a deps.edn packager) just gained a neat feature - it can generate a docker image directly from your deps.edn file

👍 4

I just saw pack, sounds very useful for those times you need docker. Thanks


it also does uberjars 🙂


pack was designed under the principle of "don't mess with the classpath - it makes bad things happen". So far that's allowed me to sidestep a number of bugs that plague the other uberjar tools, and also be much faster. That principle turns out to extend really well to other things like AWS lambda and docker, hence the natural extension of pack to them.


Sounds very useful. I had a quick look at depstar (great name and logo) and Sean did note there were limitations. Sounds like pack is more complete. Thanks


I will do a broadcast or two on using Edge soon, now that I am starting to understand the approach.


Let me know if you have any questions 🙂


oh, oh, I'll tell you what's really cool! allows you to create a nested deps.edn context in your application.


I'm using it for generating the Edge docs, I load codox+the dependency into it's own runtime, so that the docsite deps don't interfere with the dependent ones. It's much faster than shelling out to java.

👍 4

Thanks. That's a useful use case to think about.


I think it would be fun to build a clojure-style application server with, but haven't tried yet


@jr0cket I assume you've looked over my dot clojure repo? Although that's my personal setup, we have quite a bit of that copied into our base deps.edn for our monorepo too.


Thanks Sean, I am steadily working through your examples and projects, highly useful. Thank you.