Clojurians Log v2

Are those other JVM processes or something completely separate?

I used https://cr.yp.to/daemontools.html for that in the past

what you are describing what any init system does, and daemontools just happens to be a sort of init system that is easy to run separately from the init system of the os

but for example, if you are running on linux you could have systemd do it

lets see. in our monorepo: - some docker services are defined - there's a front end built with an npm script - there's a java api not in our repo, - neo4j - occasionally a neo4j-admin command (if I'm setting testing state)

- a selenium server to stand up

I think that's it. In my dreams I can trigger a test run against different commits--- I've already wrapped JGit a bit, for changing what commit the repo is at

Docker compose could start any dockerized services. If you tag your images, you could launch them at those points.

:thinking_face: The services are changing rarely enough that I probably should solve that last. It's the front end and api serving it that change the fastest. Probably that's the slice to bite off

They're the parts I rebuilt a couple three times today

Afterthought: I wonder if those containers, they're full of Java services. Maybe I should start them a different way than the other devs, and learn to e.g. simulate service outages

I think systemd running the selenium server is a good call... That should be running 99% of the time that I'm at work

There's probably two things going on: - being tired of my dumb ass forgetting to, e.g., start the typescript compiler - the more legit work of, sometimes I want to see if a subset of tests that failed will also fail against a different SHA of the codebase

make / Makefile would be another possibility to encode dependencies between your services