background preloader

Makers of the Riak distributed database

Makers of the Riak distributed database

etsy/deployinator Redis How To Use IndexDB – Code And Example « Ido's Blog IndexedDB is an evolving web standard for the storage of significant amounts of structured data in the browser and for high performance searches on this data using indexes. IndexedDB leaves room for a third-party JavaScript library to straddle the underlying primitives with a BTree API, and I look forward to seeing initiatives like BrowserCouch built on top of IndexedDB. Intrepid web developers can even build a SQL API on top of IndexedDB. I’ve work today to create this example in order to push it to MDC IndexDB page later… I found few things that didn’t work on Firefox 4 (but since we have Firefox 5 from last night) – I’ve just put them in the comments. You can go here and see a working example or browse the code below and get a beer. Here is a code that will show you all the basic features: To check the code with highlights you might want to check The code of this example on github // on errors - show us what is going wrong function idbError_(e) { idbLog_.innerHTML += ' "; return; }

Code as Craft HBase - HBase Home Wealthfront Engineering Document Store Flickr Code Key-value store RunDeck Plugin Plugin Information This plugin is a Notifier that will talk to a RunDeck instance (via its HTTP API) to schedule a job execution on RunDeck after a successful build on Jenkins. It is also a Trigger that will schedule a build on Jenkins after a job execution on RunDeck (using RunDeck WebHook Notification). Table of Contents Use RunDeck is an open-source tool for automating tasks on multiple nodes, with both a CLI and a web-based interface. You have 3 ways to use this plugin : build a "deployment pipeline", (the "0-click deployment process") : you commit a change, Jenkins picks it up, build, test and so on, and then triggers a job execution on RunDeck for deploying your application. Note that you can combine those use-cases. Deployment Pipeline The goal is to have a 0-click deployment process : you commit a change, Jenkins picks it up, build, test and so on, and then triggers a job execution on RunDeck for deploying your application. Configuration Post-deployment job Use Option Provider Links

Related: