This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-07-30
Channels
- # announcements (6)
- # bangalore-clj (1)
- # beginners (169)
- # boot (8)
- # calva (20)
- # cider (32)
- # clj-kondo (78)
- # cljdoc (42)
- # cljs-dev (4)
- # clojure (126)
- # clojure-china (35)
- # clojure-dev (5)
- # clojure-europe (3)
- # clojure-italy (40)
- # clojure-nl (15)
- # clojure-portugal (1)
- # clojure-spec (4)
- # clojure-uk (67)
- # clojurescript (89)
- # community-development (2)
- # core-async (34)
- # cursive (46)
- # datomic (14)
- # dirac (1)
- # duct (8)
- # emacs (11)
- # events (5)
- # fulcro (21)
- # jackdaw (14)
- # jobs-discuss (6)
- # off-topic (37)
- # pedestal (24)
- # perun (1)
- # quil (3)
- # reagent (27)
- # reitit (1)
- # remote-jobs (1)
- # shadow-cljs (47)
- # sql (1)
- # vim (9)
- # yada (1)
@ariel.silverman
It's about BREAKING CHANGE: nil ::host in service map defaults to localhost now (rather than being container specific) #557.
?
https://github.com/pedestal/pedestal/blob/master/CHANGELOG.md#054---june-29-2018
Thank you for replying @souenzzo, I don’t think this is it, I am moving from 0.5.5 to 0.5.7. I had that issue fixed back last month.
#pedestal - gotta love the “pull requests welcome message” found here: http://pedestal.io/reference/jetty
@souenzzo - Now that I think about it maybe I addressed issue 054 incorrectly, what I did was the following: In my pedestal config I added
{
...
::http/host "0.0.0.0"}
maybe this is not the appropriate fix for 054
Are you running it inside a container?
@jvtrigueros I run in a container that is deployed to ECS (AWS)
this is my config for prod
0.0.0.0
is an unsafe default but necessary if running inside a container
yeah, I am only seeing a timeout of the http server when I deploy to the higher environments
I saw there were some changes to the container-options
for jetty
I am setting ssl via:
{::http/container-options {:h2c? true
:h2? false
:keystore "./config/keystore.p12"
:keystore-type "PKCS12"
:key-password "qwerty"
:ssl-port 9302
:ssl? false}}
honestly I am looking to get maybe some background and docs on :io.pedestal.http.jetty/http-configuration
because its pretty opaque and there is no docs I could find on it
looks like maybe my cloud deployment was the issue, however I am starting to feel the pain with the lack of documentation in pedestal.
I've been following this conversation, but I'm still confused as to what the issue is that you're facing. I understand the docs are limited, so perhaps once you're past this a small PR would go a long way 🙂 Anyway, what exactly are you having issues with? And is there a repo I can look at and perhaps reproduce?
@jvtrigueros - It turns out that we had an issue with our deployment pipeline and not with the actual code. Thanks for following up. Regarding your comments, its increasingly harder to use pedestal in a production setup when many of the configurations are missing documentation and its unclear what are the side effects of such configurations
Hey Folks, is there a way of a function to coerce data when entering my api with pedestal? Something that i pass de data and the schema to coerce then will try to coerce for me.
I imagine you would do this with an interceptor. An interceptor has two stages, incoming and outgoing (don't remember proper terms from memory).
@quieterkali I have been doing this via a custom interceptor as a pattern
e.g. using reitit + Pedestal, you can use schema or spec to define the data and have generic coercion interceptors do the transform based on the models
@jvtrigueros - It turns out that we had an issue with our deployment pipeline and not with the actual code. Thanks for following up. Regarding your comments, its increasingly harder to use pedestal in a production setup when many of the configurations are missing documentation and its unclear what are the side effects of such configurations
@quieterkali I have been doing this via a custom interceptor as a pattern