-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Separat file for clisync credentials #97
Comments
Why don't you use ssh keys for logging into the remote server? |
I do use SSH keys for authentication. It's the database credentials which I'm talking about. |
Just put em into the .my.cnf file ;-) |
@kitzberger Are there already any possibilities to save db credentials for clisync.yml not in the file direct? If yes, could you tell me how you're doing this? We should add those information to our documentation |
@josefglatz, since the user we're using to log onto the remote machine has got read access to the DB credentials in most cases anyway (for e.g. TYPO3 they're within LocalConfiguration.php), we'll simply put the DB credentials in the remote users home dir into the file .my.cnf:
mysqldump does not like the Other db settings are possible, see http://dev.mysql.com/doc/refman/5.7/en/option-files.html for further information. |
I really love the
ct sync
script! We always try to NOT save credentials in our Git repositories for security reasons. So it a would be great if it would be possible to store credentials in a separat file (e.g.clisync-credentials.yml
) and put this file in the.gitignore
The text was updated successfully, but these errors were encountered: