I see the cider integration docs are still marked ‘help wanted’. I’m interested in helping clarify that section, once I have a few details nailed down.

I’m not sure if my method of integrating with cider is unofficial or wrong. What’s the difference between shadow.cljs.devtools.api/nrepl-select and shadow.cljs.devtools.api/repl ?

Also, once I build my project, what’s the best way to deploy it in a container-friendly way?

With a back and front-end project, I’d have a jar, which works nicely with Docker.

@jmckitrick I'm not an emacs user so I don't know how to configure anything. help is definitely welcome. repl delegates to nrepl-select nowadays so it doesn't matter much which on is used.

ok, cool. I’ll put together some points and open a PR

deploy depends entirely on your setup. jars works although I personally do not recommend them since you need to restart your server to reload the cLJS

If not a jar, what else for front-end only?

I’m trying to be as devops friendly as possible 😉

its just a .js file, just copying that should be enough

jar file implies you have a java webserver running as well

Right, and I don’t want that.

So we’d need a build step that copies the payload into our client app.

so just take the js file(s) and copy them to a directory

Right, ok.

and use any webserver to serve it

Yeah, that’s what I figured. I was hoping there was a more self-contained way to do it that didn’t depend on relative paths to other projects. Oh well.

Maybe what I need to do is move this project into that one, and call shadow as part of that build.

don't unterstand what you mean

Well, this project is in its own repo. And we like to be able to deploy components into containers from standalone repos, where possible.

no idea what that means "deploy components into containers"

So each repo represents a component, either a server, a nodejs front-end, etc.

Each repo is deployed into a docker container, which is deployed into Rancher or Kubernetes

Without dependencies on other components.

yes but your server must serve the .js files

how else would the client access them

Correct. Node comes with express, and obviously a jar file would have netty or something similar.

is express directly serving the traffic or is something like nginx in front?

or any other loadbalancer?

how do you deal with other assets? ie. css, images, etc

express is a tiny server that just serves up the index, js, and css for one component.

This is all behind Rancher, loadbalancer, nginx, etc

Anyway, I don’t mean to bore you with our devops details, I just want to pick the best way to get our payload into our build.

I would just copy things to a path that nginx is serving

Right, that’s probably what we’ll do.

things used to be so much simpler without all these containers 🙂

Yep! I think I found my answer. Since this is all npm-integrated, I’ll configure the project to serve the assets with express.