Fork me on GitHub
#lambdaisland
<
2023-03-24
>
Drew Verlee00:03:59

The readme for the launchpad docs states: > • When working on multiple related projects we prefer a single JVM over multiple What makes projects related? Why prefer a single JVM over multiple? I'm embarrassed to say I feel like I need a diagram to remember where the JVM fits into the development process. I think it's probably correct to say that the nrepl server is a JVM process?

Drew Verlee00:03:38

if i use the launchpad template, and add the alias proj2, as well as some src namespaces in both projects and a dep just in project 1, i can confusingly require the dep in project 2. It seems like the launch pad is just combining the deps into one repl. I take it to mean that these "projects" are themselves actually libraries? I guess I don't understand what the :launchpad/aliases is meant to achieve, I had first thought it would launch a repl per project and have them connect.

Drew Verlee01:03:12

sorry for the barrage of questions. let me know if I should direct my energy elsewhere 🙂 . I tried to use the launch pad to launch by web app which has three directories, backend, frontend and middlend. As a first shot, I copied the launchpad template into the parent directory of those three and mentioned the local/root for the backend directory. Then I launched, and it immediately complained that it couldn't build the classpath because of the artifact com.snowtide..blah which If i recall correctly is an issue relating to datomic permissions. I'm not even sure what the question is, just reporting that i find the readme on launchpad to be very tantalizing but i can't as of yet piece together what it's trying to do.