lein-figwheel

Jenny Kwan 2019-01-04T02:56:54.003900Z

Sorry for the basic question, but unable to find this: how do I fix the server and client websocket ports? I'm running an app (templated by Chestnut running lein-figwheel 0.5.18) inside of a Vagrant Virtualbox. I'm hoping to allow multiple of these to be running and hacked on at once, which would require the browser client (on the Vagrant host) to connect to different WS ports for each Figwheel project, while ideally keeping static the WS port on the Vagrant guest (the Figwheel server) so that proper port forwarding in Vagrant can be set up. Any thoughts?

Jenny Kwan 2019-01-04T03:05:29.005700Z

Gah, I think I just answered my own question. Use :websocket-url using the [[client-hostname]] tag and picking up the port from an env var in project.clj while using that same env var in Vagrantfile to map the same port on the guest to the host. Gonna try it and report back.

Jenny Kwan 2019-01-04T07:15:23.007200Z

No joy. It looks like Figwheel textually reads project.clj and tries to determine the options map without actually evaluating the defproject form, which renders attempts to use any computed value for any keys impossible?