Authentication is handled by http headers.
- X-Points-Key
- X-Points-Secret
#!/usr/bin/env bash | |
rm -rf extensions | |
mkdir -p extensions | |
rm -rf build/packages | |
mkdir -p build/packages | |
function build_version() { | |
PHP_VERSION=$1 |
import cookie from 'cookie-cutter'; | |
App.on('before:start', () => { | |
//Safari does not respect P3P policies by default and blocks all 3rd party cookies (which is what our cookie is when | |
//loaded in an Iframe). To work around this we need to open a window to our application and set the cookies then | |
//close it. Safari allows us to interact with cookies that have already been set (but not create new ones). | |
if (cookie.get('expected_cookie') === undefined) { | |
//However, Safari (like all browsers) puts the kibosh on all windows that open without user interaction! | |
//Therefore we intercept all clicks to open the short-lived window that initializes all of our cookies. | |
$(document.body).one('click', '[data-goto]', e => { |
#!/bin/sh | |
make clean | |
./vcsclean | |
./buildconf | |
YACC=/usr/local/opt/bison27/bin/bison ./configure --enable-debug --enable-phpdbg "$@" |
Authentication is handled by http headers.
var Style = React.createClass({ | |
render: function() { | |
var style = assign({}, this.props); | |
delete style.children; | |
return React.createElement( | |
'div', | |
{style: style, children: this.props.children} | |
); | |
} |
# --------------------------------------------------------------------------- | |
# | |
# Description: This file holds all my BASH configurations and aliases | |
# | |
# Sections: | |
# 1. Environment Configuration | |
# 2. Make Terminal Better (remapping defaults and adding functionality) | |
# 3. File and Folder Management | |
# 4. Searching | |
# 5. Process Management |
<?php | |
trait Gettable { | |
/** | |
* Retrieve private attributes. | |
* Attributes should be protected | |
* so they cannot be *set* arbitrarily. | |
* This allows us to *get* them as if they | |
* were public. |
<?php | |
HTML::macro('clever_link', function($route, $text) { | |
$active = null; | |
if (Request::path() == $route) { | |
$active = 'active'; | |
} | |
return HTML::link($route, $text, ['class' => 'list-group-item ' . $active]); | |
}); |
set nocompatible " Disable vi-compatibility | |
set t_Co=256 | |
colorscheme xoria256 | |
set guifont=menlo\ for\ powerline:h16 | |
set guioptions-=T " Removes top toolbar | |
set guioptions-=r " Removes right hand scroll bar | |
set go-=L " Removes left hand scroll bar | |
set linespace=15 |
Create the appropriate VPC that your application is going to live in. Create subnets for each availability zone you want to use.
Create VPC security group(s) for your auto-scaling instances. For example, if you're going to auto-scale web servers, create a "web" VPC security group.
Go into AWS console and create an ELB. Easy wizard. Select HTTP and (if needed) HTTPS. Make sure it's associated with the VPC you created in step 1.
Create an auto-scaling launch configuration from the CLI. The launch configuration has the AMI, size, and security group from step #2. The security group must be by ID not name ("sg-12345"):
as-create-launch-config web --image-id ami-2e31bf1e --instance-type m1.medium \
-g sg-7619041a --key root