This time it’s more about software than hardware. But first, hardware.
Lightning: We had a lightning strike near our home a few weeks back and my main Windows desktop has been acting dodgy ever since. I swapped the PSU but that didn’t help and finally came to the conclusion that some of the USB ports were damaged on the motherboard. One replacement Gigabyte 970A-DS3P later and all seems to be well. »
Once you get out of the habit of blogging it can take ages to get back in the zone. A week’s vacation this week should do the trick for me. This is partially a link dump and partially the subjects of a bunch of upcoming posts.
Red Hat acquired FeedHenry. I first installed Linux in 2006 when working in San Jose and was a Red Hat user all through those early years and into the initial Fedora years. »
I have long bemoaned Lego’s approach to adding electronics/power to their kits. Technics seems to be its own little sub-section and Mindstorms is a crazy waste of money in an Arduino and Raspberry Pi world. Now that they are the biggest toy company globally, I’d love to see how either of those product ranges are adding to the bottom line.
In that spirit I was very excited about the possibilities of the Lego Batman kit I got in Hamley’s recently. »
Back in 2011, I created a simple scraper in Python to take the river level reported by the Bandon Flood Early Warning System every 15 minutes and save it in Google Fusion Tables. In 2012, I extended it to also save the data on Pachube/Cosm/Xively/Fleeglrheumazoid (or whatever insane name they have this week). So you have 2.5 years of river data in tabular and graphic form.
The code itself is very simple and just involved walking through the page (actually a bloody iframe! »
One small annoyance with the Baseline bolierplate in harp.js is that every blogpost needs to be listed in a file called _data.json with all the relevant metadata. Whilst it’s not a huge job to slug-ify a title and add the ID and epoch time, it’s sufficiently annoying to add friction to me blogging more. Here’s the entry for this blogpost:
"a-simple-nodejs-script-to-setup-a-new-blog-post-in-harpjs": { "ID": 1291, "author": "admin", "date": 1403504847928, "ptype": "post", "description": "This little script generates the relevant metadata in the _data. »
Whilst there are tons of tools to do S3 upload, I wanted something tuned to how I blog, particularly with a static blog that used to be a WordPress one with year/month directories for images.
Usage:
node upload_s3_images.js image1.jpg image2.jpg image3.png etc It uses your AWS credentials in ~/aws_config.json { “accessKeyId”: “akid”, “secretAccessKey”: “secret”, “region”: “us-west-2” }
It uses the bucket name and root upload directory from ./s3_blog_config.json {“bucket”: “conoroneill.net”, “rootUploadDir”: “wp-content/uploads/"} »