Slug: jekyll-to-octopress
Date: 2011-09-24
Title: Porting from Jekyll To Octopress
layout: post
Continue reading
Slug: rem-by-listserv
Date: 2011-09-23
Title: R.E.M. by Listserv
layout: post
Continue reading
Slug: chrome-and-popup-windows-in-os-x-lion
Date: 2011-09-23
layout: post
Title: Chrome and Popup Windows in OS X Lion
date: 2011-09-23 18:10
comments: true
categories:
Continue reading
Slug: python-statsd-server
Date: 2011-02-27
Title: Python StatsD Server
layout: post
Thanks to Joshua Frederick (github user jfred), we now have an actual Python implementation of the statsd server, so if you don’t want to install node.js (though why wouldn’t you? :-) ) you can run it all in python.
from pystatsd import Client, Server
# client usage
sc = Client('example.org',8125)
sc.timing('python_test.time',500)
sc.increment('python_test.inc_int')
sc.decrement('python_test.decr_int')
# server usage
srvr = Server(pct_threshold=90,
graphite_port=2003, graphite_host='localhost')
srvr.serve()
Get the code (now version 0.1.1) from
Github or
Pypi
Continue reading
Slug: node-statsd
Date: 2011-02-25
Title: node-statsd
layout: post
Continue reading
Slug: on-a-roll-statsd-from-perl
Date: 2011-02-18
Title: “On a Roll: StatsD from Perl”
layout: post
Apparently I’m having too much fun – I’ve posted a perl client for Etsy’s StatsD on Github.
use Net::StatsD::Client;
my $client = Net::StatsD::Client->new();
$client->timing('perl_test.timing',500);
$client->increment('perl_test.inc_int');
$client->decrement('perl_test.decr_int');
Continue reading
Slug: pystatsd-is-now-on-pypi
Date: 2011-02-17
Title: pystatsd is now on pypi
layout: post
(With apologies to my non-nerd readers…)
Yesterday I got pystatsd pushed up to pypi (pystatsd on pypi), so you can now install it with:
If you installed it already, just use -U:
Continue reading
Slug: statsd
Date: 2011-02-16
Title: Statsd and Python
layout: post
Short version: pystatsd is fire-and-forget site metrics from python, using Etsy’s StatsD and Graphite.
The brilliant devops folks at Etsy released (and posted about) an awesome little node.js-based stats server called statsd.
Statsd sits in front of the Graphite metrics server, providing a simple API for applications to send stats over UDP. UDP is “old tech” but is fire-and-forget – clients don’t have to wait for a response to keep processing.
I took a few hours last night (after reviewing my python socket programming) and ported Etsy’s PHP example to Python. Until (and if) it gets pulled into the main repo, yo can find the python sample client in my Github fork of statsd.
>>> from python_example import Statsd
>>> Statsd.timing('some.time','500|ms')
>>> Statsd.increment('some.int')
>>> Statsd.decrement('some.int')
Stand-alone Client
I reworked this code into a standalone client you can now find
on Github:
>>> from pystatsd import Statsd
>>> statsd_client = Statsd(host, port)
>>> statsd_client.timing('some.time','500|ms')
>>> statsd_client.increment('some.int')
>>> statsd_client.decrement('some.int')
Enjoy!
Continue reading
Slug: related-items-for-movable-type
Date: 2011-02-14
Title: Related Items for Movable Type
layout: post
Continue reading
Slug: set-up-your-own-github-backed-notational-velocity
Date: 2011-02-10
Title: Set up your own Github-backed Notational Velocity
layout: post
When I last posted, I described how I was using a Github-backed wiki as my notes directory in Notational Velocity (and the fork I use, nvalt). That post got some interest, so I decided to try and make the process a bit easier by creating a project for it on GitHub: Veloci-Wiki. In nutshell, once you have a github wiki checked out locally, you checkout Veloci-Wiki and pass the path to your wiki clone to the setup script:
veloci-wiki% perl setup.pl <path/to/your/wiki/clone>
…and Veloci-wiki creates and installs the launchd config file for you, which runs the
vw-update.pl
script (in the veloci-wiki repo) against your wiki checkout anytime a file is changed, added, or removed there, pushing the changes to your Github wiki:

Full instructions are in the
README. Happy hacking, and you can report any issues
on Github, leave a comment, or email me (steveivy @ gmail).
Continue reading