SocketIO IRC-style Tutorial – Part 2 – Getting started
July 17, 2015
This is the 2nd post in a multi-part tutorial series on Socket.io. See Part 1 here. As with all things in life, code is in a constant state of change. Eventually, this tutorial series will be improved, but so that we can all stay on the same page, let’s start with the same version of code. You can go to ShakataGaNai/socketio-sample/d9b7bcc132 to browse the exact working copy this tutorial is based off of. You should download version d9b7bcc132…zip file as well, to work with locally. The repository only has three important files; app.js — which contains the NodeJS server application, index.html — which is our client side (in browser) application, and package.json — which provides some basics about this app, including the dependencies.
SocketIO IRC-style Tutorial – Part 1 – Intro
July 16, 2015
1 One of the technology things that excites me the most is the use of Websockets to help power the “Real Time Web”. When you use a modern browser and use a web based chat system (like IRCCloud), it very likely uses websockets. Twitter feed constantly updating? Websockets. Facebook feed growing as you waste the day? Websockets. “Real Time” Google Analytics? Websockets. You get the idea, lots of cool things we use every day built for the real time web, many of which probably use websockets. The easiest way to use Websockets with NodeJS (which I’ve been spending some of my free time on over the last year) is a nifty tool called Socket.IO.
Initial publishing of Puppet scripts
April 24, 2012
Once you get to a certain number of servers (virtual, physical, or cloud), you need some manner of centrally managing the machines. Something that will let you install packages and configure them all in some standard way, so you don’t have repeat these steps a hundred times yourself. In my experience, the pay off was less during the initial setup phase (because you’re generally only setting up 1 or 2 machines at a time) and more in the “we need to change something that affects all the machine” phase. Regardless of what phase, Puppet does a great job of helping you out. The last company I worked for did not have much in the way of central management so I started to learn Puppet and deployed it.