I am pleased to announce the next release of Buri, version 0.30.
We have new demonstration application it can deploy, lots of fixes, and a shiny new front-end which has a cleaner look, and built-in help on the various commands/actions Buri supports. There are new roles, a new class of role for generic java daemons, and a focus on supporting Cassandra 2.0 where we can.
Read on for more about this release.
As of the v0.20 release of Buri, we can now build all of the @Netflix stuff from GitHub at build time, or fetch binaries from a URL as before. Each role supporting source build provides a task sequence in tasks/acquire_build.yml, which downloads or builds each item. There are some similarities between some builds, but there is a fair bit of variance too, so each gets a custom “job”.
Read on for more about this release.
With the new feature for doing slide decks in the latest release of Dr. Henry, I’m moving my slides on NetflixOSS to a new location here, and publishing a now probably a bit-dated set on Google publisher tag insertion from August 2013.
More decks to come. And some kind of index to find them, which is the next direction for Dr. Henry, to get navigation/flow improvements, better control over it, more uniform handling between themes, and so on.
If you want to know more about how simple deck authoring is with the templating now in Dr. Henry is, check out the release note for version 0.1.1
This release of Buri contains mostly a re-work of how Buri sees “environment”, which is meant mostly to allow separation of VM from AMI provisioning.
The key goal of this release was to get a simple process by which to generate a virtual machine containing all of Flux Capacitor and the various supporting roles to run it. This has been achieved and is detailed in the README.md file of Buri on how to setup your own VM and do basic testing against it.
There is some work to be done to bring the AMI generation documentation up to date with the changes that have occurred around configuring the builds. This will catch up over the next week or two as we bring more of the roles developed against the VM closer to being EC2 ready.
Please give it a try, I’d love any feedback, problem reports, etc, so if this is an area of interest for you, please give it a try, favourite the project in GitHub and spread the word.
First, pop a tab with the demo player and get some music going.
jsSID is a javascript port of several emulations of the SID sound generator chip as used in the Commodore 64. These are native rewrites in javascript vs. using an asm.js compiler. They were written in September 2013, and recently cleaned up and released June 29, 2014.
The emulations converted include:
Read on to learn more about jsSID, or just enjoy the music. :)
Welcome to my GitHub hosted blog! The one I will actually use, and post things on, and twitter them or whatever.
It’s mostly going to be about various things typical of what you might find on someones GitHub account, some others, less so. As this is this first post, there is not much here as of yet. Updates on projects and other things related to these interests will be the main focus of it’s content.
And contrary to what you might think if you read this whole post, I actually want to do some things that are accessible to people getting into programming. Like this blog, as in the engine that drives it. It’s actually really easy to use it to make a blog. And anyone who doesn’t already know Git or other software configuration management will get to know the basic operations of it, if they get to know how to blog with it. Sneaky. Anyway more on that below.
I have recently decided to embrace using GitHub and push out all the various silly projects I have, for whatever reason hesitated to publish before now, I am in the process of preparing them for uploading here, for anyone who finds them of use.
I’ve been using GitHub, and other software configuration management systems for nearly 20 years, even built my own private work alike to GitHub using Redmine, which eventually I will publish the recipe for. But anything I want to put out to the public, I am going to push to here going forward.
I didn’t want to maintain my own infrastructure, or require much in the way of specific tooling to work with the blog. I found a way to do it using just git and and editor with GitHub Pages. (Or in ways that are both more, and less convenient, using just their website.)
Read on if you care to learn more about how I host this blog, and other projects I working on.