Henrik Feldt
@dajudge First set e.g. `resources` on the postgres resource while you have `spiloFSGroup: 103`, wait for it to stabalise, then set the TLS setting, then wait for it to stabilise.
Ping, what's the status of this?
``` app-analytics-db-1 postgres 2021-02-08 19:20:00 UTC [86]: [1-1] 60218ee0.56 0 FATAL: could not load server certificate file "/tls/tls.crt": Permission denied app-analytics-db-1 postgres 2021-02-08 19:20:00 UTC [86]: [2-1] 60218ee0.56 0 LOG:...
Seems like it's not enough to configure according to the docs and to the above; you also have to ensure you're not running the sts as root.
The problem with this is that the latest Spilo operator 1.6.3 simply overwrites these despite setting them as `spilo_runasgroup` and `spilo_runasuser` in the global operator configuration... @FxKu Time to release...
It should not be a timeout; if the concurrent process crashes, wait-on should terminate immediately.
Is it? https://app.circleci.com/pipelines/github/logary/logary-js/548/workflows/3fe43dc2-fded-4f48-8cad-77684f5e58a4/jobs/700 This is how.
https://github.com/kimmobrunfeldt/concurrently/blob/master/README.md#why
I guess I'm saying that wasting 10 minutes x all the instances using this "orb", is a huge waste, when IRL it might crash after 5 seconds: so it's better...