This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-11-01
Channels
- # announcements (3)
- # babashka (20)
- # beginners (77)
- # calva (27)
- # cider (5)
- # clara (3)
- # clj-kondo (9)
- # cljs-dev (4)
- # cljsrn (5)
- # clojure (26)
- # clojure-europe (32)
- # clojure-italy (5)
- # clojure-nl (3)
- # clojure-uk (5)
- # clojurescript (25)
- # clojureverse-ops (4)
- # core-async (49)
- # cursive (15)
- # data-science (1)
- # datahike (4)
- # datomic (3)
- # docker (1)
- # events (1)
- # helix (5)
- # holy-lambda (3)
- # introduce-yourself (1)
- # jobs (1)
- # kaocha (2)
- # lsp (15)
- # malli (42)
- # off-topic (18)
- # pathom (18)
- # pedestal (12)
- # polylith (7)
- # rdf (1)
- # re-frame (22)
- # reitit (2)
- # releases (1)
- # remote-jobs (1)
- # rewrite-clj (33)
- # shadow-cljs (85)
- # spacemacs (3)
- # vim (12)
- # xtdb (29)
Hi guys
• We have machines dev1, dev2, devN running nREPL on the same port (7777)
• We sometimes need to connect to multiple machines and preferably not have to kill CIDER's nREPL connection before connecting to another machine
• Would it make sense to change nrepl--ssh-tunnel-connect
such that it used a random unused local port (i.e. not just forward remote 7777 -> local 7777)?
I don't mind implementing this myself and making a PR, just wanted to sanity-check that the behaviour proposal makes sense
That sounds reasonable. Although writing up an issue and and posting a potential solution would be a good idea. Off the top of my head I don’t see why you don’t just connect to to the nrepl port on that machine directly
Right, yea I'll do that. I can't connect directly because only way is through a bastion host
ah i'm surprised it works through cider. i figured you'd have to open those tunnels manually with the correct identify file
I think it's because if you don't specify an identity file SSH commands default to id_rsa
(which I use)