This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-04-02
Channels
- # announcements (2)
- # aws (7)
- # babashka (47)
- # beginners (54)
- # biff (6)
- # calva (14)
- # clojure-europe (7)
- # clojure-germany (2)
- # clojure-japan (4)
- # clojure-norway (5)
- # datalevin (1)
- # deps-new (13)
- # helix (5)
- # hoplon (1)
- # hyperfiddle (12)
- # introduce-yourself (6)
- # joyride (1)
- # malli (2)
- # off-topic (21)
- # polylith (11)
- # re-frame (3)
- # reitit (8)
- # remote-jobs (1)
- # scittle (25)
- # shadow-cljs (20)
- # vim (19)
- # xtdb (4)
I'm writing a small article on https://github.com/practicalli/blog/pull/158. Its probably still quite rough, but if anyone has time for feedback it would be appreciated. Interest to know if it makes sense and if I misunderstood something. Article published on the staging version of my blog at: https://practical.li/blog-staging/posts/create-deps-new-template-for-clojure-cli-projects/ Thank you.
"Include the library when calling deps-enw" <- typo
:project/create
{:replace-deps {io.github.seancorfield/deps-new
{:git/tag "v0.5.0" :git/sha "48bf01e"}
Probably a good idea to update to 5.1 and sha 21cede2 (two places)"build - source of the dependencies (deps.edn) and build (build.clj) files in the new project" -- they're actually deps.tmpl
and build.tmpl
aren't they? (so tooling doesn't get confused)
:transform
[["build" ""
{"build.clj.template" "build.clj"
"deps.edn.template" "deps.edn"}]
You'll need :only
here to prevent those .template
files being copied as well.(these are just nit-picks -- this is great to see, as an article, and once it is published I'll add a link to the deps-new
README for it!)
Thanks, that's helpful. I'll update a few sections and clarify things over the next couple of days. I still have a bit of work to do on the initial practicalli/project-templates to complete, then I'll release together
The deps-new programmatic approach looks useful for adding optional parts to a project, but I think I'll save that for a second article. I'd like to make component systems optional and provide a few choices. Also add some persistence choices (postgres, h2, etc.).
As I continue to work on https://clojure-doc.org I find myself adding links to http://practical.li docs more and more often to avoid duplicating your work 🙂
Happy to discuss any work you are doing with http://clojure-doc.org and anything I can do to help. If there are links to the http://practical.li/clojure-web-services book, let me know as I will be updating that book quite a lot in the next few months I'll review http://clojure-docs.org if I make any breaking changes though (I usually add a redirect if it's a page move, but if I refactor content significant then Ill let you know (or send a pr) Thanks
I've pushed what I believe to be the final draft of the article. I'll publish early next week https://practical.li/blog-staging/posts/create-deps-new-template-for-clojure-cli-projects/
In Create template project, you have "clojure -Tnew template :name practicalli/service if deps-new was installed as a Clojure CLI tool" which links to the templates section -- I think it should link to the top of the readme where the tool installation is shown?
That's the only suggestion I have -- it's a great article! Once it is published, I'll link to it from deps-new
and also link to your templates repo.