I went with a separate alias paired with a tweaked VS Code build tasks. It perfectly solves my dev experience, and I only need to remember the pinning, which I could probably automate, but for now I prefer to do that part consciously every time. I think Leiningen or deps.edn doesn’t really matter here. They both provide a way to point at something locally. My mistake was to rely on editing the config instead of keeping two configs, easily selectable.
General Question - Any Clojurians using DataDog ( https://www.datadoghq.com/ ) out there? Is there a more specific channel to discuss this (I can't find a #datadog channel, but is there a channel for SaaS monitoring / metrics)?
Yes - I use it at $dayjob, let's chat in #C010TGGL02X
yeah, at work, made https://github.com/StudistCorporation/sleepydog/ for it too
Thanks @vale and @lukaszkorecki that's good to know, and I have joined #C010TGGL02X 🙏
(sorry about the splashy preview, I've removed it)
I push to github and use git sha that way you can use it with git-subtree/worktree without the relative dance with local-root
I also push to github using git sha. But in Backseat Driver everything about MCP happens in the library so developing on BD means developing on vscode-mcp, and pushing to github, starting it there and attaching to a repl in the cloud isn’t really an option.