hi
we are using express.js app and we are running it using following command
node app.js
it sends a lot of request logs to the console, sometimes with errors too,
we also use it to output some info on console.
what we are looking is how we can disable only request logs.
thanks
--
Job board:
hi
we are running an app using forever.js, but its creating hefty log file due
to heavy traffic that we get on the app, is there a way to limit the log
size or use logrotate and delete old logs after certain period of time.
thanks
--
Job board: http://jobs.nodejs.org/
New group rules:
https:
Can somebody tell me how to build and compile the "NodeJS Source code" on
and Java based IDE(ex. Eclipse, VXWorks).
--
Job board: http://jobs.nodejs.org/
New group rules:
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules:
https://github.com/joyent/node/wiki/Mai
thanks to all the inputs, but after some serious research, we found that
increasing globalAgent.maxSockets=Infinity; fixed our problems.
and we also used some fd fine tuning for TCP open files.
--
Job board: http://jobs.nodejs.org/
New group rules:
https://gist.github.com/othiym23/9886289#file-
we have the following scenario and we are greatly stuck to scale it and
cannot find the problem
our processflow is as follows:
-request received from client and headers are collected
-initiate a async.waterfall
>>get some data from redis
>>build some object based on redis
>>build an array of task
True. Ghost looks nice, but it's development is too slow and monolithic.
They only recently managed to add support for tag links, something that you
wouldn't expect a blogging engine to launch without (and simultaneously
broke several blogs with the update, including mine).
On Monday, 23 June 2
Just curious, how likely is it that the average public application would
use only singleton routes? I'm considering the reality of a "--singleton"
option that might be added to other more popular routers.
On Monday, 16 June 2014 04:40:00 UTC-7, Leo Oshiro wrote:
>
> Hello,
>
> I just finished wr
Hello,
What is the best way to "fake" the *request* event of http module? My use
case is to make a socket.io API that looks like a http verb api (similar to
SailsJS) so generic routers can be used for sockets (like koa-route).
The Sails implementation fakes a request using a mocking module. I f
's really the same worker
> dying.
>
> On Wednesday, 29 May 2013 12:30:19 UTC+2, Prajwal Manjunath wrote:
>>
>> I'm trying to test a cluster which forks off three children. When one of
>> them dies, the master replaces that worker with a new fork. I'm usi
I'm trying to test a cluster which forks off three children. When one of
them dies, the master replaces that worker with a new fork. I'm using Mocha
with Sinon stubs for testing.
I'm stubbing out the cluster's "fork" method. The first test case which
checks that it is called thrice (for 3 worke
There's nothing wrong with this per se, but you're simple not using node to
its strengths here. Mozilla's Persona actually does something similar using
node-compute-cluster (https://github.com/lloyd/node-compute-cluster).
But why use javascript for this? Computationally heavy programs are
tradi
If you already have expertise in RoR, you must understand there is still
nothing on Node's side that is as all-emcompassing or as stable as Rails.
For a startup project, getting off the ground asap is critical, so you
should focus on the stack that will do most for you, and that is RoR. RoR
its
There are plenty of resources on the web addressing this, you won't find
much help for such trivial questions here. Just search for and study
Backbone.js and similar client-side MV* frameworks for single page apps.
Your server would act like an independent API server. It's just like a
Rails app
;t have grunt boilerplate.
>>>
>>> Serverside "MVC" is 100% overrated.
>>>
>>> Usage of backbone on the server is unnecessary, usage of it on the
>>> client is completely 100% orthogonal to setting up the "boilerplate" for a
>>&
Hi,
I was trying to build a web app on express, and on the way I couldn't help
but notice that there was a lack of proper boilerplates encompassing all
major aspects of modern web apps. Now, a typical node project would use
Bower for client-side library management, Grunt for dev workflow
manag
it yourself. is performance an
> issue? what the bottleneck? would a binding solve that issue? What about
> development resources and maintenance of the new lib, does this pay off?
>
> Am Montag, 18. März 2013 06:19:33 UTC+1 schrieb Prajwal Manjunath:
>>
>> Hi,
>
Hi,
I was reading up on writing addons for Node. I realize its primary purpose
is to extend Node's functionality, but I was wondering, if my application
uses a C++ library very frequently, would I get any performance benefit by
binding it to the V8 runtime with node-gyp, versus just calling it
I second node. Your application seems pretty straightforward, and you can
tap readily into your frontend/javascript guys to do it for you. Also, Node
is far more lightweight than any Java solution since it pretty much comes
bundled with a web server built in. Scala/Closure would require more hir
Cluster was never meant to address the computation problems issue in Node.
It was simply meant to be something like a very basic Passenger/Unicorn
load distributor.
The "compute-cluster" is ideally how you would solve this. At a simpler
level, you could simply write your compute intensive code
19 matches
Mail list logo
