Trevor Hartman

Thanks @dblandin. Not sure when I'll be able to get to it either :)

Agree, why not default it to `_id` or something? Alternatively, let users set a global default so we don't have to keep passing `{ idField: "id" }` on all `useFirestoreCollectionData`...

Is there not a simple way to pull stuff out of react context in `getInitialProps`?

Seems like GitHub/Bitbucket/GitLab username should be a separate field. My name is not `devth`.

I'm working on a custom image that installs and configures it. I'd be happy to PR if it's something you're interested in. I think enabling SSL by default makes sense,...

Makes sense overall, though my ssl is a bit weak so I don't follow the specific commands 100%. Not sure if you saw but the SG SSL repo provides [example...

Good point, I hadn't considered K8S secrets. I'll be working on it over the next few days.

We ended up deciding to use Elastic's Shield product, so I didn't get very far with this. I pushed my changes here: https://github.com/devth/docker-elasticsearch-kubernetes/commit/a550a29197f2ffeaf6c83cfa0901448b63179924 I was adding the keystore and truststore...

I increased `LEGO_MINIMUM_VALIDITY` to 80 days to force it to refresh. It successfully got a new certificate and stored it in the correct secret, but the `alreadyExists` issue remains.

Filed https://github.com/kubernetes/ingress/issues/330. I guess I could just delete the SSL cert in gcloud, but I'm trying to figure out a non-destructive way to recover without downtime.