The 6th incarnation of Elmer's blog
Runnable creates full-stack environments for every branch across all your GitHub repositories. These environments can be used to integrate and test branches end-to-end, before they’re merged into master.
Watch the 90 second video and browse through our feature tour.
— Runnable Sandboxes: Full-stack environments for every GitHub branch http://blog.runnable.com/post/141200219146/runnable-sandboxes-full-stack-environments-for
This looks interesting especially as we move to new platforms.
While Kubernetes is designed to run across large clusters, it can be useful to have Kubernetes available on a single machine. This guide walks a deployer through this process using Vagrant and CoreOS. After completing this guide, a deployer will be able to interact with the Kubernetes API from their workstation using the kubectl CLI tool.
Source: Kubernetes on Vagrant (Single Machine)
Docker vs. Vagrant
Source: [Infographic] Docker vs. Vagrant
There is a difference and it’s important.
An Introduction to Programming in Go | Go Resources http://www.golang-book.com/books/intro
Calibre 2.53 adds style transformation tool to e-book editor and converter – TeleRead News: E-books, publishing, tech and beyond http://www.teleread.com/calibre-2-53-adds-style-transformation-tool-e-book-editor-converter/
So blockchains make sense for databases that are shared by multiple writers who don’t entirely trust each other, and who modify that database directly. But that’s still not enough. Blockchains truly shine where there is some interaction between the transactions created by these writers.
— Avoiding the pointless blockchain project | MultiChain http://www.multichain.com/blog/2015/11/avoiding-pointless-blockchain-project/
This article has some of the best thinking I’ve seen about how to figure out what to do with blockchain. Blockchain all the things really isn’t a good idea here. This is a complex set of technologies that have any number of useful applications, but, like any tool, it needs to used properly.
FFR: The database preferences for locally hosted Drupal sites running in Acquia Dev Desktop are located in the .acquia/DevDesktop/DrupalSettings folder in your home directory. On Widnows that’s /Users/YourName/. This is especially important if you’ve just imported a Drupal site from elsewhere that has it’s own settings.php that will be left in the structure but ignored. Things like db table prefixes are not picked up in the import process and you’re on your own to track things down to make the site run locally.
Using AWS Lambda for cheap S3 content processing | docs.scanii.com http://docs.scanii.com/articles/aws-lambda-for-cUsingheap-s3-content-processing.html
PHP MySQL JSON Manager: Build and Execute SQL queries with results in JSON – PHP Classes http://www.phpclasses.org/package/9512-PHP-Build-and-Execute-SQL-queries-with-results-in-JSON.html
jiahaog/nativefier: Wrap any web page natively without even thinking, across Windows, OSX and Linux https://github.com/jiahaog/nativefier
