This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-20
Channels
- # arachne (11)
- # aws (2)
- # beginners (33)
- # boot (167)
- # cider (71)
- # clara (2)
- # cljs-dev (28)
- # cljsrn (3)
- # clojars (1)
- # clojure (83)
- # clojure-austin (21)
- # clojure-dev (24)
- # clojure-russia (19)
- # clojure-spec (33)
- # clojure-uk (108)
- # clojurescript (114)
- # component (1)
- # core-async (1)
- # cursive (7)
- # datomic (13)
- # editors (1)
- # emacs (15)
- # hoplon (10)
- # lein-figwheel (4)
- # leiningen (3)
- # mount (2)
- # om (134)
- # om-next (4)
- # onyx (42)
- # pedestal (41)
- # quil (2)
- # re-frame (29)
- # reagent (4)
- # remote-jobs (6)
- # ring-swagger (5)
- # untangled (9)
There will definitely be some stubs, had a couple issues in the last day or two. But the code is all there and working, and what docs are missing will be fleshed out over the next week.
Yep, we’ll be shipping with http, pedestal, an asset pipeline, clojurescript (using the asset pipeline) and figwheel
so security isn’t really something you can add after the fact: it’s more a matter of not making one of a zillion possible omissions. So it probably won’t have its own module (although maybe an adversarial robo-testing module would be a good idea). Security will be more of a “by default” thing and will be accomplished by having the right Pedestal interceptors running automatically, etc.