4 ms·
As soon as I saw the title I anticipated the Dropbox conversation! I’m guessing people like me who use the shell as a means to an end. Honestly most of the tim
by quickthrower2 5y ago
As soon as I saw the title I anticipated the Dropbox conversation!
I’m guessing people like me who use the shell as a means to an end. Honestly most of the time I’m using git bash “coz it’s there” and hate typing in commands. I actively avoid it. I installed LENS for kubernetes to avoid it.
I’d rather write a script in an IDE and run that than be working at the command line. Because then I can treat it like code, review before running and it’s repeatable.
I really get the benefits of this tool but I won’t use it because I prefer to avoid excessive command line use - preferring GUI and scripts BUT I do get why it is useful if I have to do interactive command line sessions
- mschrage 5y agoOut of curiosity, do the scripts you write take options or arguments? Or are they generally just invoked directly?
- quickthrower2 5y agoSometimes arguments and sometimes not. Often the argument is simply test vs prod. So I can run it on my machine but also run it from Travis ci. Any connections or secrets would be in the environment. For local I’d create another script to set them up and call the first script. Why? So the secrets don’t end up in the repo by mistake.