morse icon indicating copy to clipboard operation
morse copied to clipboard

:host property is ignored

Open puredanger opened this issue 1 year ago • 2 comments

morse doesn't show any errors in the UI when it cannot connect to a remote, you just get a stacktrace written to stdout of the process

puredanger avatar Feb 08 '24 19:02 puredanger

replicant is the project that is actually ignoring the :host key, so when you start a replicant server it can only listen on localhost, but the morse docs for running remotely reference starting replicant with the :host key.

what happend to me is:

  1. I have never used morse before and decided to check it out.
  2. I installed morse as a tool on my laptop
  3. on my work vm I started a replicant prepl per the docs passing :host "the-hostname"
  4. launched the morse tool locally with the params to connect to the replicant prepl
  5. tried to eval some stuff, and nothing happened
  6. eventually noticed the stacktrace printed to the terminal where I started the morse tool saying it could not connect
  7. figured I must have launched replicant wrong and changed :host to an ip instead of a hostname
  8. noticed no matter what I passed as :host to replicant the started socket server is always just listening on localhost
  9. looked at the replicant code and found it was ignoring :host

hiredman avatar Feb 08 '24 19:02 hiredman

the work around I ended up using is starting the replicant prepl using:

(clojure.core.server/start-server 
 {:port   23945,
  :name   "rds"
  :address "0.0.0.0"
  :accept 'clojure.data.alpha.replicant.server.prepl/rds-prepl
  :args   [(#'replicant/create-default-cache)]
  :server-daemon false})

hiredman avatar Feb 08 '24 21:02 hiredman