0
Good morning,
I have 1 project, which is in development and I am using github in the development phase. However configuration files that have password, I n mando pro github haha.
Qnd I do the last commit and then deploy to the application server will the config files with password and everything +.
If I want to make a new implementation and need to use github again, this last commit with the config files with password and everything + will go along with the next push on github.
What would be the best practice in this situation? Why does the commit that was specifically made for deploy not go to github and expose passwords and so on.
I believe that has already been answered here on the site, it would be nice if someone found the link. In addition to the ignore option for certain files, the very network that maintains Sopt has a solution that encrypts certain files of its choice, and this solution is available on github
– Bacco
https://github.com/StackExchange/blackbox
– Bacco