Clojurians Log v2

@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?

::http/host "0.0.0.0" should work for dev setup

@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

It works on local/REPL?

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?

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.