Ah, very good. I see that in the new Luminus templates, and look forward to
trying it.
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - ple
The recommended way to manage components in Luminus is using the mount
library (https://github.com/tolitius/mount), it's much less intrusive than
Component in my opinion and provides most of the same benefits without
requiring you to structure your application around it. The latest version
of m
It definitly is compatible. It just takes some manual work. Like I said, I
started myself with the luminus template and implement components + other
stuff into it.
You can definitly do it and I also recommend it for the sole reason that a
change to the routes in compojure will lead to a restart
Maybe I spoke too soon when mentioning incompatibility between Luminus and
Reloaded. I look forward to taking a closer look at your work!
On Wednesday, December 2, 2015 at 1:49:20 AM UTC-7, Sven Richter wrote:
>
> Hi,
>
> I based a template on luminus myself and added some stuff. It also
> conta
Thanks for the pointers to the Reloaded pattern I've been hearing about. It
looks like it may not be easily compatible with Luminus, which would need
to be rewritten to match the pattern, but could be a great tool for my next
projects.
On Tuesday, December 1, 2015 at 9:43:41 AM UTC-7, Colin Ya
Hi,
I based a template on luminus myself and added some stuff. It also contains
predefined components so you don't have to add it yourself.
You can look how its done here:
https://github.com/sveri/closp/tree/master/resources/leiningen/new/closp/clj/components
Best Regards,
Sven
Am Dienstag, 1.
You can hardcode the nrepl-server port with :repl-options {:port 4001} as
seen at [1].
When thinking about it, maybe you could script tmux or similar to show all
running terminals at once, like shown in [2].
[1]
https://github.com/technomancy/leiningen/blob/master/sample.project.clj#L354
[2]
The general idea is to use the ‘reloaded’ pattern, so rather than `lein run`
you would have a function which starts and stop the system. You still need to
run figwheel and mongo (yay for document databases) as separate processes,
although I tend to do those in straight terminals rather than emac
I recently read something hinting at ways of streamlining the startup
process for the dev environment, so I'm hoping you good folks can give me
some tips. I'm developing a web app in Linux, Clojurescript/Clojure
(incidentally using the Luminus architecture). I use emacs (that part's
non-negotia