Andrew Gertig gertig

Heroku Release Phase + Review Apps + Rails

This is a simplified, but fairly thorough, set of scripts and configuration to enable Heroku Release Phase for Rails apps. Further, this particular set up plays nicely with Heroku Review Apps in that the release phase script will:

Fail, loudly, if the DB does not yet exist.
Load the DB schema if the current schema version (as determined by bin/rails db:version) is 0.
Run DB migrations otherwise.

For a "normal" app that usually means it will run the DB migrations.

react-arduino

React has revolutionized the way we write user interfaces. It brings an extremely simple mental model to the authoring of UIs. React-native, react-canvas, and other projects have shown us that this model extends beyond the browser DOM.

I believe that this functional, predictable approach can also revolutionize how we build real-world user interfaces.

	Replicate Codex Micro Layer 1 on Layer 2

	This guide is written so it can be given directly to an agent. Its goal is to make Layer 2 behave exactly like the protected Codex Layer 1. Afterward, Layer 2 remains editable in Work Louder Input, so individual keys can be replaced normally.

	This is an unsupported, version-sensitive technique. Back up the configuration and follow the validation steps before writing anything to the device.

	## Expected result

	Layer 2 retains its own name, color, and lighting settings, but gains Layer 1's:

	// If the user has been on the page for over 12 hours, the next link
	// click will do a full page transition to get new code
	import React from "react";
	import { BrowserRouter, useLocation } from "react-router-dom";

	let hour = 3600000;

	export default function StaleAppRouter(props) {
	let [isStale, setIsStale] = useState(false);

	require('./styles.css');

	import React, {Component, PropTypes} from 'react';
	import { connect } from 'react-redux';
	import { meetsPolicy } from 'policies';

	class VisibleToUser extends Component {

	render() {
	let { children, hasUser, type, value, user, action } = this.props;

	<style>
	input[type=checkbox] {
	display: none;
	}

	input[type=checkbox] + label {
	display: inline-block;
	position: relative;
	padding: 6px;
	background-color: white;

	.
	├── actions
	├── stores
	├── views
	│ ├── Anonymous
	│ │ ├── __tests__
	│ │ ├── views
	│ │ │ ├── Home
	│ │ │ │ ├── __tests__
	│ │ │ │ └── Handler.js

	drift.on('ready',function(api, payload) {
	api.showWelcomeOrAwayMessage(<%== @options.to_json %>);
	});

	require('font-awesome/css/font-awesome.css');

	document.body.innerHTML = '<i class="fa fa-fw fa-question"></i>';

	// A simple trigger for the Adafruit Audio FX Sound Board
	// For complete info on the sound board, see https://learn.adafruit.com/adafruit-audio-fx-sound-board/overview

	/*
	This is a simple test of a direct trigger of the Audio FX Sounds Board from an Arduino.

	For my test, I used an Arduino Pro Mini running at 3.3v & 8mHz. Digital pin #4 of the Arduino
	was connected to trigger pin #0 of the Sound Board, and I tied them to a common ground. I powered
	Sound Board via a USB external battery for the initial tests, and the Arduino via the FTDI cable.
	For later tests, I powered the Sound Board via the Arduino's VCC (3v) pin directly.