This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-05-08
Channels
- # aws (9)
- # beginners (69)
- # boot (14)
- # cider (26)
- # cljs-dev (56)
- # cljsrn (9)
- # clojars (4)
- # clojure (229)
- # clojure-brasil (1)
- # clojure-france (11)
- # clojure-greece (2)
- # clojure-italy (4)
- # clojure-mke (6)
- # clojure-serbia (6)
- # clojure-spec (83)
- # clojure-uk (38)
- # clojurescript (171)
- # core-async (3)
- # cursive (11)
- # data-science (11)
- # datomic (27)
- # emacs (113)
- # funcool (6)
- # hoplon (4)
- # jobs (1)
- # luminus (13)
- # lumo (44)
- # off-topic (148)
- # onyx (5)
- # overtone (1)
- # pedestal (4)
- # powderkeg (1)
- # proton (2)
- # re-frame (150)
- # reagent (16)
- # ring-swagger (43)
- # spacemacs (4)
- # specter (36)
- # vim (4)
- # yada (10)
Just wanna say thank you to @yogthos for making memory-hole as a thing I referenced to figure out how to do authenticated compojure-api building!
I read your book but it defining it in restricted-routes wasn’t wrapping the body in the right way, so i used the new template’s way. i’m also gonna learn re-frame using memory hole. I’d just use it as a blanket SPA template if not for the license :)
It’s the most advanced (and modern) open source clojure site setup (that’s not highly specialized) that I’ve found.
and took a bit of digging to find the idiomatic compojure-api way to do auth, but it’s pretty nice once I got it working in memory hole
Ahhh I see. Also, side question: did you design macchiato in a way that it’s somewhat transparent to port an app on the JVM backend to node, or is it (a lot) more complicated?
(I haven’t even tried, but it seems like a nice alternative to deploying a little test thing on a free heroku dyno vs using the JVM)