James Addison

@abhinavrau Thanks for getting in touch - `cloud-grocy` looks excellent. Out of interest, is the exposure and regular reload of the [`nginx conf.d`](https://github.com/abhinavrau/cloud-grocy/blob/master/docker/docker-compose.yml#L23) volume in place to handle a specific...

@abhinavrau That all sounds reasonable; and thanks for the link to the nginx-certbot project - I've had a read through some of the content there. When you have time I'd...

@abhinavrau That's great to hear! Out of interest, are the three additional containers required at application run-time, or are some/all of them only required during certificate provisioning (and renewal)? Making...

Additional idea: automatically run vulnerability scans (during pull requests and/or release packaging). Resolved by [v3.3.1-3](https://github.com/grocy/grocy-docker/releases/tag/v3.3.1-3).

A few mistakes were made during release changelog updates, release tagging, and upload to Docker Hub during releases `v3.0.1-12` and `v3.1.0-0`. Automating more of the process should help. Resolved by...

Validating the lockfile using a continuous integration step sounds like a good plan to me :+1:

A mistake was made during the release of container v3.3.1-0 -- despite the tag name, it has grocy v3.3.0 inside. In particular this item could help: > Ensure upstream grocy...

Thanks @caseydavenport - I probably should've started this off by filing a suggestion/feature request, and working from there. `yamllint` does barf on the (Helm?) source templates due to some of...

(randomly browsing open issues, and was curious about this one) It looks like the string appears as part of a list of DNS top-level-domains (TLDs), and that it was added...

(ah: I didn't realize that scans run on every git push during pull requests; I'll try to keep the number of commit batches pushed to a reasonable level)