Richard Michael richardkmichael

Ember.Console

This is a set of helpers for finding the application's currently active models/routes/controllers/etc. This isn't a straightforward process because of how Ember (rightly) encapsulates application objects, but it's useful in debugging environments to be able to quickly access them. And with the beta release of Ember Data, the store is not easily accessible without helpers either.

Usage

All helpers can be called directly if you provide them an application instance:

KVM OSX Guest 10.11 (El Capitan) with Clover

Some notes about this approach:
- An OSX Installer USB drive for Install OS X El Capitan is created
- Clover is then installed on the USB drive
- Clover Configurator is then run on the USB drive
- The USB drive contents are copied to the VM host
- VNC is used to connect to the guest UI
The qxl virtual video device is used (part of the standard kvm qemu install)

	#!/bin/bash

	# FIXME: Can't node write a PID file? This hopes the current user doesn't run more
	# than one node process.
	kill_node_server() {
	kill -9 $(ps \| grep -m 1 "node" \| cut -c 1-5)
	}

	setup_heroku() {
	gem install heroku -d --no-rdoc --no-ri


	#!/bin/bash
	#
	# pgpool-II replication manager
	#
	# Interfaces with pgpool's pcp command-line tools to provide access to common functions for managing
	# load-balancing and failover.
	#
	# [email protected]
	# 2011-08-28

	/*
	Creates a computed property that persists into local storage, all
	instances share the same value for the same property.

	App.AuthController = Ember.Controller.extend({
	token: Em.computed.stored()
	});

	controller = App.__container__.lookup('controller:auth')
	contorller.set('token', 'abc123foo456bar')