At Decompress 2014 I had a play with hooking up a Leap Motion to the CSSConf Australia 2014 giraffes.
See https://www.youtube.com/watch?v=4nM3y8b_rso for a video of them in action.
At Decompress 2014 I had a play with hooking up a Leap Motion to the CSSConf Australia 2014 giraffes.
See https://www.youtube.com/watch?v=4nM3y8b_rso for a video of them in action.
source "https://rubygems.org/" | |
gem "rails", "~> 4.0" | |
gem "sinatra", "~> 1.4" | |
gem "puma" |
My 15 hack for @pasql's and @johnallsopp's Web Directions 2013 workshop exercise, implementing an animation Pasquale had mocked in After Effects.
http://webdirections.org/wds13/ http://www.pasqualedsilva.com/
# Reconfigures ActionDispatch's TLD handling dynamically based on the request | |
# host, so you don't have to mess with config.action_dispatch.tld_length for | |
# cross-device testing using xip.io and friends | |
# | |
# Examples: | |
# use Rack::HostBasedTldLength, /xip\.io/, 5 | |
class Rack::HostBasedTldLength | |
def initialize(app, host_pattern, host_tld_length) | |
@app = app |
# A simple Makefile alternative to using Grunt for your static asset compilation | |
# | |
## Usage | |
# | |
# $ npm install | |
# | |
# And then you can run various commands: | |
# | |
# $ make # compile files that need compiling | |
# $ make clean all # remove target files and recompile from scratch |
require 'sass/importers' | |
# = SASS CSS Importer | |
# | |
# This overrides the Filesystem importer, which is used by Sass to @import | |
# .sass and .scss files from the filesystem, to include .css files as well. | |
# | |
# Once require'd, you can import a "some-stylesheet.css" file by simply doing: | |
# | |
# @import "some-stylesheet"; |
define(function() { | |
/* | |
Require.js loader plugin for the Pin Payments Javascript API | |
Firstly, ensure that your <html> element has the following attributes set: | |
data-pin-api - either "test" or "live" | |
data-pin-publishable-key - your Pin publishable API key |
module.exports = function(grunt) { | |
grunt.initConfig({ | |
// ... | |
sass: { | |
styles: { | |
files: { | |
'sass/styles.css': [ | |
'components/normalize-css/normalize.css', |
Using the OpsWorks dashboard after it's been left for a day:
to which I say:
and then proceed to:
AWS OpsWorks, formerly Scalarium, is a chef-based system that deeply integrates with EC2 (security policies, key pairs, etc). OpsWorks acts as web console to configure your entire system, and as a command hub for running chef-solo on all the instances.
A stack represents a collection of inter-connected and inter-configured services.
A stack has lifecycle events which are triggered by any change to the stack configuration (such as, adding a new instance to a layer, or changing the hosts of an application). In this way, the stack acts as an event hub, notifying every instance of any changes.