Re: [nodejs] Running multiple instances of node.js servers on different ports

[Tim Caswell]

I'm not sure it's what you want, but yes, a single node process can listen
on any number of ports.

You can even have the same exact request handler function service all those
ports.

var http = require('http');
http.createServer(onRequest).listen(3000);
http.createServer(onRequest).listen(3001);

function on request(req, res) { ... }
On Feb 10, 2014 12:48 PM, "Arman Didandeh"  wrote:

> Dear all,
>
> I am a newbie when it comes to node.js, so I need your help towards
> running multiple instances of my node.js server on my machine.
>
> I do not want to use other tools that manage this and prefer to do the
> confing to learn more.
>
> Also  I do not need to assign each of these instances to a core (as I have
> seen is very popular in discussion forums).
>
> All I need is for my local machine (which is acting as the server during
> the development phase), to be able to listen to different ports. This way
> myself and other developers can test their changes in code through these
> connections and once everything is stable, each person could commit to our
> git repo. Also the same machine is working as the actual server for current
> users so it is probably using port 80.
>
> Thanks in advance for your helps.
>
> Cheers all,
> Arman
>
> --
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "nodejs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to nodejs+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [nodejs] Running multiple instances of node.js servers on different ports

[Mark Hahn]

Assuming each developer has shell access to the server they could each run
node from their github directory in their home directory.  You could have a
config file in each home directory that just contains the port number
assigned to them.  Then the node server code would read that file when it
starts to know what port to use.


On Mon, Feb 10, 2014 at 2:47 PM, Arman Didandeh wrote:

> I still think that your suggestion might work properly.
> Do you have instructions on how to do that?
>
>
> On 10 February 2014 17:43, Mark Hahn  wrote:
>
>> Then may I propose my original response again?  Just run a bunch of
>> different node instances on the server, one for each developer with a
>> different port on each.  I guess i'm not capable of understanding the
>> problem.  Sorry.
>>
>>
>> On Mon, Feb 10, 2014 at 12:47 PM, Arman Didandeh <
>> arman.didan...@gmail.com> wrote:
>>
>>> There is one stable version of code on the server, runing on 80.
>>>
>>> The same code is on multiple machines as the base code for further
>>> development. Hence testing the new components need the server. This service
>>> can come from each machine, on each a node.js server running. This is not a
>>> choice for me now.
>>>
>>> Another is for each one of those under development codes to be served on
>>> the server, each on a specific port.
>>>
>>> Since codes are in javascript plus sone python/R, I have both client and
>>> server side codes.
>>> On Feb 10, 2014 3:41 PM, "Mark Hahn"  wrote:
>>>
 >  each user is a developer who is trying to run his specific version
 of the code, locating on his machine.

 This custom code, is it a server or a client?  If it is server code
 then are you asking for the user's machine to accept requests on multiple
 ports?

 We are going in circles with this discussion.  Can you give more
 details about the nature of the code?  What code is running on each
 machine, including any central server.  What does the code do?



 On Mon, Feb 10, 2014 at 12:33 PM, Arman Didandeh <
 arman.didan...@gmail.com> wrote:

> Cause as I said, each user is a developer who is trying to run his
> specific veraion of the code, locating on his machine.
>
> Not sure if it makes any sense? As I said, since I am newbie, I might
> ask silly questions.
> On Feb 10, 2014 3:29 PM, "Mark Hahn"  wrote:
>
>> I may be oversimplifying your request but if you mean can one node
>> executable take http requests from multiple ports then the answer is yes,
>> if you use a reverse proxy.  You could set up nginx to accept requests on
>> different ports and proxy them all to one node server.  There might be an
>> easier way that I can't think of right now.
>>
>> I'm confused as to why this would be useful.  Why can't your users
>> all go to one port?  There will be absolutely no difference at the http
>> level.
>>
>>
>>
>> On Mon, Feb 10, 2014 at 12:02 PM, Arman Didandeh <
>> arman.didan...@gmail.com> wrote:
>>
>>> My bad.
>>>
>>> Right now I have connections to db for each developer on the same
>>> server, so everyone can connect. However there is only one db instance.
>>>
>>> What I am saying is that is there a way to do the same for the
>>> application server? So users can get served by the same server but on
>>> different ports. Is it even possible?
>>> On Feb 10, 2014 2:58 PM, "Mark Hahn"  wrote:
>>>
 I'm sorry but I'm getting lost at this sentence ...

 > I trying to deploy a similar connection for the DB over the
 network

 You haven't mentioned a DB before.  A node server is a very
 different thing than a DB server.

 Maybe someone else can understand better?  I might not be thinking
 straight today.



 On Mon, Feb 10, 2014 at 11:27 AM, Arman Didandeh <
 arman.didan...@gmail.com> wrote:

> Let me describe the situation a bit more.
>
> So what I have right now is a repo, the code for which has been
> written by someone else. Now I have myself and other developers who 
> cloned
> the code on our machines to extend it.
>
> Since each developer is working on different modules, I do not
> want us to commit or branch on the repo and have the repo run on my 
> server.
> In fact, I want a separate stable thing to run, and I was planning 
> for each
> developer to run and test their added codes on their own machines. 
> However
> some machines are down in RAM, so I trying to deploy a similar 
> connection
> for the DB over the network (with different users and even possibly
> different DB clones), but this time on different ports.
>
> If this is what you pointed out, could you plea

Re: [nodejs] Running multiple instances of node.js servers on different ports

[Arman Didandeh]

I still think that your suggestion might work properly.
Do you have instructions on how to do that?


On 10 February 2014 17:43, Mark Hahn  wrote:

> Then may I propose my original response again?  Just run a bunch of
> different node instances on the server, one for each developer with a
> different port on each.  I guess i'm not capable of understanding the
> problem.  Sorry.
>
>
> On Mon, Feb 10, 2014 at 12:47 PM, Arman Didandeh  > wrote:
>
>> There is one stable version of code on the server, runing on 80.
>>
>> The same code is on multiple machines as the base code for further
>> development. Hence testing the new components need the server. This service
>> can come from each machine, on each a node.js server running. This is not a
>> choice for me now.
>>
>> Another is for each one of those under development codes to be served on
>> the server, each on a specific port.
>>
>> Since codes are in javascript plus sone python/R, I have both client and
>> server side codes.
>> On Feb 10, 2014 3:41 PM, "Mark Hahn"  wrote:
>>
>>> >  each user is a developer who is trying to run his specific version
>>> of the code, locating on his machine.
>>>
>>> This custom code, is it a server or a client?  If it is server code then
>>> are you asking for the user's machine to accept requests on multiple ports?
>>>
>>> We are going in circles with this discussion.  Can you give more details
>>> about the nature of the code?  What code is running on each machine,
>>> including any central server.  What does the code do?
>>>
>>>
>>>
>>> On Mon, Feb 10, 2014 at 12:33 PM, Arman Didandeh <
>>> arman.didan...@gmail.com> wrote:
>>>
 Cause as I said, each user is a developer who is trying to run his
 specific veraion of the code, locating on his machine.

 Not sure if it makes any sense? As I said, since I am newbie, I might
 ask silly questions.
 On Feb 10, 2014 3:29 PM, "Mark Hahn"  wrote:

> I may be oversimplifying your request but if you mean can one node
> executable take http requests from multiple ports then the answer is yes,
> if you use a reverse proxy.  You could set up nginx to accept requests on
> different ports and proxy them all to one node server.  There might be an
> easier way that I can't think of right now.
>
> I'm confused as to why this would be useful.  Why can't your users all
> go to one port?  There will be absolutely no difference at the http level.
>
>
>
> On Mon, Feb 10, 2014 at 12:02 PM, Arman Didandeh <
> arman.didan...@gmail.com> wrote:
>
>> My bad.
>>
>> Right now I have connections to db for each developer on the same
>> server, so everyone can connect. However there is only one db instance.
>>
>> What I am saying is that is there a way to do the same for the
>> application server? So users can get served by the same server but on
>> different ports. Is it even possible?
>> On Feb 10, 2014 2:58 PM, "Mark Hahn"  wrote:
>>
>>> I'm sorry but I'm getting lost at this sentence ...
>>>
>>> > I trying to deploy a similar connection for the DB over the
>>> network
>>>
>>> You haven't mentioned a DB before.  A node server is a very
>>> different thing than a DB server.
>>>
>>> Maybe someone else can understand better?  I might not be thinking
>>> straight today.
>>>
>>>
>>>
>>> On Mon, Feb 10, 2014 at 11:27 AM, Arman Didandeh <
>>> arman.didan...@gmail.com> wrote:
>>>
 Let me describe the situation a bit more.

 So what I have right now is a repo, the code for which has been
 written by someone else. Now I have myself and other developers who 
 cloned
 the code on our machines to extend it.

 Since each developer is working on different modules, I do not want
 us to commit or branch on the repo and have the repo run on my server. 
 In
 fact, I want a separate stable thing to run, and I was planning for 
 each
 developer to run and test their added codes on their own machines. 
 However
 some machines are down in RAM, so I trying to deploy a similar 
 connection
 for the DB over the network (with different users and even possibly
 different DB clones), but this time on different ports.

 If this is what you pointed out, could you please forward me to
 some instruction, as I am not very good at these things YET!

 Cheers


 On 10 February 2014 14:21, Mark Hahn  wrote:

