curl: (48) An unknown option was passed in to libcurl
Just had this exact issue with Alpine Linux. The fix was to install curl-dev in addition to curl.
Just had this exact issue with Alpine Linux. The fix was to install curl-dev in addition to curl.
I had the same problem. Fixed with: WARNING: This erases your local database: meteor reset
While we’re waiting for the official tools to have this functionality, here’s the uglyslow vershion: for p in `meteor list | grep ‘^[a-z]’ | awk ‘{ print $1″@”$2 }’`; do echo “$p”; meteor show “$p” | grep -E ‘^ [a-z]’; echo; done This will show the dependencies of all added packages. It parses the output … Read more
You can set a deploy password for your app. $ meteor deploy -P spartan.meteor.com Any future deploy (or request for logs) will require the same password.
Users are special objects in meteor ; you don’t want to add fields in the user but in the users profile. From the doc : By default the server publishes username, emails, and profile. If you want to add properties like surname when you create the account, you should use in the Account.onCreateUser server-side hook … Read more
A hacky way to do it is: foo.html <template name=”mytemplate”> <div id=”my-magic-div”> .. stuff goes here .. {{add_my_special_behavior}} </div> </template> foo.js Template.mytemplate.add_my_special_behavior = function () { Meteor.defer(function () { // find #my-magic-div in the DOM // do stuff to it }); // return nothing }; The function will get called whenever the template is rendered … Read more
may be you can try this, it works for me on linux(centOS), puppeteer(10.2.0). cd ./node_modules/puppeteer npm run install If that fails, you can also try running: cd ./node_modules/puppeteer npm install This will download the chromium to ./node_modules/puppeteer/.local-chromium
Could you not just use the same query client-side when you want to look at the items? In a lib directory: enabledItems = function() { return Items.find({enabled: true}); } processedItems = function() { return Items.find({processed: true}); } On the server: Meteor.publish(‘enabled_items’, function() { return enabledItems(); }); Meteor.publish(‘processed_items’, function() { return processedItems(); }); On the client … Read more
Figured it out through trial and error: Values.upsert({ // Selector source: “SourceOne”, currency: “USD” }, { // Modifier $set: { value: res.data[‘data’][‘last’][‘value’], time: Date.now() // no comma needed here } });
You have to use Meteor.user() in a place where a request is made from the client (such as a Meteor.methods or a Meteor.publish). It can’t be placed anywhere else because meteor wouldn’t know at that point in the code the user is supposed to bound to. If there is a place a request of some … Read more