[jotaen]

Great suggestions, I’d agree with all points!

> 6. Change "We do not store your credentials. Tasks are done in your browser" to "No data is saved. View source on GitHub."

Assuming that OP has made it clearer that this website is a CLI command builder and not a dumping tool, I’d find “No data is saved” potentially confusing. To me, it would be unclear whether “data” refers to the credentials or to the underlying database data. It might also raise the concern why a command builder utility would entertain the idea of storing anything in the first place.

Maybe “Your credentials won’t leave your computer” or so?

[ChristianGeek]

I would solve this by not asking for the password and just putting a password placeholder in the generated command.

[jotaen]

That could also be an option, although an additional manual step might be slightly less convenient, especially in case you want to “debug” the command (i.e., regenerate multiple times with varying parameters).

Another potential benefit of entering the PW in the field is that the generator could take care of proper escaping – think, if the password contains spaces, quotes, asterisks, $ signs, or other bash shenanigans. (That, by the way, doesn’t seem to work right now, @OP.)

Another idea could be to allow entering an env variable name instead of a value.

[phil21]

If you are on a dev machine iterating quickly, just set the basic credentials up in ~/.mylogin.cnf[0] and you don't need to worry about supplying those options on the command line at all.

[0]: https://dev.mysql.com/doc/refman/8.0/en/mysql-config-editor....