Re: [nodejs] npm package mutability

Gemnasium can alert you when your npm dependencies are not up-to-date: https://gemnasium.com On Mon, Dec 30, 2013 at 4:11 PM, Mark Hahn wrote: > > You have to remember to check for updates on some schedule > > It would be nice to have a "watch" feature that would email you about > updates and

Re: [nodejs] npm package mutability

> You have to remember to check for updates on some schedule It would be nice to have a "watch" feature that would email you about updates and even tell you when the contents of an existing version change. This would go a long way to all the concerns on this thread. In other words allow mutabil

Re: [nodejs] npm not running on CentOS

I see that now. Thank you Reza On Monday, December 30, 2013 2:38:58 PM UTC-8, T.C. Hollingsworth wrote: > > On Dec 30, 2013 3:05 PM, "Reza Razavipour" > > > wrote: > > > > I am trying to install node on ` > > > > CentOS 2.6.31.11-an_centos6-v42 #3 SMP Thu Oct 31 12:17:24 PDT 2013 > i686 i6

Re: [nodejs] npm not running on CentOS

I see that, thank you Regards, Reza On Mon, Dec 30, 2013 at 2:38 PM, T.C. Hollingsworth < tchollingswo...@gmail.com> wrote: > On Dec 30, 2013 3:05 PM, "Reza Razavipour" > wrote: > > > > I am trying to install node on ` > > > > CentOS 2.6.31.11-an_centos6-v42 #3 SMP Thu Oct 31 12:17:24 PDT

Re: [nodejs] npm not running on CentOS

On Dec 30, 2013 3:05 PM, "Reza Razavipour" wrote: > > I am trying to install node on ` > > CentOS 2.6.31.11-an_centos6-v42 #3 SMP Thu Oct 31 12:17:24 PDT 2013 i686 i686 i386 GNU/Linux > > I download the tar file from nodejs.org. > > tar -xf node-v0.10.23.tar.gz > cd node-v0.10.23 >

[nodejs] npm not running on CentOS

I am trying to install node on ` CentOS 2.6.31.11-an_centos6-v42 #3 SMP Thu Oct 31 12:17:24 PDT 2013 i686 i686 i386 GNU/Linux I download the tar file from nodejs.org. tar -xf node-v0.10.23.tar.gz cd node-v0.10.23 ./configure make I see node in node-v0.10.23/node pointing t

Re: [nodejs] npm package mutability

For what it does and what it was designed for, the current NPM central repository system works great. It wasn't meant to be a secure system with evil actors that can't trust eachother, but must work together. It does at least have basic authentication so that an author has to change evil after pu

[nodejs] Re: we need a new mongodb driver for node

Also had problems with verbosity of mongodb-native driver and created simplified version http://alexeypetrushin.github.io/mongo-lite My reasons for creating it was - in most of the cases I usually need only about 20% of functionality of MongoDB and don't need rest of it, so, I tried to make tho

[nodejs] Re: we need a new mongodb driver for node

Can you please link to your project? Possibly we can add this behavior to the existing node-mongodb-native driver? It has to support database failovers and connection failures already, so it shouldn't be hard to implement a new connect() function around this functionality. I really like

[nodejs] node server and keeping remote connections alive

I have a node server that needs to communicate with a single remote SOAP server. I establish this connection and reuse it throughout the run. Except this server is not very reliable and crashes some time :( So at some point during the run, I make a call and I get socket connection error. What

Re: [nodejs] npm package mutability

Em 30-12-2013 14:10, Mark Hahn escreveu: > and people start to depend on it, it should be hard to remove it. Are you referring to some central authority you would have to petition to be allowed to remove? I can't imagine any other process that could be implemented to stop me from removing my

Re: [nodejs] npm package mutability

> and people start to depend on it, it should be hard to remove it. Are you referring to some central authority you would have to petition to be allowed to remove? I can't imagine any other process that could be implemented to stop me from removing my module. In other words a computer can't mak

[nodejs] Re: Good way to store passwords server-side for node apps

Hello, exposing the code on Github would be disastrous. I've seen both well-known clients and people I personally know make this error. Here are the recommendations I give to avoid this potential: 1. Yes, please add config.yaml (or however you choose to store config) to your gitignore. 2. *Impo

Re: [nodejs] we need a new mongodb driver for node

One of the problem I had with the native driver over and over was that you should keep the db instance somewhere, but it is returned asynchronous from the connect method. So, you have to make sure that you call connect only once and you keep that instance somewhere. I didn't like this API so using

Re: [nodejs] we need a new mongodb driver for node

 Apart from a (solvable) callback hell, node-mongodb-native is a good and easy to use driver. I see no need to write a new one whatsoever. If you want a wrapper to reduce callbacks, "mongode" will do the job just fine (while being a really thin wrapper so you don't even notice it at times).  30.12.

[nodejs] Node.js Half Day Workshop in Norwich (UK) Wanted

Hi All I run a tech community group in Norwich (UK) called Norfolk Developers: http://norfolkdevelopers.com Every quarter we run a half day hands on workshop. I'd like the next one to be a hands on introduction to Node.js in March. I'm afraid I don't know anyone in the Node community who could

[nodejs] we need a new mongodb driver for node

node-mongodb-native is the most popular node mongodb driver. But it is not easy to use. I think a mongodb driver should exports the db instance and collection instance synchronized or promised. So I wrote mongoskin, a wrapper layer of node-mongodb-native. But I personally don't like mon

Re: [nodejs] Re: node.js for server-side ?

+1 On Monday, December 30, 2013 8:02:43 AM UTC-5, José F. Romaniello wrote: > > Hello, I'm trying to build a nuclear reactor to power 1000 cities. Does > uranium-235 generates enough heat? > > > 2013/12/30 Alexey Petrushin > > >> > if i have 1 concurrent users >> >> If you'll have 1 concu

[nodejs] Re: Node app causing Core Dump

Hello, Upgrade your node there were a bugthat have been fixed since 0.11.8 On Wednesday, 11 December 2013 14:33:17 UTC, Frankie Nwafili wrote: > > Hello. I’m trying to run the PUT example on the Knox github page [ > https://github.com/LearnBoos

[nodejs] How to timeout a fs.read? Closing a file-descriptor does not cancel fs.read

Hi, I want to read from a file and want to timeout if there is no data. How can I cancel the fs.read, closing the file-descriptor doesn't work. Is it a bug? Here is a example: You have to create a fifo: "mkfifo file" var fs=require('fs'); fs.open('file', 'r+', function(err,fd) { console.log

Re: [nodejs] Re: node.js for server-side ?

Hello, I'm trying to build a nuclear reactor to power 1000 cities. Does uranium-235 generates enough heat? 2013/12/30 Alexey Petrushin > > if i have 1 concurrent users > > If you'll have 1 concurrent users on a payment gateway you will > have enough money to hire developers that will so

[nodejs] Re: node.js for server-side ?

> if i have 1 concurrent users If you'll have 1 concurrent users on a payment gateway you will have enough money to hire developers that will solve any problem no matter is it node.js, php or even cobol :) On Sunday, 29 December 2013 12:44:32 UTC+4, Raf Roger wrote: > > Hi, > > i'm new

Re: [nodejs] npm package mutability

> i'm not disagreeing with you but when you say things like "change in behavior" you're sort > of sugar coating the fact that packages will fail to install at a greater rate than they do now. I think the core problem there isn't that removing force-republish would encourage greater use of unpublis