> Interesting question.  One would think than you could put the http
> server example in the code multiple times with a different variable 
> for
> each httpserver.  I don't see any reason why that wouldn't work.  
> Should
> only take a few minutes to try it.
>
>
> On Mon,

Re: [nodejs] Running multiple instances of node.js servers on different ports

[Mark Hahn]

Then may I propose my original response again?  Just run a bunch of
different node instances on the server, one for each developer with a
different port on each.  I guess i'm not capable of understanding the
problem.  Sorry.


On Mon, Feb 10, 2014 at 12:47 PM, Arman Didandeh
wrote:

> There is one stable version of code on the server, runing on 80.
>
> The same code is on multiple machines as the base code for further
> development. Hence testing the new components need the server. This service
> can come from each machine, on each a node.js server running. This is not a
> choice for me now.
>
> Another is for each one of those under development codes to be served on
> the server, each on a specific port.
>
> Since codes are in javascript plus sone python/R, I have both client and
> server side codes.
> On Feb 10, 2014 3:41 PM, "Mark Hahn"  wrote:
>
>> >  each user is a developer who is trying to run his specific version of
>> the code, locating on his machine.
>>
>> This custom code, is it a server or a client?  If it is server code then
>> are you asking for the user's machine to accept requests on multiple ports?
>>
>> We are going in circles with this discussion.  Can you give more details
>> about the nature of the code?  What code is running on each machine,
>> including any central server.  What does the code do?
>>
>>
>>
>> On Mon, Feb 10, 2014 at 12:33 PM, Arman Didandeh <
>> arman.didan...@gmail.com> wrote:
>>
>>> Cause as I said, each user is a developer who is trying to run his
>>> specific veraion of the code, locating on his machine.
>>>
>>> Not sure if it makes any sense? As I said, since I am newbie, I might
>>> ask silly questions.
>>> On Feb 10, 2014 3:29 PM, "Mark Hahn"  wrote:
>>>
 I may be oversimplifying your request but if you mean can one node
 executable take http requests from multiple ports then the answer is yes,
 if you use a reverse proxy.  You could set up nginx to accept requests on
 different ports and proxy them all to one node server.  There might be an
 easier way that I can't think of right now.

 I'm confused as to why this would be useful.  Why can't your users all
 go to one port?  There will be absolutely no difference at the http level.



 On Mon, Feb 10, 2014 at 12:02 PM, Arman Didandeh <
 arman.didan...@gmail.com> wrote:

> My bad.
>
> Right now I have connections to db for each developer on the same
> server, so everyone can connect. However there is only one db instance.
>
> What I am saying is that is there a way to do the same for the
> application server? So users can get served by the same server but on
> different ports. Is it even possible?
> On Feb 10, 2014 2:58 PM, "Mark Hahn"  wrote:
>
>> I'm sorry but I'm getting lost at this sentence ...
>>
>> > I trying to deploy a similar connection for the DB over the network
>>
>>
>> You haven't mentioned a DB before.  A node server is a very different
>> thing than a DB server.
>>
>> Maybe someone else can understand better?  I might not be thinking
>> straight today.
>>
>>
>>
>> On Mon, Feb 10, 2014 at 11:27 AM, Arman Didandeh <
>> arman.didan...@gmail.com> wrote:
>>
>>> Let me describe the situation a bit more.
>>>
>>> So what I have right now is a repo, the code for which has been
>>> written by someone else. Now I have myself and other developers who 
>>> cloned
>>> the code on our machines to extend it.
>>>
>>> Since each developer is working on different modules, I do not want
>>> us to commit or branch on the repo and have the repo run on my server. 
>>> In
>>> fact, I want a separate stable thing to run, and I was planning for each
>>> developer to run and test their added codes on their own machines. 
>>> However
>>> some machines are down in RAM, so I trying to deploy a similar 
>>> connection
>>> for the DB over the network (with different users and even possibly
>>> different DB clones), but this time on different ports.
>>>
>>> If this is what you pointed out, could you please forward me to some
>>> instruction, as I am not very good at these things YET!
>>>
>>> Cheers
>>>
>>>
>>> On 10 February 2014 14:21, Mark Hahn  wrote:
>>>
 Interesting question.  One would think than you could put the http
 server example in the code multiple times with a different variable for
 each httpserver.  I don't see any reason why that wouldn't work.  
 Should
 only take a few minutes to try it.


 On Mon, Feb 10, 2014 at 11:00 AM, Arman Didandeh <
 arman.didan...@gmail.com> wrote:

> So there is no way to run one executable that listens to different
> ports?
>
>
> On 10 February 2014 13:58, Mark Hahn  wrote:
>
>> It should 

Re: [nodejs] Running multiple instances of node.js servers on different ports

[Arman Didandeh]

There is one stable version of code on the server, runing on 80.

The same code is on multiple machines as the base code for further
development. Hence testing the new components need the server. This service
can come from each machine, on each a node.js server running. This is not a
choice for me now.

Another is for each one of those under development codes to be served on
the server, each on a specific port.

Since codes are in javascript plus sone python/R, I have both client and
server side codes.
On Feb 10, 2014 3:41 PM, "Mark Hahn"  wrote:

> >  each user is a developer who is trying to run his specific version of
> the code, locating on his machine.
>
> This custom code, is it a server or a client?  If it is server code then
> are you asking for the user's machine to accept requests on multiple ports?
>
> We are going in circles with this discussion.  Can you give more details
> about the nature of the code?  What code is running on each machine,
> including any central server.  What does the code do?
>
>
>
> On Mon, Feb 10, 2014 at 12:33 PM, Arman Didandeh  > wrote:
>
>> Cause as I said, each user is a developer who is trying to run his
>> specific veraion of the code, locating on his machine.
>>
>> Not sure if it makes any sense? As I said, since I am newbie, I might ask
>> silly questions.
>> On Feb 10, 2014 3:29 PM, "Mark Hahn"  wrote:
>>
>>> I may be oversimplifying your request but if you mean can one node
>>> executable take http requests from multiple ports then the answer is yes,
>>> if you use a reverse proxy.  You could set up nginx to accept requests on
>>> different ports and proxy them all to one node server.  There might be an
>>> easier way that I can't think of right now.
>>>
>>> I'm confused as to why this would be useful.  Why can't your users all
>>> go to one port?  There will be absolutely no difference at the http level.
>>>
>>>
>>>
>>> On Mon, Feb 10, 2014 at 12:02 PM, Arman Didandeh <
>>> arman.didan...@gmail.com> wrote:
>>>
 My bad.

 Right now I have connections to db for each developer on the same
 server, so everyone can connect. However there is only one db instance.

 What I am saying is that is there a way to do the same for the
 application server? So users can get served by the same server but on
 different ports. Is it even possible?
 On Feb 10, 2014 2:58 PM, "Mark Hahn"  wrote:

> I'm sorry but I'm getting lost at this sentence ...
>
> > I trying to deploy a similar connection for the DB over the network
>
> You haven't mentioned a DB before.  A node server is a very different
> thing than a DB server.
>
> Maybe someone else can understand better?  I might not be thinking
> straight today.
>
>
>
> On Mon, Feb 10, 2014 at 11:27 AM, Arman Didandeh <
> arman.didan...@gmail.com> wrote:
>
>> Let me describe the situation a bit more.
>>
>> So what I have right now is a repo, the code for which has been
>> written by someone else. Now I have myself and other developers who 
>> cloned
>> the code on our machines to extend it.
>>
>> Since each developer is working on different modules, I do not want
>> us to commit or branch on the repo and have the repo run on my server. In
>> fact, I want a separate stable thing to run, and I was planning for each
>> developer to run and test their added codes on their own machines. 
>> However
>> some machines are down in RAM, so I trying to deploy a similar connection
>> for the DB over the network (with different users and even possibly
>> different DB clones), but this time on different ports.
>>
>> If this is what you pointed out, could you please forward me to some
>> instruction, as I am not very good at these things YET!
>>
>> Cheers
>>
>>
>> On 10 February 2014 14:21, Mark Hahn  wrote:
>>
>>> Interesting question.  One would think than you could put the http
>>> server example in the code multiple times with a different variable for
>>> each httpserver.  I don't see any reason why that wouldn't work.  Should
>>> only take a few minutes to try it.
>>>
>>>
>>> On Mon, Feb 10, 2014 at 11:00 AM, Arman Didandeh <
>>> arman.didan...@gmail.com> wrote:
>>>
 So there is no way to run one executable that listens to different
 ports?


 On 10 February 2014 13:58, Mark Hahn  wrote:

