Channels
#server
- c
cedric
03/01/2018, 7:46 PMThe default one (I think it’s jetty?) - f
fred.deschenes
03/01/2018, 7:46 PMyup - d
dave
03/01/2018, 7:47 PMcan you run it with sunhttp ? that's effectively free... - c
cedric
03/01/2018, 7:47 PMI can probably use whatever http stack I prefer but I don’t think it’s the issue - d
dave
03/01/2018, 7:48 PMhave you got a link to your gradle file in GH? something seems odd - c
cedric
03/01/2018, 7:48 PM - d
dave
03/01/2018, 7:49 PMbtw - the max slug size according to heroku settings is 500mg: - f
fred.deschenes
03/01/2018, 7:50 PMFYI Dropwizard 0.8.0 is ancient, you should try 1.2.X or the 1.3.0 RCs - c
cedric
03/01/2018, 7:50 PMNoted - f
fred.deschenes
03/01/2018, 7:51 PMactually updating to a more recent version might remove some dependencies (not sure which version # they started at, but a lot of extra java8 libs were removed when java8 support was added natively) - d
dave
03/01/2018, 7:51 PMwow - dropwizard core relies on a load of stuff... 18 direct dependencies - d
dave
03/01/2018, 7:52 PM(that's 1.3.x) - c
cedric
03/01/2018, 7:52 PMIt’s lower than I’d have guessed - d
dave
03/01/2018, 7:53 PMthat's direct only... 🙂 - c
cedric
03/01/2018, 7:53 PMah - d
dave
03/01/2018, 7:54 PMyour gradle looks legit - unless the shadow jar plugin is doing something unexpected. - c
cedric
03/01/2018, 7:55 PMDeploying the jar file directly should work. Heroku is probably not the best tool for building anyway, a better pipeline is probably to build on a real CI/CD (Travis…) and deploy to Heroku from there - c
codefinger
03/01/2018, 8:04 PM@cedric i was able to deploy the koolaid repo. is that the one that gave you trouble? - c
codefinger
03/01/2018, 8:04 PM@cedric also https://github.com/cbeust/koolaid/pull/1 - c
codefinger
03/01/2018, 8:05 PMdeploying a pre-compiled jar is fine too. but if you deploy source you can use the full Heroku CI/CD https://blog.heroku.com/heroku_flow_pipelines_review_apps_and_github_sync - c
cedric
03/01/2018, 8:05 PM@codefinger Interesting, let me take a look - c
codefinger
03/01/2018, 8:07 PMalso maybe looks like it's binding to a fixed port (9000) instead of using the $PORT env var - c
cedric
03/01/2018, 8:08 PMIndeed. The log indicates the server started (progress!) but still not responding on 9000 - c
codefinger
03/01/2018, 8:08 PMis there a way to put env vars in the
?config.yml - c
cedric
03/01/2018, 8:08 PMI use
for that.env - c
codefinger
03/01/2018, 8:08 PMlike in a Spring application.yml - f
fred.deschenes
03/01/2018, 8:09 PMyou can have env vars directly in the yaml - c
codefinger
03/01/2018, 8:09 PMi mean like:Copy codeserver: applicationConnectors: - type: http port: ${PORT} - f
fred.deschenes
03/01/2018, 8:09 PM - c
codefinger
03/01/2018, 8:09 PMnice