jwieringa

package resource_proxy_integration

import (
	. "github.com/onsi/ginkgo"
	. "github.com/onsi/gomega"
	"log"
	"net/http"
	"testing"
)

jwieringa

resource "aws_vpc" "main" {
  cidr_block = "10.0.0.0/16"
}

resource "aws_subnet" "main" {
  vpc_id     = "${aws_vpc.main.id}"
  cidr_block = "10.0.1.0/24"
}

resource "aws_security_group" "allow_all" {

jwieringa

A curated list of AWS resources to prepare for the AWS Certifications

A curated list of awesome AWS resources you need to prepare for the all 5 AWS Certifications. This gist will include: open source repos, blogs & blogposts, ebooks, PDF, whitepapers, video courses, free lecture, slides, sample test and many other resources.

---

Index:

jwieringa

#!/usr/bin/env ruby
require "socket"
require "uri"

if ENV["DATABASE_URL"]
  url = URI.parse ENV["DATABASE_URL"]

  puts "Waiting for DB on #{url}..."
  30.times do
    begin

jwieringa

# set up iam users, groups, roles, policies for cross account sts assume role access
# devs have near full rights to dev account, read access to prod with mfa requirement
# works great with a bit of https://github.com/remind101/assume-role for cli switching

# create a thing in one account vs the other

variable "prod_enable_flag" {
    default = {
        stage = 0
        prod = 1

jwieringa

Chromium OS ft. Docker

Chromium OS is cool. Chromium OS with crouton is cooler. Chromium OS with Docker is even cooler. This is specifically a guide for the Chromebook Pixel 2 (2015), but I can't think of any reason it wouldn't work with other devices.

1. Create a build environment
2. Customize the kernel
3. Build Chromium OS
4. Flash Chromium OS to USB
5. Install Chromium OS

jwieringa

#!/bin/bash

DEBUG=1;

if [ "$(id -u)" != "0" ]; then
  echo "This script must be run as root" 1>&2
  exit 1
fi

GREP="`which grep`";

jwieringa

variable "s3_bucket_id" {
  default = "s3-assets"
}

variable "s3_origin_id" {
  default = "S3-assets"
}

resource "aws_cloudfront_distribution" "main" {
  enabled             = true

jwieringa

Installing Fedora 23 on 4th gen (2016) X1 Carbon

(Last updated Apr 29 2016)

If you attempt to install Fedora 23 (any spin) on the 2016 X1 Carbon you'll receive a black screen just after kernel selection. This is caused by a kernel bug. You will need to add intel_pstate=no_hwp to the kernel boot arguments, which you are able to do from the kernel selection screen. After installation you must do this again to boot into the installed OS. Once booted, I recommend adding intel_pstate=no_hwp to your /etc/default/grub and running sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg, which will then cause any kernel to have this parameter added to it.

Once Fedora ships with the upcoming 4.6 kernel (and perhaps a patch to the 4.4 kernel, but that remains to be seen), you should be able to remove this argument.

~~Update Apr 21: The 4.4.7 kernel was released but still has these issues. It appears that the fix will be shipped in the 4.4.8 kernel: htt

jwieringa

resource "aws_security_group" "gocd_agent_elb" {
    name = "gocd-agent-elb-sg"
    description = "Security group for the gocd agent ELBs"
    vpc_id = "${var.vpc_id}"

    tags {
        Name = "gocd agent (ELB)"
    }

    # HTTP - SSL (SERVER TO AGENT)