You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Secrets should never be committed to your Git Repositories.
Instead either
use secret files and bind/mount them to a specifc directory/destination inside the doco-cd container so you can access them in your deployments: https://docs.docker.com/compose/use-secrets/
Maybe also add support for SOPS to the app so that sensitive data can be stored encrypted directly in the Git Repo? Since SOPS is also written in Go, the package could easily be integrated in the app.
The text was updated successfully, but these errors were encountered:
I think it would be cool to be able to assign secrets using the tool - I currently push docker secrets to the server using terraform (they’re generated there) and it would be nice to read them out using this tool to avoid having to mess around with the images themselves - not sure how this would work though, what was your idea for the second option?
Secrets should never be committed to your Git Repositories.
Instead either
Maybe also add support for SOPS to the app so that sensitive data can be stored encrypted directly in the Git Repo? Since SOPS is also written in Go, the package could easily be integrated in the app.
The text was updated successfully, but these errors were encountered: