Nodejs-code

Strider, our continuous deployment platform for node.js and Python, is in fact written in node.js and Python and it was the first project that we started testing and deploying via Strider.

A problem I experienced while starting coding with NodeJS environment and Express framework is that I had difficulties to make a well structured app quickly. I spent too much time on organizing my ...

I’m happy to share a little experiment I played with this week. I needed to take a look at Node.js & it’s family of technology for a project but found it hard to find good explanations of how to build apps.

In part 2 of my node.js tutorial, we built the web server and created a dispatcher to handle the incoming client browser requests and route them to actions. In part 3 of this series, I cover refactoring our Node app into separate node modules and components.

Two-factor authentication is becoming the go-to method for increased login security on the web, as it ties a physical device to your virtual credentials.

The first step to doing anything with node.js is creating a server to accept incoming HTTP requests. You can also create a TCP server or work with UDP, but I won't be going into that here...

Our node app that we created in part one is writing out our header "Hello World!" really well. But that's not really that cool. Plus, it doesn't scale. If we wanted to output more HTML we would find the current solution to be a giant pain in the ass.

In this post, I take a look at the different patterns that you need to know when using Node.js. These came from my own coding and from a look at the code behind Tim Caswell’s flow control libraries.

This stack is great for rapid prototyping and highly intuitive. Personal note: I love using Javascript as my only language for the entire application(FrontEnd/BackEnd/API/Database). Restify is still in early development but is essentially just an extension of Express. So for anyone needing more stability you can easily just substitute Express in.

One of the annoyances of Node.js for development purposes is the fact that you have to restart the server everytime you make changes to your included modules. This is because Node actually caches module includes for better performance. A great workaround is using the Node Module “Supervisor“.

The project I have made is very simple and not optimized. I quickly wanted to demonstrate the concept and will try to explain the workflow now:

This is pretty much an exact copy of my Writing a Nagios plugin with PHP post modified for Javascript. So, here is a quick example of writing a Javascript plugin for Nagios using Node.js.