The aim of this guide is to get people getting started with Node.js and npm, while also showing some of the handy commands I use to bootstrap my projects.
Create your project directory.
mkdir npmtest Change to the directory you just created.
cd !$ Tell git to make a repo.
git init Pull down a preconfigured .gitignore file for node projects from github.
wget https://raw.githubusercontent.com/github/gitignore/master/Node.gitignore -O .gitignore Pull down a basic Makefile I use for my projects.
I am currently working on building a simple wireless sensor using the ATmega256RFR2 Xplained Pro Evaluation Kit. This kit includes a base board and a bunch of other peripherals to mess around with.
When I started reading up on the kit I noticed it required windows to install some 600mb + more IDE (gasp), to hack on a small micro controller. This really didn’t gel with me, especially considering said IDE:
Recently I started work for a new employer who runs has a number of applications hosted on Heroku, my typical strategy when faced with a new environment and systems is try and get some monitoring in place as soon as possible. I do this for a few reasons:
It enables me to establish a baseline for performance and behavior of the system. It lets me quickly zero on any areas I can help with.
The aim of this post is to guide the reader through the process of installing ruby 2.0.0 into rbenv with dtrace probes enabled. As rbenv uses ruby-build, which currently downloads and compiles a copy of openssl rather than using the one homebrew i prefer to use the homebrew one.
Note that you MUST install xcode before installing anything, then install homebrew, rbenv, and lastly openssl.
ruby -e "$(curl -fsSL https://raw.github.com/mxcl/homebrew/go)" brew install rbenv brew install openssl Next to overcome the fact that OSX doesn’t have an openssl ca certificate bundle, use the following brew to create and maintain one using the CA certs stored in your keychain.
For some time I have had a Raspberry Pi languishing on my desk, like many I bought one early on and played around with it for a while and then got busy with other stuff. Recently however I have been looking into distributed sensor networks which led me to consider how I could use the Raspberry Pi to aid in my research. If I could get a number of these devices connected up together gathering some measurements of some sort, I could a) make some graphs, b) produce some useful test data and c) get some real world experience with sensor networks.
To start with a little background, then I will outline the options for authentication of HTTP based server APIs with a focus on HMAC and lastly I will provide some tips for developers building and using HMAC based authentication.
Recently I have been doing quite a bit of research and hacking in and around server APIs. Authentication for these type APIs really depends on the type of service, and falls into a couple of general categories:
The latest release of the Ruby plugin I develop for Atlassian Bamboo now includes some new configuration options for Bundler along with a number of other additions and improvements. In this post I want to focus on the new options available in the Bundler task, and illustrate how they are used to make Ruby builds simpler.
In the past with my plugin the administrator of the CI server had two options when managing the gems associated with a build:
I have been working on an update of my Bamboo ruby plugin which uses bundler to install all the gems for a given project within the working copy of the project and then run rake using these gems.
The aim of this post is to illustrate how this is done and how to craft an environment to run ruby once gems are “staged” within a working copy.
The aim of this post is to illustrate how a rails project is staged using bundler without installing any gems in the base ruby installation.
Having recently developed a plugin (Ruby Rake Plugin) for Atlassian’s Bamboo continuous integration (CI) server I thought I would put together a list of tips for those looking to do the same. As there are some great documents provided by Atlassian on how to get started with plugin development I am not going to go into a lot of detail in this area, it is assumed you already messed around a bit with the Plugin SDK.