| description "Upstart script to run a nodejs app as a service" | |
| author "Louis Chatriot" | |
| env NODE_BIN=/usr/local/bin/node | |
| env APP_DIR=/path/to/app/dir | |
| env SCRIPT_FILE="scriptfile.js" # Entry point for the nodejs app | |
| env LOG_FILE=/path/to/logfile.log | |
| env RUN_AS="anyuser" # Upstart can only be run nicely as root, need to drop privileges | |
| env SERVER_ENV="anything" # Usual apps can be run in different environments (development, test, production ...) | |
| # I typically use the environment variable NODE_ENV (see below) |
This article has been given a more permanent home on my blog. Also, since it was first written, the development of the Promises/A+ specification has made the original emphasis on Promises/A seem somewhat outdated.
Promises are a software abstraction that makes working with asynchronous operations much more pleasant. In the most basic definition, your code will move from continuation-passing style:
getTweetsFor("domenic", function (err, results) {
// the rest of your code goes here.
| * Sensu | |
| - As a nagios replacement basically, plus the extra goodies tha sensu has itself | |
| (mutators, events filters , handlers, API, etc). | |
| * Riemann | |
| - When state tracking is needed, cause of the powerful stream processing language, | |
| I'm planning to aggregate events from client agents running on riak nodes, | |
| erlang queue size grow, cassandra, others, to track trends and report | |
| on events, the idea is to report posible problems before they became critical. |
It is generally desirable to group all the hosts for a specific service into a single dashboard view. For example, all the web servers are in single view while all the database servers are in another view.
This is usually not an issue when you are sending custom metrics using Riemann client. However, there are cases where you are using something that you do not control how the metrics are being sent. i.e., Riemann-tools.
Since Riemann-tools scripts are application agnostic, in order for the dashboard view to group hosts, we must inject some application specific information into the tags field. Tags is a collection of arbitrary strings. In the case of Riemann-tools scripts you can pass in arbitrary strings on the command line.
riemann-health --host 127.0.0.1 --tag "prod" --tag "webserver"
| /** | |
| * APNS test client | |
| */ | |
| var net = require('net'); | |
| var HOST = '127.0.0.1'; | |
| var PORT = 7777; | |
| var TOKEN_LENGTH = 64; | |
| var NUM_PACKETS = 5; |
| /** | |
| * Mock APNS server | |
| */ | |
| var net = require('net'); | |
| var HOST='127.0.0.1'; | |
| var PORT=7777; | |
| // Need this option so the client doesn't close | |
| // the connection on sending a FIN |
| #include <czmq.h> | |
| static void | |
| listener_thread (void *args, zctx_t *ctx, void *pipe) | |
| { | |
| void *listener = zsocket_new (ctx, ZMQ_SUB); | |
| zsocket_set_subscribe (listener, ""); | |
| int address; | |
| for (address = 1; address < 255; address++) |
| --- | |
| language: objective-c | |
| before_script: | |
| - ./scripts/travis/add-key.sh | |
| after_script: | |
| - ./scripts/travis/remove-key.sh | |
| after_success: | |
| - ./scripts/travis/testflight.sh | |
| env: | |
| global: |
