wardethan2000-eng locks down deployment secrets
A small deployment change reduces the chance that live credentials end up in a public code repository.
The fork stops a local deployment configuration containing real sign-in and file-storage credentials from being tracked in version control. It replaces that setup with an example configuration, so teams have a clearer starting point without exposing production access.
It also tidies the container build process so the public-facing application can reliably use shared information from the wider product. The example still needs proper environment-variable handling before it should be treated as a production-ready template.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?