I haven't used "lein ring server", but my understanding is that it reloads when you write to disk. If you're just using the Eval feature of Fireplace, it's not going to write anything to disk, so lein won't know it should reload.
I've been using fireplace with the "manual" ring process described here: https://github.com/mmcgrana/ring/wiki/Interactive-Development which seems a lot more flexible and convenient. It doesn't require writing to disk, so you can, for example, make temporary changes in a library, evaluate the form with fireplace, and the server is updated live. I've been leaving a comment like ; (defonce server (run-jetty #'handler {:port 8080 :join? false})) which can be evaluated in fireplace with cp% to start the server. New routes are picked up when evaluated in the same fashion. On Sunday, April 27, 2014 10:22:01 AM UTC-7, Jarrod Swart wrote: > > I've noticed that when using Ring + Compojure w/ LightTable the following > process will get me access to any newly added routes. > > 1. Add a route > 2. Eval the route NS > 3. Eval the handler NS > 4. Check route in browser > 5. Success > > Recently I've begun using Vim + Fireplace. > > I cd to my project dir and start a 'lein repl'. I then startup a 'lein > ring server'. > > With this setup I can only access newly added routes when I completely > restart the server. > > What am I doing wrong? > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to [email protected] Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
