This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-04-19
Channels
- # aws-lambda (4)
- # beginners (62)
- # cider (20)
- # cljs-dev (9)
- # cljsrn (13)
- # clojars (3)
- # clojure (105)
- # clojure-brasil (1)
- # clojure-denver (1)
- # clojure-finland (4)
- # clojure-italy (23)
- # clojure-norway (1)
- # clojure-spec (6)
- # clojure-uk (56)
- # clojurescript (41)
- # cursive (10)
- # datomic (25)
- # emacs (23)
- # figwheel (2)
- # fulcro (133)
- # graphql (12)
- # hoplon (32)
- # instaparse (13)
- # keechma (1)
- # lein-figwheel (1)
- # luminus (1)
- # lumo (1)
- # nyc (2)
- # off-topic (34)
- # om (2)
- # onyx (10)
- # pedestal (8)
- # portkey (1)
- # re-frame (10)
- # reagent (26)
- # ring (8)
- # shadow-cljs (77)
- # spacemacs (4)
- # sql (8)
- # tools-deps (15)
- # vim (9)
do you mean pedestal-app or pedestal server?
@mv as far as I know pedestal-app is not really maintained anymore, for server side stuff with a clojurescript frontend I’ve found it easiest to set up 2 different projects where the frontend code has its own figwheel server and the “custom” server stuff is on another process.
In production it turns out that usually you’d deploy the frontend app on some other server than the backend service (app on S3, with caching/CDN) so you need to make sure that that works anyway.
@mv this project uses pedestal (server) and figwheel: https://github.com/thegeez/clj-board where figwheel is started from the repl (see dev/clj/user/clj), instead of through lein fighweel
@joost-diepenmaat yep, pedestal-app is no longer maintained. I’ve also found the two project approach (front end, service) to be the preferred approach as well. /cc @mv
@joost-diepenmaat in case of a split codebase, have you ever experienced that you wanted shared code, and how did you deal with that?