If you use @weavejester’s Ragtime for DB migrations and 🔥 to use Sean's awesome next-jdbc, you can do that now with the release of https://clojars.org/dev.weavejester/ragtime.next-jdbc (notice the group id)

Announcing 0.0.2 of https://github.com/lispyclouds/contajners An idiomatic, data-driven, REPL friendly clojure client for OCI container engines The main feature is that its now #babashka compatible from source! Thanks a lot @eugen.stan @imdad.ahmed for the majority of the work! 🎉 🎉

Announcing https://github.com/FieryCod/holy-lambda-ring-adapter, that is compatible with all holy-lambda's backends: native, babashka, clojure. This is an optimized version of what is already used in production in Retailic. Demo: https://9g7a59k254.execute-api.eu-central-1.amazonaws.com/api-docs/index.html Welcome screen: https://9g7a59k254.execute-api.eu-central-1.amazonaws.com/welcome-screen Source code: https://github.com/FieryCod/holy-lambda-ring-adapter/tree/master/examples/native/src/example Rationale I wanted to build a library that provides a simple full-featured integration between Ring and AWS Lambda. A Library that doesn't vendor-locks the user with AWS Lambda. With the holy-lambda-ring-adapter you don't care about the AWS Lambda, and just regularly develop your application locally with all the goodness you already know. You're entitled to deploy your application either to AWS Lambda or to regular servers with simple commands. Cold starts are optimized, and for our API with dozens of dependencies it's only <=500ms on ARM64. 🙂 EDIT: If you're interested in running Ring apps on AWS Lambda join #holy-lambda channel 🙂