sooo how do I change the nRepl port in dirac (I have 5088 instead of 8231 in a project)

actually it seems I am launching two nrepls:

Adding :preloads dirac.runtime.preload to main.cljs.edn...
nREPL server started on port 8230 on host 127.0.0.1 - 
Writing figwheel.connect.main-acfc07d9 namespace to main_acfc07d9.cljs...
Adding :require(s) to main.cljs.edn...
nREPL server started on port 5088 on host 127.0.0.1 - 
Adding :require adzerk.boot-cljs-repl to main.cljs.edn...
Compiling ClojureScript...

weird, I receive:

console.error("Unable to resolve backend-url for given tab-url (via debugger-url).
reason: empty body response from api-endpoint=
tab-url=, debugger-url=

I have a fairly uncommon setup but the pieces are there

ok I am trying the oraculum now 😄

@richiardiandrea I’m back, I could try to help now

so the oraculum downloads the right version...

so then I need a way to use it...uhm...ok maybe the functionality it's not there yet

oraculum has some ad-hoc functionality, I use it to do mapping between chromium revision numbers to downloadable builds, or retrieve latest chromium revision, etc.

oh ok, so launching Chromium canary would be out of scope?

well, maybe you should write what are you trying to achieve, Chrome Canary is some Chromium version selected by google devs, Chromium builds are continuous, you can pick any Chrome revision

I use oraculum to generate health-check branch, to test specific Chromium builds against recently release Dirac extension: https://github.com/binaryage/dirac/commits/health-check

e.g. the commit message tells travis what to test https://github.com/binaryage/dirac/commit/8a5a2c855f0c00821316f146a7f1c16cb68714f5

and to generate it I use oraculum: https://github.com/binaryage/dirac/blob/master/scripts/health-check.sh

Ok gotcha, I just would like to have a way to tell my colleages "here is a Chrome/Chromium you can use to debug Cljs"

the above Chromium will have Dirac installed/point to a local profile that has Dirac

probably I can fork the oraculum...if it seems you'd not want this feature..

oraculum project should ideally have no knowledge about dirac, at least right now it is an independent tool

yep I agree

but if data is persisted on the host

oraculum would be just a docker container containing Chromium canary

I just need to tunnel X, lol 😄

probably worth a fork

I don’t follow, what is X? 🙂

http://dasunhegoda.com/gui-ubuntu-server-x11-forwarding/679/

sounds like an overkill to me

devs are lazy 😄

especially when you need to convince them to switch tech

I imagined you want a simple (bash) script, which given dirac version would download matching Chromium build and setup some launch scripts with proper dirac-specific chromium args

yeah that too

I am still evaluating options 😄

why do you want to run that chromium inside docker?

a script would do, I am evaluating what to do as well speak...initially I though the oraculum was already doing that 😉

you could write a script which would scrape Dirac’s release page and get the links from there, see https://github.com/binaryage/dirac/releases/tag/v1.2.10

or use something like this script to compute those links on its own: https://github.com/binaryage/dirac/blob/master/scripts/prepare-chromium-links.sh

I extract chrome version here: https://github.com/binaryage/dirac/blob/master/scripts/prepare-rolling-section.sh#L31-L32

oh cool sounds you have already all the pieces

chrome version is baked in here https://github.com/binaryage/dirac/blob/master/resources/unpacked/devtools/front_end/InspectorBackendCommands.js#L1

this file gets regenerated quite often when I pull new changes from official chrome repo via this script: https://github.com/binaryage/dirac/blob/master/scripts/regenerate.sh

ok very cool

Thanks a lot!

np, good luck and let me know if you get stuck on smthng

kk