What's coming in Meteor 1.2, and beyond
info.meteor.com
What's coming in Meteor 1.2, and beyond
1–10 of 98 posts
Re: What's coming in Meteor 1.2, and beyond
#2Re: What's coming in Meteor 1.2, and beyond
#3Re: What's coming in Meteor 1.2, and beyond
#4Re: What's coming in Meteor 1.2, and beyond
#5Re: What's coming in Meteor 1.2, and beyond
#6And yet they still tell people to install Meteor by piping to their shell. Incredible. http://curlpipesh.tumblr.com/ https://paragonie.com/files/blog/pipeshell.jpg
Re: What's coming in Meteor 1.2, and beyond
#7And yet they still tell people to install Meteor by piping to their shell. Incredible. http://curlpipesh.tumblr.com/ https://paragonie.com/files/blog/pipeshell.jpg
That's a pretty common thing. I don't see the problem.
Worse: the people who are most likely to curl|sh are DevOps folks with the keys to their company's kingdom.
Re: What's coming in Meteor 1.2, and beyond
#8An example file of code for the records overview (dashboard was a bit tabby-spacey): https://github.com/liamzebedee/metric/blob/master/client/fea...
Re: What's coming in Meteor 1.2, and beyond
#9And yet they still tell people to install Meteor by piping to their shell. Incredible. http://curlpipesh.tumblr.com/ https://paragonie.com/files/blog/pipeshell.jpg
That's a pretty common thing. I don't see the problem.
Re: What's coming in Meteor 1.2, and beyond
#10Earlier quoted context omitted.
That's a pretty common thing. I don't see the problem.
Hack their webserver, replace the contents of https://install.meteor.com/ with malware, instantly pwn anyone who pipes that to their shell. Worse: the people who are most likely to curl|sh are DevOps folks with the keys to their company's kingdom.
It's convenient and that does not mean it's a good practice but i doubt using an other method would minimize a risk when the meteor.com would actually get owned.