jasonkuhrt

'use strict';

var tcp = require('net');



var s1 = tcp.createServer().listen(9000);
var s2 = tcp.createServer().listen(9001);
var s3 = tcp.createServer().listen(9002);

jasonkuhrt

-e 'a=1' -e 'b=2' -e 'c=3'

jasonkuhrt

# -*- mode: ruby -*-
# vi: set ft=ruby :



# Vagrantfile API/syntax version.
VAGRANTFILE_API_VERSION = "2"

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
  # Configure VM settings for servers running in VirutalBox.

jasonkuhrt

# -*- mode: ruby -*-
# vi: set ft=ruby :



# Vagrantfile API/syntax version.
VAGRANTFILE_API_VERSION = "2"

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
  # Configure VM settings for servers running in VirutalBox.

jasonkuhrt

var r = React
var t = r.PropTypes



module.exports = {
  propTypes: {
    value: t.any,
    onChange: t.func,
    valueLink: t.shape({

jasonkuhrt

• Taking instructions from here https://leanpub.com/purescript/read#leanpub-auto-installing-purescript
• Had to brew unlink haskell-platform
• Had to add ~/Library/Haskell/bin to PATH. See http://stackoverflow.com/questions/18290416/path-for-installation-binaries-for-cabal

Related links:

• purescript/purescript#749
• purescript/purescript#631

jasonkuhrt

Private Registry

The --insecure-registry flag allows a docker daemon to communicate with a docker registry that is not secure.

When using the client to execute $ docker pull or ... push against an insecure registry it will fail unless that registry was listed in the --insecure-registry flag during the booting of the daemon.

A failure may have a pattern like this:

2014/12/09 12:38:13 Error: Invalid registry endpoint https:///v1/: Get https:///v1/_ping: EOF. If this private registry supports only HTTP or HTTPS with an unknown CA certificate, please add `--insecure-registry ` to the daemon's arguments. In the case of HTTPS, if you have access to the registry's CA certificate, no need for the flag; simply place the CA certificate at /etc/docker/certs.d//ca.crt

jasonkuhrt

id: cloud-delivery-test
kind: Pod
apiVersion: v1beta1
desiredState:
  manifest:
    version: v1beta1
    containers:
      - name: cloud-delivery-test
        image: quay.io/littlebits/cloud-delivery-test:4308c23a5bf29be702a64ad92e9cb0d1dac403ad
        # image: $DOCKER_REGISTRY/$DOCKER_REPO:$DOCKER_TAG

jasonkuhrt

$ kubectl version --insecure-skip-tls-verify=true --server=https://146.148.60.38

Client Version: version.Info{Major:"0", Minor:"5", GitVersion:"v0.5", GitCommit:"e2e1c87ae06b303af92fdb5f44af60643d80469e", GitTreeState:"clean"}
Server Version: &version.Info{Major:"0", Minor:"4+", GitVersion:"v0.4.2", GitCommit:"2902951c445da6e6ead9e406b3c8e19bc28c2b4a", GitTreeState:"clean"}

$ kubectl describe pod bitlab-voteview --insecure-skip-tls-verify=true --server=https://146.148.60.38

jasonkuhrt

A direct link to the app running on the pod works:

http://130.211.165.148:7200/primus/primus.js

A direct link to the Kubernetes Service should work but does not:

http://107.178.208.133:7777/primus/primus.js