Ignasi Marimon-Clos

> Im using OpenJdk 8 The exact version and vendor are relevant when diagnosing some of the issues related to TLS, ALPN, HTTP/2 etc... as those are areas that are...

I think the best location is `shopping-cart/deploy/scripts/sql/` (or `ddl/`). I'd also split and rename into `write-side.sql` and `read-side.sql` (or something like that). Then, there's also some SQL for schema creation...

> @ignasi35 why do you think it's better to split into two files? I like having smaller, more clear pieces: a sql file for the journal and snapshots and another...

Once fixed, this is worth a thorough explanation on the quickstart guide.

IMHO, this issue surfaces in lagom/lagom-samples but it should be caught in either lagom/lagom or playframework/play-grpc .

This was fixed in https://github.com/akka/akka-sample-cluster-kubernetes-scala/pull/54/files so I copied the same approach in #195

Both in this issue and a few others with a similar comment from @TimMoore, I think that at least a link to the original `reference.conf` (instead of copy/pasting comments) could...

Actually, I don't think that's supported at the moment. I thought we had a specific inssue in either `lagom/lagom` or playframework/play-grpc` (which includes lagom support for grpc) but I could...

> What did you have in mind here, @ignasi35? `interaction` isthe wrong word. My point was that there are 2 settings that may result into a node/pod being removed before...

> Got it. But maybe the best place to document it is in the Lagom documentation rather than the example application? Sure! I generally like comments cross-referencing from settings to...