▲ | gchamonlive 4 days ago | |
It's fine, but it wouldn't hurt to have a more formal alias like `docker push-over-ssh`. EDIT: why I think it's important because on automations that are developed collaboratively, "pussh" could be seen as a typo by someone unfamiliar with the feature and cause unnecessary confusion, whereas "push-over-ssh" is clearly deliberate. Think of them maybe as short-hand/full flags. | ||
▲ | psviderski 4 days ago | parent | next [-] | |
That's a valid concern. You can very easily give it whatever name you like. Docker looks for `docker-COMAND` executables in ~/.docker/cli-plugins directory making COMMAND a `docker` subcommand. Rename the file to whatever you like, e.g. to get `docker pushoverssh`:
Note that Docker doesn't allow dashes in plugin commands. | ||
▲ | whalesalad 3 days ago | parent | prev [-] | |
can easily see an engineer spotting pussh in a ci/cd workflow or something and thinking "this is a mistake" and changing it. |