Clojurians Log v2
announcements
https://www.big-config.it/ https://github.com/amiorin/big-config/blob/main/CHANGELOG.md#03256---2025-10-06 is a workflow and a template engine that enables you to have a zero-cost build step before running any CLI tool like GNU Make, Terraform, Kubectl, Helm, Kustomize, and Ansible.
It is built on a strong foundation, and we extend a huge thank you to the creators of Babashka, Clojure Tools, and deps-new for their incredible work.
• New website: https://www.big-config.it
• big-config has integrated and extended deps-edn: https://www.big-config.it/guides/build/
◦ render is the new name of the step and it should be used intead of build that was invoking deps-new
◦ selmer as templating language
◦ src is interpolated like target
◦ src can be a symbol or a function to generate files with code
• Clojure Tools is used to generate big-config templates: https://www.big-config.it/guides/clojure-tools/
◦ action: Create a GitHub action for the CI of a Clojure project.
◦ ansible: Create a repo to manage Ansible projects with BigConfig.
◦ devenv: Create the devenv files for Clojure and Babashka development.
◦ dotfiles: Create a repo to manage dotfiles with BigConfig.
◦ generic: Create a repo to manage a generic projects with BigConfig.
◦ multi: Create a repo to manage both Ansible and Terraform projects with BigConfig.
◦ terraform: Create a repo to manage Terraform/Tofu projects with BigConfig.
◦ tools: Create a tools.clj for a Clojure project.
• Template dotfiles is inspired by https://www.chezmoi.io/
• Many blog articles:
◦ https://www.big-config.it/blog/a-new-approach-to-dotfiles-management-with-bigconfig/
◦ https://www.big-config.it/blog/why-ansible-still-rules-for-your-dev-environment/
◦ https://www.big-config.it/blog/reimplementing-aws-eks-with-big-config/
◦ https://www.big-config.it/blog/killer-feature-big-config/
◦ https://www.big-config.it/blog/big-config-replaces-atlantis/
• Looking for a logo. DM if you would like to provide one.
This brings a sparkle to my eye, I dove into config-generators/managers in my first foray into Nix and Dhall some years ago (I even tried to package https://copier.readthedocs.io/en/stable/ for Nix back then, which was... harrowing), and came away a little dissapointed/uncertain- Where does/will BigConfig sit on the spectrum of stuff like Cookiecutter/Copier (strictly 'templaters') to Dhall/Nickle (DSL's used to generate structured config files)? (Or does that spectrum also have a y-axis and im missing another dimension?)
Hi @sludwig.dev! Thx for the question. Today BigConfig competes with both Cookiecutter and Dhall. I guess I prefer Clojure to Python; therefore, I find BigConfig a better solution than Cookicutter for me. I don't buy into the ideas of configuration languages like Dhall and CUE. Rather than learning a new language, I prefer to use a general-purpose language I'm already comfortable with to generate my structured configuration. One of the new ideas of BigConfig is the zero-cost build step. Have you checked it out?
> I don't buy into the ideas of configuration languages like Dhall and CUE. Rather than learning a new language, I prefer to use a general-purpose language I'm already comfortable with to generate my structured configuration. Exactly my feeling, I used to be in the 'config/templating-language-should-be-stupid/single-purpose' camp, but felt like that just kept ending up in an ad-hoc turing-complete language sprouting, whenever enough requirements would come in (not unlike PHP's life-story). Been reading some of the docs, I'm in a between period of config-life, looking at trying out #guix again, and if I can leverage more lisp/edn in more spots, I'm hoping to take that opportunity :^)
I was an early adopter of Ansible, but I started to have doubts about YAML with GitHub Actions and Kubernetes. I started to joke that we should change all our job titles to "YAML Engineer." Renovate was the last straw; it brought engineering almost to a halt by creating trivial pull requests to update the same library in multiple places. I had to do something, so I started working on BigConfig.
perhaps a demo with ascii cinema?
@dimitar.ouzounoff Ok. Any topic that you would like me to cover?
A port of hashids.clj has been released https://github.com/brandoncorrea/hashids.clj at version 1.1.0, adding platform support for:
• ClojureScript
• Babashka
• ClojureCLR
• ClojureDart
Same library as before, just with platform compatibility.
Does this use the same algorithm as hashids.clj?
Nvm, found the FAQ. Seems not. This is cool though
yeah, the biggest thing is that it's simpler than hashids and has some extra features that the original doesn't
Nice. I’ll make note of it in the readme as a recommended alternative
New version of metosin/malli 0.19.2 https://github.com/metosin/malli/releases/tag/0.19.2
• Performance improvements in malli.transform/transformer https://github.com/metosin/malli/pull/1220 and malli.core/-intercepting https://github.com/metosin/malli/pull/1219
• malli.clj-kondo/emit! saves to .clj-kondo/imports now as recommended by clj-kondo. https://github.com/metosin/malli/pull/1216
• malli.clj-kondo/emit! no longer deletes anything automatically. Use malli.clj-kondo/clean! to clean up.
• Add malli.core/old-parse-format for converting output of parse to the pre-0.18.0 format. https://github.com/metosin/malli/pull/1223
• FIX: Malli dev-mode no longer throws java.lang.UnsupportedOperationException when printing out an #inst of type java.sql.Date https://github.com/metosin/malli/issues/1214
• Updated dependencies:
borkdude/edamame '1.4.30' to '1.4.32'
fipp '0.6.27' to '0.6.29'