Fork me on GitHub
#luminus
<
2016-03-17
>
ricardo15:03:55

@yogthos: Sorry if you get this all the time, but … is the Luminus-recommended approach to RESTful services Swagger / Compojure-api now, instead of liberator?

yogthos15:03:12

Yup, compojure-api for services

ricardo15:03:03

@yogthos: Acknowledged, thanks!

ricardo15:03:13

I was going to ask for the rationale, but right off the bat, it seems cleaner.

yogthos16:03:02

Yeah I find it hits the sweet spot, you get end point schema and swagger docs

yogthos16:03:23

But I never found mapping to the HTTP state graph to be that useful myself

yogthos16:03:24

And the stateful nature of liberator makes it difficult to debug I find

actsasgeek17:03:52

I have a webapp that’s mostly luminus based using conman and mount. When I run it locally, lein -jar webapp.jar, it connects to postgres just fine. When I go to deploy it to AWS EBS in a Docker container, it freaks out and I get:

java.lang.RuntimeException: Unable to get driver instance for jdbcUrl=<redacted>
	at com.zaxxer.hikari.util.DriverDataSource.<init>(DriverDataSource.java:88)
	at com.zaxxer.hikari.pool.PoolBase.initializeDataSource(PoolBase.java:296)
	at com.zaxxer.hikari.pool.PoolBase.<init>(PoolBase.java:84)
	at com.zaxxer.hikari.pool.HikariPool.<init>(HikariPool.java:102)
	at com.zaxxer.hikari.HikariDataSource.<init>(HikariDataSource.java:71)
	at conman.core$connect_BANG_.invokeStatic(core.clj:60)
There doesn’t seem to be a way set the driver through Conman and, well, it’s all a bit mysterious anyway. Does anyone have a suggestion?

actsasgeek17:03:57

I’m also a bit curious in that the value :adapter :postgresql shown in the pool-spec doesn’t actually seem to be used anywhere that I can determine.

yogthos23:03:47

@actsasgeek: yeah the :adapter is vestigial

yogthos23:03:22

from the error it sounds like it doesn't like the url it's getting on AWS