This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-04-03
Channels
- # announcements (4)
- # aws (13)
- # babashka (35)
- # beginners (162)
- # boot (8)
- # calva (5)
- # chlorine-clover (15)
- # cider (64)
- # clj-kondo (20)
- # cljs-dev (29)
- # clojars (6)
- # clojure (166)
- # clojure-europe (3)
- # clojure-finland (6)
- # clojure-france (8)
- # clojure-germany (3)
- # clojure-italy (3)
- # clojure-nl (7)
- # clojure-spec (49)
- # clojure-uk (83)
- # clojurescript (39)
- # clojurex (5)
- # core-typed (2)
- # cursive (3)
- # data-science (17)
- # datascript (3)
- # datomic (22)
- # exercism (5)
- # fulcro (3)
- # jobs-discuss (2)
- # joker (2)
- # kaocha (3)
- # malli (26)
- # off-topic (89)
- # pathom (10)
- # pedestal (14)
- # protorepl (14)
- # re-frame (23)
- # reitit (2)
- # shadow-cljs (27)
- # slack-help (10)
- # spacemacs (14)
- # tools-deps (10)
- # tree-sitter (3)
- # xtdb (19)
- # yada (2)
what is the current status of fern in vase? I just failed to load deps dependency
{:deps {com.cognitect/pedestal.vase {:mvn/version "0.9.4-SNAPSHOT"}
from Clojars
{:deps {com.cognitect/pedestal.vase {:git/url ""
:sha "d882bc8f28e8af2077b55c80e069aa2238f646b7"}
works of course; is that my only option if I want to use fern?@ben.hammond on the back burner atm. We’ve not officially released a version of vase using Fern. There are a few changes I’d like to make before doing that. Just need the time.
are there any nasty surprises to be aware of? can I have multiple .fern files that I can link together? do I have to shoehorn everything into one file?
Nast surprises -> not that I know of Multiple file support/using one file -> Vase expects your service config to be in a single file
and if I want some kind of (fern/lit include-file
then I need to write my own ?
@ben.hammond I’d avoid getting too clever, though. reading in schema as edn should be fine but partitioning config and accessing parent config env in included files is a different matter. The later is not possible
If you do want to partition your config into separate files and access env across them then consider a pre-processing step which joins them prior to loading them.
once you start sticking datomic schema in there, I can imagine a single config file getting bloated pretty quickly
The primary issue I’d like to resolve before cutting another release is https://github.com/cognitect-labs/vase/issues/45
I wrote my first API using pedestal and everything works with lein run
or using an uberjar, but not inside a container. I tracked it down to a step with a POST
call (using clj-http-lite
, but I also tried hato
) to GraphQL. Everything works on the REPL outside the container. Could this be related to pedestal, or should I look elsewhere? I tried using both immutant and jetty and it doesn’t make a difference. My host is set to 0.0.0.0
because otherwise I couldn’t send requests to the container