2 ms·
> I wonder why there is such a focus on this `curl|bash` pattern. Because it's easy to understand, it's a cheap way to look smart on the Internet by bashing pe
by carlhjerpe 6y ago
> I wonder why there is such a focus on this `curl|bash` pattern.
Because it's easy to understand, it's a cheap way to look smart on the Internet by bashing people. Also on a lot of servers people might only run ditro packaged packages. More eyes has gone though them so ops people would bash someone for curl | bash on their servers while it's perfectly "acceptable" on client machines.
- Uehreka 6y agoThis is the answer. It’s the “never use inline styles” of ops: A rule that was once taught for good reasons, and is easy for people who know little else to call out and enforce. Never mind that times have changed and the reasoning that caused people to create these rules in the first place no longer makes sense.
- lock-free 6y agoI have put several curl|bash things into production and it's done because it's the only way to run installers that work on everything but windows without having to maintain a .deb, .rpm, and brew formula or something. Often I'll write something like: here's the install steps, or just enter this curl|bash line into your terminal. Guess which users prefer. People who care can download the script first and/or run it as a different user or in a vm. It's not that scary.
- ossusermivami 6y agoi like it, can you make them available ?