> It should be as simple as running a different node executable for
> each server.  In other words you'd do
>
> node server1.js
> node server2.js
> node server3.js
>
> where each executable is using a different port.  You might want
> to make the port an argument so you could say `node server.js 8080`.
>
>
> On Mon, Feb 10, 2014 at 10:48 AM, Arman Didandeh <
> arman.didan...@gmail.com

Re: [nodejs] My desk is URDESK (a very good client for node)

[Alan Hoffmeister]

But it have "Powered By Google" and a Chrome logo, what could possible go wrong?
--
Att,
Alan Hoffmeister


2014-02-10 18:30 GMT-02:00 Mark Hahn :
> It is tl;dr for me and there is no way I'm going to a web page and clicking
> on a button called "install me" with no indication of what is being
> installed.
>
>
> On Mon, Feb 10, 2014 at 12:18 PM, Dennis Kane  wrote:
>>
>> (If this is tl;dr, just go to http://urdesk.net right now)
>>
>> What does it mean for something to be "a good node client"?
>>
>> When I think of a client for node.js, I think of a dynamic user experience
>> that doesn't really require any page refreshes, and that stirs up a whole
>> bunch of good feelings as regards what is possible on the web.
>>
>> I started thinking about web programming in the mid-2011 time frame. I
>> wanted to see how far I could push the concept of a dynamic user experience.
>> Fast forward to February 10, 2014 (today), and I think that my original
>> vision has finally come to fruition. Starting in September 2012, I began
>> working on the current incarnation. My idea was to go "all in" by way of
>> seeing if I could duplicate the OS X end user experience inside of a web
>> browser... all courtesy of Google's V8 JS engine running inside of standard
>> Chrome.   Since that time, I've put in about a full year's worth of 8-12
>> hour coding days. Here is the basic setup:
>>
>> There is a core desktop module that performs all of the essential system
>> level operations: window, icon, context menu, menubar, and toolbar GUI
>> operations, as well as all of the interactions with Local Storage and the
>> filesystem API.
>>
>> There are several self-contained modules of which the core has no
>> knowledge that plug into the system through a basic interface.  The most
>> important of these modules are the Unix-style text editor (called Nanim) and
>> the command-line interface.  There are other, graphical modules that I've
>> spent relatively small amounts of time developing, such as a media player
>> and a prototype-phase word processor.
>>
>> There are several ways of thinking about the system.  Most obviously, I
>> think that it pushes the envelope in terms of how we understand the notion
>> of an operating system.  Such a thing has traditionally been written in
>> native code, and has required a fairly sizeable cost to download, install,
>> replace, etc.  (What I mainly mean by "cost" is NOT the purchase price, but
>> rather the potential for catastrophe if the installation procedures are not
>> followed precisely.  So by this definition, we can judge the commercial OSes
>> to be much cheaper that all of the Linux distributions that require one to
>> do things such as partition hard drives and install custom boot loaders to
>> try them out.)
>>
>> We can call the OS that I've developed a trivially loadable/bootable OS.
>> The only investment that it currently requires comes in the form of
>> accepting the browser's "this site wants to permanently store data on your
>> computer" prompt, and then waiting the minute or so for all of the resources
>> to download. After that, everything is served locally, meaning that a
>> network connection is not necessary for it to load. Furthermore, given that
>> all of the locally stored data is essentially namespaced by the domain name,
>> one can have many OS environments running alongside each other in different
>> tabs of the same browser, with the caveat that each tab is must use a
>> different subdomain (this just means that all of the resources owned by
>> www.urdesk.net essentially live in a sandboxe, safely hidden away from, eg.
>> dev.urdesk.net... or any other subdomain of urdesk.net).
>>
>> In this way, there is essentially zero cost involved when it comes to
>> experimenting with a new OS, and trying out all of the different
>> applications contained within it. Application developers will be able to
>> write their logic without having to worry about distribution problems, given
>> that it will be guaranteed to run on any Chrome browser, thereby eliminating
>> all issues related to downloading (and the related issue of viruses),
>> plugin-installing, flag-enabling, etc.
>>
>> The next level of thinking about the system is that the applications are
>> not traditional "applications" in the sense that they run as different
>> native processes, and thereby keep their data structures in mutually
>> exclusive address spaces. In this system, there are precisely zero issues of
>> interprocess communication (IPC). All "applications" are actually just
>> JavaScript function objects that collectively inhabit a single browser tab
>> address space. All complications traditionally related to IPC now become
>> null and void. Given this fact, the possibilities in terms of the
>> development of a holistic kind of user experience increase profoundly. (As a
>> trivial example of this, imagine your calendar app being aware of what you
>> are typing into your word processor and adjusting itself a

Re: [nodejs] Running multiple instances of node.js servers on different ports

[Mark Hahn]

>  each user is a developer who is trying to run his specific version of
the code, locating on his machine.

This custom code, is it a server or a client?  If it is server code then
are you asking for the user's machine to accept requests on multiple ports?

We are going in circles with this discussion.  Can you give more details
about the nature of the code?  What code is running on each machine,
including any central server.  What does the code do?



On Mon, Feb 10, 2014 at 12:33 PM, Arman Didandeh
wrote:

> Cause as I said, each user is a developer who is trying to run his
> specific veraion of the code, locating on his machine.
>
> Not sure if it makes any sense? As I said, since I am newbie, I might ask
> silly questions.
> On Feb 10, 2014 3:29 PM, "Mark Hahn"  wrote:
>
>> I may be oversimplifying your request but if you mean can one node
>> executable take http requests from multiple ports then the answer is yes,
>> if you use a reverse proxy.  You could set up nginx to accept requests on
>> different ports and proxy them all to one node server.  There might be an
>> easier way that I can't think of right now.
>>
>> I'm confused as to why this would be useful.  Why can't your users all go
>> to one port?  There will be absolutely no difference at the http level.
>>
>>
>>
>> On Mon, Feb 10, 2014 at 12:02 PM, Arman Didandeh <
>> arman.didan...@gmail.com> wrote:
>>
>>> My bad.
>>>
>>> Right now I have connections to db for each developer on the same
>>> server, so everyone can connect. However there is only one db instance.
>>>
>>> What I am saying is that is there a way to do the same for the
>>> application server? So users can get served by the same server but on
>>> different ports. Is it even possible?
>>> On Feb 10, 2014 2:58 PM, "Mark Hahn"  wrote:
>>>
 I'm sorry but I'm getting lost at this sentence ...

 > I trying to deploy a similar connection for the DB over the network

 You haven't mentioned a DB before.  A node server is a very different
 thing than a DB server.

 Maybe someone else can understand better?  I might not be thinking
 straight today.



 On Mon, Feb 10, 2014 at 11:27 AM, Arman Didandeh <
 arman.didan...@gmail.com> wrote:

> Let me describe the situation a bit more.
>
> So what I have right now is a repo, the code for which has been
> written by someone else. Now I have myself and other developers who cloned
> the code on our machines to extend it.
>
> Since each developer is working on different modules, I do not want us
> to commit or branch on the repo and have the repo run on my server. In
> fact, I want a separate stable thing to run, and I was planning for each
> developer to run and test their added codes on their own machines. However
> some machines are down in RAM, so I trying to deploy a similar connection
> for the DB over the network (with different users and even possibly
> different DB clones), but this time on different ports.
>
> If this is what you pointed out, could you please forward me to some
> instruction, as I am not very good at these things YET!
>
> Cheers
>
>
> On 10 February 2014 14:21, Mark Hahn  wrote:
>
>> Interesting question.  One would think than you could put the http
>> server example in the code multiple times with a different variable for
>> each httpserver.  I don't see any reason why that wouldn't work.  Should
>> only take a few minutes to try it.
>>
>>
>> On Mon, Feb 10, 2014 at 11:00 AM, Arman Didandeh <
>> arman.didan...@gmail.com> wrote:
>>
>>> So there is no way to run one executable that listens to different
>>> ports?
>>>
>>>
>>> On 10 February 2014 13:58, Mark Hahn  wrote:
>>>
 It should be as simple as running a different node executable for
 each server.  In other words you'd do

 node server1.js
 node server2.js
 node server3.js

 where each executable is using a different port.  You might want to
 make the port an argument so you could say `node server.js 8080`.


 On Mon, Feb 10, 2014 at 10:48 AM, Arman Didandeh <
 arman.didan...@gmail.com> wrote:

> Dear all,
>
> I am a newbie when it comes to node.js, so I need your help
> towards running multiple instances of my node.js server on my machine.
>
> I do not want to use other tools that manage this and prefer to do
> the confing to learn more.
>
> Also  I do not need to assign each of these instances to a core
> (as I have seen is very popular in discussion forums).
>
> All I need is for my local machine (which is acting as the server
> during the development phase), to be able to listen to different 
> ports.
> This way myself and other deve

Re: [nodejs] Running multiple instances of node.js servers on different ports

[Arman Didandeh]

Cause as I said, each user is a developer who is trying to run his specific
veraion of the code, locating on his machine.

Not sure if it makes any sense? As I said, since I am newbie, I might ask
silly questions.
On Feb 10, 2014 3:29 PM, "Mark Hahn"  wrote:

> I may be oversimplifying your request but if you mean can one node
> executable take http requests from multiple ports then the answer is yes,
> if you use a reverse proxy.  You could set up nginx to accept requests on
> different ports and proxy them all to one node server.  There might be an
> easier way that I can't think of right now.
>
> I'm confused as to why this would be useful.  Why can't your users all go
> to one port?  There will be absolutely no difference at the http level.
>
>
>
> On Mon, Feb 10, 2014 at 12:02 PM, Arman Didandeh  > wrote:
>
>> My bad.
>>
>> Right now I have connections to db for each developer on the same server,
>> so everyone can connect. However there is only one db instance.
>>
>> What I am saying is that is there a way to do the same for the
>> application server? So users can get served by the same server but on
>> different ports. Is it even possible?
>> On Feb 10, 2014 2:58 PM, "Mark Hahn"  wrote:
>>
>>> I'm sorry but I'm getting lost at this sentence ...
>>>
>>> > I trying to deploy a similar connection for the DB over the network
>>>
>>> You haven't mentioned a DB before.  A node server is a very different
>>> thing than a DB server.
>>>
>>> Maybe someone else can understand better?  I might not be thinking
>>> straight today.
>>>
>>>
>>>
>>> On Mon, Feb 10, 2014 at 11:27 AM, Arman Didandeh <
>>> arman.didan...@gmail.com> wrote:
>>>
 Let me describe the situation a bit more.

 So what I have right now is a repo, the code for which has been written
 by someone else. Now I have myself and other developers who cloned the code
 on our machines to extend it.

 Since each developer is working on different modules, I do not want us
 to commit or branch on the repo and have the repo run on my server. In
 fact, I want a separate stable thing to run, and I was planning for each
 developer to run and test their added codes on their own machines. However
 some machines are down in RAM, so I trying to deploy a similar connection
 for the DB over the network (with different users and even possibly
 different DB clones), but this time on different ports.

 If this is what you pointed out, could you please forward me to some
 instruction, as I am not very good at these things YET!

 Cheers


 On 10 February 2014 14:21, Mark Hahn  wrote:

> Interesting question.  One would think than you could put the http
> server example in the code multiple times with a different variable for
> each httpserver.  I don't see any reason why that wouldn't work.  Should
> only take a few minutes to try it.
>
>
> On Mon, Feb 10, 2014 at 11:00 AM, Arman Didandeh <
> arman.didan...@gmail.com> wrote:
>
>> So there is no way to run one executable that listens to different
>> ports?
>>
>>
>> On 10 February 2014 13:58, Mark Hahn  wrote:
>>
>>> It should be as simple as running a different node executable for
>>> each server.  In other words you'd do
>>>
>>> node server1.js
>>> node server2.js
>>> node server3.js
>>>
>>> where each executable is using a different port.  You might want to
>>> make the port an argument so you could say `node server.js 8080`.
>>>
>>>
>>> On Mon, Feb 10, 2014 at 10:48 AM, Arman Didandeh <
>>> arman.didan...@gmail.com> wrote:
>>>
 Dear all,

 I am a newbie when it comes to node.js, so I need your help towards
 running multiple instances of my node.js server on my machine.

 I do not want to use other tools that manage this and prefer to do
 the confing to learn more.

 Also  I do not need to assign each of these instances to a core (as
 I have seen is very popular in discussion forums).

 All I need is for my local machine (which is acting as the server
 during the development phase), to be able to listen to different ports.
 This way myself and other developers can test their changes in code 
 through
 these connections and once everything is stable, each person could 
 commit
 to our git repo. Also the same machine is working as the actual server 
 for
 current users so it is probably using port 80.

 Thanks in advance for your helps.

 Cheers all,
 Arman

 --
 --
 Job Board: http://jobs.nodejs.org/
 Posting guidelines:
 https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
 You received this message because you are subscribed to the Google
 Group

Re: [nodejs] My desk is URDESK (a very good client for node)

[Mark Hahn]

It is tl;dr for me and there is no way I'm going to a web page and clicking
on a button called "install me" with no indication of what is being
installed.


On Mon, Feb 10, 2014 at 12:18 PM, Dennis Kane  wrote:

> (If this is tl;dr, just go to http://urdesk.net right now)
>
> What does it mean for something to be "a good node client"?
>
> When I think of a client for node.js, I think of a dynamic user experience
> that doesn't really require any page refreshes, and that stirs up a whole
> bunch of good feelings as regards what is possible on the web.
>
> I started thinking about web programming in the mid-2011 time frame. I
> wanted to see how far I could push the concept of a dynamic user
> experience. Fast forward to February 10, 2014 (today), and I think that my
> original vision has finally come to fruition. Starting in September 2012, I
> began working on the current incarnation. My idea was to go "all in" by way
> of seeing if I could duplicate the OS X end user experience inside of a web
> browser... all courtesy of Google's V8 JS engine running inside of standard
> Chrome.   Since that time, I've put in about a full year's worth of 8-12
> hour coding days. Here is the basic setup:
>
> There is a core desktop module that performs all of the essential system
> level operations: window, icon, context menu, menubar, and toolbar GUI
> operations, as well as all of the interactions with Local Storage and the
> filesystem API.
>
> There are several self-contained modules of which the core has no
> knowledge that plug into the system through a basic interface.  The most
> important of these modules are the Unix-style text editor (called Nanim)
> and the command-line interface.  There are other, graphical modules that
> I've spent relatively small amounts of time developing, such as a media
> player and a prototype-phase word processor.
>
> There are several ways of thinking about the system.  Most obviously, I
> think that it pushes the envelope in terms of how we understand the notion
> of an operating system.  Such a thing has traditionally been written in
> native code, and has required a fairly sizeable cost to download, install,
> replace, etc.  (What I mainly mean by "cost" is NOT the purchase price, but
> rather the potential for catastrophe if the installation procedures are not
> followed precisely.  So by this definition, we can judge the commercial
> OSes to be much cheaper that all of the Linux distributions that require
> one to do things such as partition hard drives and install custom boot
> loaders to try them out.)
>
> We can call the OS that I've developed a trivially loadable/bootable OS.
> The only investment that it currently requires comes in the form of
> accepting the browser's "this site wants to permanently store data on your
> computer" prompt, and then waiting the minute or so for all of the
> resources to download. After that, everything is served locally, meaning
> that a network connection is not necessary for it to load. Furthermore,
> given that all of the locally stored data is essentially namespaced by the
> domain name, one can have many OS environments running alongside each other
> in different tabs of the same browser, with the caveat that each tab is
> must use a different subdomain (this just means that all of the resources
> owned by www.urdesk.net essentially live in a sandboxe, safely hidden
> away from, eg. dev.urdesk.net... or any other subdomain of urdesk.net).
>
> In this way, there is essentially zero cost involved when it comes to
> experimenting with a new OS, and trying out all of the different
> applications contained within it. Application developers will be able to
> write their logic without having to worry about distribution problems,
> given that it will be guaranteed to run on any Chrome browser, thereby
> eliminating all issues related to downloading (and the related issue of
> viruses), plugin-installing, flag-enabling, etc.
>
> The next level of thinking about the system is that the applications are
> not traditional "applications" in the sense that they run as different
> native processes, and thereby keep their data structures in mutually
> exclusive address spaces. In this system, there are precisely zero issues
> of interprocess communication (IPC). All "applications" are actually just
> JavaScript function objects that collectively inhabit a single browser tab
> address space. All complications traditionally related to IPC now become
> null and void. Given this fact, the possibilities in terms of the
> development of a holistic kind of user experience increase profoundly. (As
> a trivial example of this, imagine your calendar app being aware of what
> you are typing into your word processor and adjusting itself according.)
>
> And finally, this system allows for the emergence of a fundamentally new
> paradigm in terms of how we relate to our computers.  I have actually had a
> much longer history developing AI-type command-and-response syst

Re: [nodejs] Running multiple instances of node.js servers on different ports

[Mark Hahn]

I may be oversimplifying your request but if you mean can one node
executable take http requests from multiple ports then the answer is yes,
if you use a reverse proxy.  You could set up nginx to accept requests on
different ports and proxy them all to one node server.  There might be an
easier way that I can't think of right now.

I'm confused as to why this would be useful.  Why can't your users all go
to one port?  There will be absolutely no difference at the http level.



On Mon, Feb 10, 2014 at 12:02 PM, Arman Didandeh
wrote:

> My bad.
>
> Right now I have connections to db for each developer on the same server,
> so everyone can connect. However there is only one db instance.
>
> What I am saying is that is there a way to do the same for the application
> server? So users can get served by the same server but on different ports.
> Is it even possible?
> On Feb 10, 2014 2:58 PM, "Mark Hahn"  wrote:
>
>> I'm sorry but I'm getting lost at this sentence ...
>>
>> > I trying to deploy a similar connection for the DB over the network
>>
>> You haven't mentioned a DB before.  A node server is a very different
>> thing than a DB server.
>>
>> Maybe someone else can understand better?  I might not be thinking
>> straight today.
>>
>>
>>
>> On Mon, Feb 10, 2014 at 11:27 AM, Arman Didandeh <
>> arman.didan...@gmail.com> wrote:
>>
>>> Let me describe the situation a bit more.
>>>
>>> So what I have right now is a repo, the code for which has been written
>>> by someone else. Now I have myself and other developers who cloned the code
>>> on our machines to extend it.
>>>
>>> Since each developer is working on different modules, I do not want us
>>> to commit or branch on the repo and have the repo run on my server. In
>>> fact, I want a separate stable thing to run, and I was planning for each
>>> developer to run and test their added codes on their own machines. However
>>> some machines are down in RAM, so I trying to deploy a similar connection
>>> for the DB over the network (with different users and even possibly
>>> different DB clones), but this time on different ports.
>>>
>>> If this is what you pointed out, could you please forward me to some
>>> instruction, as I am not very good at these things YET!
>>>
>>> Cheers
>>>
>>>
>>> On 10 February 2014 14:21, Mark Hahn  wrote:
>>>
 Interesting question.  One would think than you could put the http
 server example in the code multiple times with a different variable for
 each httpserver.  I don't see any reason why that wouldn't work.  Should
 only take a few minutes to try it.


 On Mon, Feb 10, 2014 at 11:00 AM, Arman Didandeh <
 arman.didan...@gmail.com> wrote:

> So there is no way to run one executable that listens to different
> ports?
>
>
> On 10 February 2014 13:58, Mark Hahn  wrote:
>
>> It should be as simple as running a different node executable for
>> each server.  In other words you'd do
>>
>> node server1.js
>> node server2.js
>> node server3.js
>>
>> where each executable is using a different port.  You might want to
>> make the port an argument so you could say `node server.js 8080`.
>>
>>
>> On Mon, Feb 10, 2014 at 10:48 AM, Arman Didandeh <
>> arman.didan...@gmail.com> wrote:
>>
>>> Dear all,
>>>
>>> I am a newbie when it comes to node.js, so I need your help towards
>>> running multiple instances of my node.js server on my machine.
>>>
>>> I do not want to use other tools that manage this and prefer to do
>>> the confing to learn more.
>>>
>>> Also  I do not need to assign each of these instances to a core (as
>>> I have seen is very popular in discussion forums).
>>>
>>> All I need is for my local machine (which is acting as the server
>>> during the development phase), to be able to listen to different ports.
>>> This way myself and other developers can test their changes in code 
>>> through
>>> these connections and once everything is stable, each person could 
>>> commit
>>> to our git repo. Also the same machine is working as the actual server 
>>> for
>>> current users so it is probably using port 80.
>>>
>>> Thanks in advance for your helps.
>>>
>>> Cheers all,
>>> Arman
>>>
>>> --
>>> --
>>> Job Board: http://jobs.nodejs.org/
>>> Posting guidelines:
>>> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
>>> You received this message because you are subscribed to the Google
>>> Groups "nodejs" group.
>>> To post to this group, send email to nodejs@googlegroups.com
>>> To unsubscribe from this group, send email to
>>> nodejs+unsubscr...@googlegroups.com
>>> For more options, visit this group at
>>> http://groups.google.com/group/nodejs?hl=en?hl=en
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> G

[nodejs] My desk is URDESK (a very good client for node)

[Dennis Kane]

(If this is tl;dr, just go to http://urdesk.net right now)

What does it mean for something to be "a good node client"?

When I think of a client for node.js, I think of a dynamic user experience 
that doesn't really require any page refreshes, and that stirs up a whole 
bunch of good feelings as regards what is possible on the web. 

I started thinking about web programming in the mid-2011 time frame. I 
wanted to see how far I could push the concept of a dynamic user 
experience. Fast forward to February 10, 2014 (today), and I think that my 
original vision has finally come to fruition. Starting in September 2012, I 
began working on the current incarnation. My idea was to go "all in" by way 
of seeing if I could duplicate the OS X end user experience inside of a web 
browser... all courtesy of Google's V8 JS engine running inside of standard 
Chrome.   Since that time, I've put in about a full year's worth of 8-12 
hour coding days. Here is the basic setup: 

There is a core desktop module that performs all of the essential system 
level operations: window, icon, context menu, menubar, and toolbar GUI 
operations, as well as all of the interactions with Local Storage and the 
filesystem API. 

There are several self-contained modules of which the core has no knowledge 
that plug into the system through a basic interface.  The most important of 
these modules are the Unix-style text editor (called Nanim) and the 
command-line interface.  There are other, graphical modules that I've spent 
relatively small amounts of time developing, such as a media player and a 
prototype-phase word processor. 

There are several ways of thinking about the system.  Most obviously, I 
think that it pushes the envelope in terms of how we understand the notion 
of an operating system.  Such a thing has traditionally been written in 
native code, and has required a fairly sizeable cost to download, install, 
replace, etc.  (What I mainly mean by "cost" is NOT the purchase price, but 
rather the potential for catastrophe if the installation procedures are not 
followed precisely.  So by this definition, we can judge the commercial 
OSes to be much cheaper that all of the Linux distributions that require 
one to do things such as partition hard drives and install custom boot 
loaders to try them out.) 

We can call the OS that I've developed a trivially loadable/bootable OS. 
The only investment that it currently requires comes in the form of 
accepting the browser's "this site wants to permanently store data on your 
computer" prompt, and then waiting the minute or so for all of the 
resources to download. After that, everything is served locally, meaning 
that a network connection is not necessary for it to load. Furthermore, 
given that all of the locally stored data is essentially namespaced by the 
domain name, one can have many OS environments running alongside each other 
in different tabs of the same browser, with the caveat that each tab is 
must use a different subdomain (this just means that all of the resources 
owned by www.urdesk.net essentially live in a sandboxe, safely hidden away 
from, eg. dev.urdesk.net... or any other subdomain of urdesk.net). 

In this way, there is essentially zero cost involved when it comes to 
experimenting with a new OS, and trying out all of the different 
applications contained within it. Application developers will be able to 
write their logic without having to worry about distribution problems, 
given that it will be guaranteed to run on any Chrome browser, thereby 
eliminating all issues related to downloading (and the related issue of 
viruses), plugin-installing, flag-enabling, etc. 

The next level of thinking about the system is that the applications are 
not traditional "applications" in the sense that they run as different 
native processes, and thereby keep their data structures in mutually 
exclusive address spaces. In this system, there are precisely zero issues 
of interprocess communication (IPC). All "applications" are actually just 
JavaScript function objects that collectively inhabit a single browser tab 
address space. All complications traditionally related to IPC now become 
null and void. Given this fact, the possibilities in terms of the 
development of a holistic kind of user experience increase profoundly. (As 
a trivial example of this, imagine your calendar app being aware of what 
you are typing into your word processor and adjusting itself according.) 

And finally, this system allows for the emergence of a fundamentally new 
paradigm in terms of how we relate to our computers.  I have actually had a 
much longer history developing AI-type command-and-response systems than I 
have had developing user interfaces.  Within the command-line interface, 
there is a working prototype of a natural language REPL (read/eval/print 
loop) that accepts the kind of syntax that the most naive of end users 
would not find intimidating in the least.  You must understa

Re: [nodejs] Running multiple instances of node.js servers on different ports

[Arman Didandeh]

My bad.

Right now I have connections to db for each developer on the same server,
so everyone can connect. However there is only one db instance.

What I am saying is that is there a way to do the same for the application
server? So users can get served by the same server but on different ports.
Is it even possible?
On Feb 10, 2014 2:58 PM, "Mark Hahn"  wrote:

> I'm sorry but I'm getting lost at this sentence ...
>
> > I trying to deploy a similar connection for the DB over the network
>
> You haven't mentioned a DB before.  A node server is a very different
> thing than a DB server.
>
> Maybe someone else can understand better?  I might not be thinking
> straight today.
>
>
>
> On Mon, Feb 10, 2014 at 11:27 AM, Arman Didandeh  > wrote:
>
>> Let me describe the situation a bit more.
>>
>> So what I have right now is a repo, the code for which has been written
>> by someone else. Now I have myself and other developers who cloned the code
>> on our machines to extend it.
>>
>> Since each developer is working on different modules, I do not want us to
>> commit or branch on the repo and have the repo run on my server. In fact, I
>> want a separate stable thing to run, and I was planning for each developer
>> to run and test their added codes on their own machines. However some
>> machines are down in RAM, so I trying to deploy a similar connection for
>> the DB over the network (with different users and even possibly different
>> DB clones), but this time on different ports.
>>
>> If this is what you pointed out, could you please forward me to some
>> instruction, as I am not very good at these things YET!
>>
>> Cheers
>>
>>
>> On 10 February 2014 14:21, Mark Hahn  wrote:
>>
>>> Interesting question.  One would think than you could put the http
>>> server example in the code multiple times with a different variable for
>>> each httpserver.  I don't see any reason why that wouldn't work.  Should
>>> only take a few minutes to try it.
>>>
>>>
>>> On Mon, Feb 10, 2014 at 11:00 AM, Arman Didandeh <
>>> arman.didan...@gmail.com> wrote:
>>>
 So there is no way to run one executable that listens to different
 ports?


 On 10 February 2014 13:58, Mark Hahn  wrote:

> It should be as simple as running a different node executable for each
> server.  In other words you'd do
>
> node server1.js
> node server2.js
> node server3.js
>
> where each executable is using a different port.  You might want to
> make the port an argument so you could say `node server.js 8080`.
>
>
> On Mon, Feb 10, 2014 at 10:48 AM, Arman Didandeh <
> arman.didan...@gmail.com> wrote:
>
>> Dear all,
>>
>> I am a newbie when it comes to node.js, so I need your help towards
>> running multiple instances of my node.js server on my machine.
>>
>> I do not want to use other tools that manage this and prefer to do
>> the confing to learn more.
>>
>> Also  I do not need to assign each of these instances to a core (as I
>> have seen is very popular in discussion forums).
>>
>> All I need is for my local machine (which is acting as the server
>> during the development phase), to be able to listen to different ports.
>> This way myself and other developers can test their changes in code 
>> through
>> these connections and once everything is stable, each person could commit
>> to our git repo. Also the same machine is working as the actual server 
>> for
>> current users so it is probably using port 80.
>>
>> Thanks in advance for your helps.
>>
>> Cheers all,
>> Arman
>>
>> --
>> --
>> Job Board: http://jobs.nodejs.org/
>> Posting guidelines:
>> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
>> You received this message because you are subscribed to the Google
>> Groups "nodejs" group.
>> To post to this group, send email to nodejs@googlegroups.com
>> To unsubscribe from this group, send email to
>> nodejs+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/nodejs?hl=en?hl=en
>>
>> ---
>> You received this message because you are subscribed to the Google
>> Groups "nodejs" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to nodejs+unsubscr...@googlegroups.com.
>>
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>  --
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visi

Re: [nodejs] Running multiple instances of node.js servers on different ports

[Mark Hahn]

I'm sorry but I'm getting lost at this sentence ...

> I trying to deploy a similar connection for the DB over the network

You haven't mentioned a DB before.  A node server is a very different thing
than a DB server.

Maybe someone else can understand better?  I might not be thinking straight
today.



On Mon, Feb 10, 2014 at 11:27 AM, Arman Didandeh
wrote:

> Let me describe the situation a bit more.
>
> So what I have right now is a repo, the code for which has been written by
> someone else. Now I have myself and other developers who cloned the code on
> our machines to extend it.
>
> Since each developer is working on different modules, I do not want us to
> commit or branch on the repo and have the repo run on my server. In fact, I
> want a separate stable thing to run, and I was planning for each developer
> to run and test their added codes on their own machines. However some
> machines are down in RAM, so I trying to deploy a similar connection for
> the DB over the network (with different users and even possibly different
> DB clones), but this time on different ports.
>
> If this is what you pointed out, could you please forward me to some
> instruction, as I am not very good at these things YET!
>
> Cheers
>
>
> On 10 February 2014 14:21, Mark Hahn  wrote:
>
>> Interesting question.  One would think than you could put the http server
>> example in the code multiple times with a different variable for each
>> httpserver.  I don't see any reason why that wouldn't work.  Should only
>> take a few minutes to try it.
>>
>>
>> On Mon, Feb 10, 2014 at 11:00 AM, Arman Didandeh <
>> arman.didan...@gmail.com> wrote:
>>
>>> So there is no way to run one executable that listens to different ports?
>>>
>>>
>>> On 10 February 2014 13:58, Mark Hahn  wrote:
>>>
 It should be as simple as running a different node executable for each
 server.  In other words you'd do

 node server1.js
 node server2.js
 node server3.js

 where each executable is using a different port.  You might want to
 make the port an argument so you could say `node server.js 8080`.


 On Mon, Feb 10, 2014 at 10:48 AM, Arman Didandeh <
 arman.didan...@gmail.com> wrote:

> Dear all,
>
> I am a newbie when it comes to node.js, so I need your help towards
> running multiple instances of my node.js server on my machine.
>
> I do not want to use other tools that manage this and prefer to do the
> confing to learn more.
>
> Also  I do not need to assign each of these instances to a core (as I
> have seen is very popular in discussion forums).
>
> All I need is for my local machine (which is acting as the server
> during the development phase), to be able to listen to different ports.
> This way myself and other developers can test their changes in code 
> through
> these connections and once everything is stable, each person could commit
> to our git repo. Also the same machine is working as the actual server for
> current users so it is probably using port 80.
>
> Thanks in advance for your helps.
>
> Cheers all,
> Arman
>
> --
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>
> ---
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to nodejs+unsubscr...@googlegroups.com.
>
> For more options, visit https://groups.google.com/groups/opt_out.
>

  --
 --
 Job Board: http://jobs.nodejs.org/
 Posting guidelines:
 https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
 You received this message because you are subscribed to the Google
 Groups "nodejs" group.
 To post to this group, send email to nodejs@googlegroups.com
 To unsubscribe from this group, send email to
 nodejs+unsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/nodejs?hl=en?hl=en

 ---
 You received this message because you are subscribed to a topic in the
 Google Groups "nodejs" group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/nodejs/FOkOcKQ68Ew/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 nodejs+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.

>>>
>>> 

Re: [nodejs] Running multiple instances of node.js servers on different ports

[Arman Didandeh]

Let me describe the situation a bit more.

So what I have right now is a repo, the code for which has been written by
someone else. Now I have myself and other developers who cloned the code on
our machines to extend it.

Since each developer is working on different modules, I do not want us to
commit or branch on the repo and have the repo run on my server. In fact, I
want a separate stable thing to run, and I was planning for each developer
to run and test their added codes on their own machines. However some
machines are down in RAM, so I trying to deploy a similar connection for
the DB over the network (with different users and even possibly different
DB clones), but this time on different ports.

If this is what you pointed out, could you please forward me to some
instruction, as I am not very good at these things YET!

Cheers


On 10 February 2014 14:21, Mark Hahn  wrote:

> Interesting question.  One would think than you could put the http server
> example in the code multiple times with a different variable for each
> httpserver.  I don't see any reason why that wouldn't work.  Should only
> take a few minutes to try it.
>
>
> On Mon, Feb 10, 2014 at 11:00 AM, Arman Didandeh  > wrote:
>
>> So there is no way to run one executable that listens to different ports?
>>
>>
>> On 10 February 2014 13:58, Mark Hahn  wrote:
>>
>>> It should be as simple as running a different node executable for each
>>> server.  In other words you'd do
>>>
>>> node server1.js
>>> node server2.js
>>> node server3.js
>>>
>>> where each executable is using a different port.  You might want to make
>>> the port an argument so you could say `node server.js 8080`.
>>>
>>>
>>> On Mon, Feb 10, 2014 at 10:48 AM, Arman Didandeh <
>>> arman.didan...@gmail.com> wrote:
>>>
 Dear all,

 I am a newbie when it comes to node.js, so I need your help towards
 running multiple instances of my node.js server on my machine.

 I do not want to use other tools that manage this and prefer to do the
 confing to learn more.

 Also  I do not need to assign each of these instances to a core (as I
 have seen is very popular in discussion forums).

 All I need is for my local machine (which is acting as the server
 during the development phase), to be able to listen to different ports.
 This way myself and other developers can test their changes in code through
 these connections and once everything is stable, each person could commit
 to our git repo. Also the same machine is working as the actual server for
 current users so it is probably using port 80.

 Thanks in advance for your helps.

 Cheers all,
 Arman

 --
 --
 Job Board: http://jobs.nodejs.org/
 Posting guidelines:
 https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
 You received this message because you are subscribed to the Google
 Groups "nodejs" group.
 To post to this group, send email to nodejs@googlegroups.com
 To unsubscribe from this group, send email to
 nodejs+unsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/nodejs?hl=en?hl=en

 ---
 You received this message because you are subscribed to the Google
 Groups "nodejs" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to nodejs+unsubscr...@googlegroups.com.

 For more options, visit https://groups.google.com/groups/opt_out.

>>>
>>>  --
>>> --
>>> Job Board: http://jobs.nodejs.org/
>>> Posting guidelines:
>>> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
>>> You received this message because you are subscribed to the Google
>>> Groups "nodejs" group.
>>> To post to this group, send email to nodejs@googlegroups.com
>>> To unsubscribe from this group, send email to
>>> nodejs+unsubscr...@googlegroups.com
>>> For more options, visit this group at
>>> http://groups.google.com/group/nodejs?hl=en?hl=en
>>>
>>> ---
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "nodejs" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/nodejs/FOkOcKQ68Ew/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> nodejs+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>
>>  --
>> --
>> Job Board: http://jobs.nodejs.org/
>> Posting guidelines:
>> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
>> You received this message because you are subscribed to the Google
>> Groups "nodejs" group.
>> To post to this group, send email to nodejs@googlegroups.com
>> To unsubscribe from this group, send email to
>> nodejs+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/nodejs?hl=en?hl=en
>>
>> ---
>> You received this message because

Re: [nodejs] Running multiple instances of node.js servers on different ports

[Mark Hahn]

Interesting question.  One would think than you could put the http server
example in the code multiple times with a different variable for each
httpserver.  I don't see any reason why that wouldn't work.  Should only
take a few minutes to try it.


On Mon, Feb 10, 2014 at 11:00 AM, Arman Didandeh
wrote:

> So there is no way to run one executable that listens to different ports?
>
>
> On 10 February 2014 13:58, Mark Hahn  wrote:
>
>> It should be as simple as running a different node executable for each
>> server.  In other words you'd do
>>
>> node server1.js
>> node server2.js
>> node server3.js
>>
>> where each executable is using a different port.  You might want to make
>> the port an argument so you could say `node server.js 8080`.
>>
>>
>> On Mon, Feb 10, 2014 at 10:48 AM, Arman Didandeh <
>> arman.didan...@gmail.com> wrote:
>>
>>> Dear all,
>>>
>>> I am a newbie when it comes to node.js, so I need your help towards
>>> running multiple instances of my node.js server on my machine.
>>>
>>> I do not want to use other tools that manage this and prefer to do the
>>> confing to learn more.
>>>
>>> Also  I do not need to assign each of these instances to a core (as I
>>> have seen is very popular in discussion forums).
>>>
>>> All I need is for my local machine (which is acting as the server during
>>> the development phase), to be able to listen to different ports. This way
>>> myself and other developers can test their changes in code through these
>>> connections and once everything is stable, each person could commit to our
>>> git repo. Also the same machine is working as the actual server for current
>>> users so it is probably using port 80.
>>>
>>> Thanks in advance for your helps.
>>>
>>> Cheers all,
>>> Arman
>>>
>>> --
>>> --
>>> Job Board: http://jobs.nodejs.org/
>>> Posting guidelines:
>>> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
>>> You received this message because you are subscribed to the Google
>>> Groups "nodejs" group.
>>> To post to this group, send email to nodejs@googlegroups.com
>>> To unsubscribe from this group, send email to
>>> nodejs+unsubscr...@googlegroups.com
>>> For more options, visit this group at
>>> http://groups.google.com/group/nodejs?hl=en?hl=en
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "nodejs" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to nodejs+unsubscr...@googlegroups.com.
>>>
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>
>>  --
>> --
>> Job Board: http://jobs.nodejs.org/
>> Posting guidelines:
>> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
>> You received this message because you are subscribed to the Google
>> Groups "nodejs" group.
>> To post to this group, send email to nodejs@googlegroups.com
>> To unsubscribe from this group, send email to
>> nodejs+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/nodejs?hl=en?hl=en
>>
>> ---
>> You received this message because you are subscribed to a topic in the
>> Google Groups "nodejs" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/nodejs/FOkOcKQ68Ew/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> nodejs+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>  --
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "nodejs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to nodejs+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [nodejs] Running multiple instances of node.js servers on different ports

[Arman Didandeh]

So there is no way to run one executable that listens to different ports?


On 10 February 2014 13:58, Mark Hahn  wrote:

> It should be as simple as running a different node executable for each
> server.  In other words you'd do
>
> node server1.js
> node server2.js
> node server3.js
>
> where each executable is using a different port.  You might want to make
> the port an argument so you could say `node server.js 8080`.
>
>
> On Mon, Feb 10, 2014 at 10:48 AM, Arman Didandeh  > wrote:
>
>> Dear all,
>>
>> I am a newbie when it comes to node.js, so I need your help towards
>> running multiple instances of my node.js server on my machine.
>>
>> I do not want to use other tools that manage this and prefer to do the
>> confing to learn more.
>>
>> Also  I do not need to assign each of these instances to a core (as I
>> have seen is very popular in discussion forums).
>>
>> All I need is for my local machine (which is acting as the server during
>> the development phase), to be able to listen to different ports. This way
>> myself and other developers can test their changes in code through these
>> connections and once everything is stable, each person could commit to our
>> git repo. Also the same machine is working as the actual server for current
>> users so it is probably using port 80.
>>
>> Thanks in advance for your helps.
>>
>> Cheers all,
>> Arman
>>
>> --
>> --
>> Job Board: http://jobs.nodejs.org/
>> Posting guidelines:
>> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
>> You received this message because you are subscribed to the Google
>> Groups "nodejs" group.
>> To post to this group, send email to nodejs@googlegroups.com
>> To unsubscribe from this group, send email to
>> nodejs+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/nodejs?hl=en?hl=en
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "nodejs" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to nodejs+unsubscr...@googlegroups.com.
>>
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>  --
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "nodejs" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/nodejs/FOkOcKQ68Ew/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> nodejs+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [nodejs] Running multiple instances of node.js servers on different ports

[Mark Hahn]

It should be as simple as running a different node executable for each
server.  In other words you'd do

node server1.js
node server2.js
node server3.js

where each executable is using a different port.  You might want to make
the port an argument so you could say `node server.js 8080`.


On Mon, Feb 10, 2014 at 10:48 AM, Arman Didandeh
wrote:

> Dear all,
>
> I am a newbie when it comes to node.js, so I need your help towards
> running multiple instances of my node.js server on my machine.
>
> I do not want to use other tools that manage this and prefer to do the
> confing to learn more.
>
> Also  I do not need to assign each of these instances to a core (as I have
> seen is very popular in discussion forums).
>
> All I need is for my local machine (which is acting as the server during
> the development phase), to be able to listen to different ports. This way
> myself and other developers can test their changes in code through these
> connections and once everything is stable, each person could commit to our
> git repo. Also the same machine is working as the actual server for current
> users so it is probably using port 80.
>
> Thanks in advance for your helps.
>
> Cheers all,
> Arman
>
> --
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "nodejs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to nodejs+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[nodejs] Running multiple instances of node.js servers on different ports

[Arman Didandeh]

Dear all,

I am a newbie when it comes to node.js, so I need your help towards running 
multiple instances of my node.js server on my machine.

I do not want to use other tools that manage this and prefer to do the 
confing to learn more.

Also  I do not need to assign each of these instances to a core (as I have 
seen is very popular in discussion forums).

All I need is for my local machine (which is acting as the server during 
the development phase), to be able to listen to different ports. This way 
myself and other developers can test their changes in code through these 
connections and once everything is stable, each person could commit to our 
git repo. Also the same machine is working as the actual server for current 
users so it is probably using port 80.

Thanks in advance for your helps.

Cheers all,
Arman

-- 
-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[nodejs] Re: nodejs beginner

[Qihan Zhang]

Welcome to the community Alfred!

In addition to the great resources already posted, StrongLoop.com also has 
a few introductory videos to help you understand the fundamentals of node, 
you can find them here 
http://strongloop.com/developers/videos/#a-video-intro-to-nodejs-fundamentalsand
 
http://strongloop.com/developers/videos/#a-video-intro-to-how-node-works

I definitely recommend nodeschool.io as well for a more hands-on 
experience, it is very well done and teaches you a lot of the main points 
of node by doing.

Be sure to check out and bookmark our blog at 
http://strongloop.com/strongblog/. We frequently update it with the latest 
and greatest tutorials and real-world applications of node. Here's a few 
highlights for example:

   - What makes Node.js Faster than Java? 

   - Creating desktop applications with 
node-webkit
   - Managing Node.js Callback Hell with Promises, Generators and Other 
   
Approaches

Cheers

On Saturday, February 8, 2014 7:13:56 PM UTC-8, Alfred Roa wrote:
>
> Hello
>
> Im new to nodejs anyone please recommend a good beginners guide? im more 
> into microsoft technologies but was struck with the reviews of nodejs.
>
> Alfred
>
>

-- 
-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [nodejs] Can't compile node-sass on FreeBSD 10.0

[Vladimir Vasilenko]

Andrew Nesbitt promt a solution ( Based on this guide: 
https://github.com/TryGhost/Ghost/wiki/HOWTO:FreeBSD ):

CXX=c++ npm install node-sass

Thank all.

Best regards,
Vladimir Vasilenko.

On Mon, 10 Feb 2014 04:34:48 -0800 (PST)
Vladimir Vasilenko  wrote:

> Hello, when I try run "npm install node-sass", I get this errors:
> 
> gyp http GET http://nodejs.org/dist/v0.11.9/node-v0.11.9.tar.gz
> gyp http 200 http://nodejs.org/dist/v0.11.9/node-v0.11.9.tar.gz
> gmake: Вход в каталог 
> `/usr/home/jeltoesolnce/tmp/test_zurb_5/node-sass/build'
>   CXX(target) Release/obj.target/binding/binding.o
> gmake: g++: Команда не найдена
> gmake: *** [Release/obj.target/binding/binding.o] Ошибка 127
> gmake: Выход из каталога 
> `/usr/home/jeltoesolnce/tmp/test_zurb_5/node-sass/build'
> gyp ERR! build error 
> gyp ERR! stack Error: `gmake` failed with exit code: 2
> gyp ERR! stack at ChildProcess.onExit 
> (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:267:23)
> gyp ERR! stack at ChildProcess.EventEmitter.emit (events.js:101:17)
> gyp ERR! stack at Process.ChildProcess._handle.onexit 
> (child_process.js:827:12)
> gyp ERR! System FreeBSD 10.0-RELEASE-p4
> gyp ERR! command "node" 
> "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" 
> "rebuild"
> gyp ERR! cwd /usr/home/jeltoesolnce/tmp/test_zurb_5/node-sass
> gyp ERR! node -v v0.11.9
> gyp ERR! node-gyp -v v0.10.10
> gyp ERR! not ok 
> Build failed
> npm ERR! weird error 1
> npm ERR! not ok code 0
> 
> -- 
> -- 
> Job Board: http://jobs.nodejs.org/
> Posting guidelines: 
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
> 
> --- 
> You received this message because you are subscribed to the Google Groups 
> "nodejs" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to nodejs+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.


-- 
Vladimir Vasilenko 

-- 
-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [nodejs] io is not defined

[almarjin]

Hi ryan,

Thanks for the reply, but the chat application if working properly which 
means the socket.io is defined properly in the server side code. In my 
above post it's listening to port 3050, but when I go to port 300, the chat 
is now working and I can login to the site. If I make them listed to the 
same port, I'm getting error.

Thanks again

On Saturday, January 18, 2014 8:46:52 AM UTC+8, ryandesign wrote:
>
>
> On Jan 17, 2014, at 04:59, almarjin > 
> wrote: 
>
> > I'm trying to create a chat application with login. I have manage to 
> make the chat and login work in a separate application but when integrating 
> them, they dont work. 
> > 
> > I'm getting this error: 
> > 
> > Failed to load resource: the server responded with a status of 404 (Not 
> Found) http://dev.nodejs.putoshop.com:3000/socket.io/socket.io.js 
> > Uncaught ReferenceError: io is not defined dev.nodejs.putoshop.com/:14 
> > 
> > I'm using EJS for my template engine. If I go to the port(3050) where 
> the chat application is listening, the chat application is working and when 
> I go to main port which is 3000, I can login but the chat application is 
> not working and showing the error above. 
>
> It sounds like in your server-side code you have forgotten to require('
> socket.io') and make it listen to your app. That’s what makes the path /
> socket.io/socket.io.js return the right script instead of the 404 error 
> you’re getting. 
>
> http://socket.io/#how-to-use 
>
>
>

-- 
-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [nodejs] Re: Print form node

[Zlatko Đurić]

On 02/10/2014 02:00 PM, Lincoln Lemos wrote:
Yes, I want click on 'print' button and this send a job to a user's 
printer. (With no dialogs).
Maybe i can make a function to click "Print Automatically", and send 
the jobs with no actions.




Uh, then tough luck! I don't think this is possible with any server-side 
code, at least not in the regular sense.


I think the most that you can do here is autostart a print dialog. That 
means doing something like window.print(); or iframeElement.print(); in 
frontend javascript. But it's not related to node. Also, the above will 
not automatically print, it will just open the users' print dialog - if 
they have any installed.


The problem is generally in that that the browser scripts cannot access 
hardware, and probably the browser itself can't access it by default.


It could possibly be done with some sort of browser extension, but I'm 
not sure about this.


In any case, it is nothing to do with node.js. Your server will probably 
have no access to the printer ports if it is not in a sort of a vpn or 
local network and having remote admin access to the users' computer. 
Which is probably not the case :)







2014-02-06 7:26 GMT-02:00 zladuric >:


That module looks like it is made node into a print server.

What exactly do you mean, print from the frontend? Click on the
'print' button? Where does this action print: to your printer
attached to the node's server? Or to the users' printer?

Because if it's the former, it's in the modules' examples and
readme page. I'd use this module to discover printers on wakeup.
Then once I get a request from 'frontend' to do some printing, use
this module to send it a print job.


If it's the later, then node is of no help, I think - unless
you're doing something like node-webkit, which is a client side app.



On Wednesday, February 5, 2014 7:57:15 PM UTC+1, Lincoln de Sousa
Cunha Lemos wrote:

How i can print automatically with node from front-end?

I found a module (Ipp - internet print protocol ).
This help me start a communication with the printer, but i can
not do with this from front-end.

Someone have any idea?

-- 
Lincoln Lemos

*62 81998667 
*

-- 
-- 
Job Board: http://jobs.nodejs.org/

Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com

To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

---
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to nodejs+unsubscr...@googlegroups.com
.
For more options, visit https://groups.google.com/groups/opt_out.




--
Lincoln Lemos
*62 81998667

*BIGO Design 

--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines

You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

---
You received this message because you are subscribed to a topic in the 
Google Groups "nodejs" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/nodejs/mV2DZWFjn2c/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
nodejs+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.



--
Zlatko

--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--- 
You received this message because you are subscribed to the Google Groups "nodejs" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [nodejs] Re: Print form node

[Lincoln Lemos]

Yes, I want click on 'print' button and this send a job to a user's
printer. (With no dialogs).
Maybe i can make a function to click "Print Automatically", and send the
jobs with no actions.




2014-02-06 7:26 GMT-02:00 zladuric :

> That module looks like it is made node into a print server.
>
> What exactly do you mean, print from the frontend? Click on the 'print'
> button? Where does this action print: to your printer attached to the
> node's server? Or to the users' printer?
>
> Because if it's the former, it's in the modules' examples and readme page.
> I'd use this module to discover printers on wakeup. Then once I get a
> request from 'frontend' to do some printing, use this module to send it a
> print job.
>
>
> If it's the later, then node is of no help, I think - unless you're doing
> something like node-webkit, which is a client side app.
>
>
>
> On Wednesday, February 5, 2014 7:57:15 PM UTC+1, Lincoln de Sousa Cunha
> Lemos wrote:
>>
>> How i can print automatically with node from front-end?
>>
>> I found a module (Ipp - internet print protocol ).
>> This help me start a communication with the printer, but i can not do
>> with this from front-end.
>>
>> Someone have any idea?
>>
>> --
>> Lincoln Lemos
>>
>> *62 81998667 <62%2081998667>*
>>
>  --
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "nodejs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to nodejs+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>



-- 
Lincoln Lemos


*62 81998667*BIGO Design 

-- 
-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[nodejs] Can't compile node-sass on FreeBSD 10.0

[Vladimir Vasilenko]

Hello, when I try run "npm install node-sass", I get this errors:

gyp http GET http://nodejs.org/dist/v0.11.9/node-v0.11.9.tar.gz
gyp http 200 http://nodejs.org/dist/v0.11.9/node-v0.11.9.tar.gz
gmake: Вход в каталог 
`/usr/home/jeltoesolnce/tmp/test_zurb_5/node-sass/build'
  CXX(target) Release/obj.target/binding/binding.o
gmake: g++: Команда не найдена
gmake: *** [Release/obj.target/binding/binding.o] Ошибка 127
gmake: Выход из каталога 
`/usr/home/jeltoesolnce/tmp/test_zurb_5/node-sass/build'
gyp ERR! build error 
gyp ERR! stack Error: `gmake` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit 
(/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:267:23)
gyp ERR! stack at ChildProcess.EventEmitter.emit (events.js:101:17)
gyp ERR! stack at Process.ChildProcess._handle.onexit 
(child_process.js:827:12)
gyp ERR! System FreeBSD 10.0-RELEASE-p4
gyp ERR! command "node" 
"/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" 
"rebuild"
gyp ERR! cwd /usr/home/jeltoesolnce/tmp/test_zurb_5/node-sass
gyp ERR! node -v v0.11.9
gyp ERR! node-gyp -v v0.10.10
gyp ERR! not ok 
Build failed
npm ERR! weird error 1
npm ERR! not ok code 0

-- 
-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.