lynsei

/****/
  /*  @desc:  jscript using IFF expr to deliver objects in far less code
   *  @vers:  0.1
   *                                                                                                                                                                                                 
   **``~x&*/



/*````````````````````````````````` *``~x&*``
.| IFFE: makey.grid

lynsei

--> ok so I do this: 
aws s3 sync s3://one.region s3://to.another --dryrun --profile pms-east --source-region us-east-1 --region us-west-1 --sse-c AES256 --sse-c-key '496ea1ea1b35561e2342342474db682692a8bbf03f3e22aasdasd1c9fed1a9b605a69137'

--> and on the dry run it says:
"Completed 56 part(s) with ... file(s) remaining
(dryrun) copy: s3://blah to s3://blah2  etc..."

--> when I take off the dryrun I get this on every single file copy when using --sse-c in tandem with --sse-c-key:
"A client error (InvalidArgument) occurred when calling the CreateMultipartUpload operation: 
The secret key was invalid for the specified algorithm."

lynsei

// Load plugins
var gulp = require('gulp'),
    sass = require('gulp-sass'),
    minifyCss = require("gulp-minify-css"),
    autoprefixer = require("gulp-autoprefixer"),
    imagemin = require('gulp-imagemin'),
    notify = require("gulp-notify"),
    rename = require("gulp-rename"),
    cmq = require('gulp-combine-media-queries'),
    uglify = require('gulp-uglify'),

lynsei

# My guide to setting up PGP/OpenPGP keys the correct way

# download gpg-keygen.py python script and run it.  it's slow but it creates your gpg profile the correct way, and that's why it's slow
$ cd ~/; wget https://raw.githubusercontent.com/object-code/gpg-keygen/master/gpg-keygen.py; 


## deploy gpg using latest python scripting methods from gpg-keygen 
$ sudo ~/gpg-keygen.py --t /root/.gnupg/whomever --step generateMasterKey  \
      --master-key-length 4096 \   
      --master-key-type RSA  \

lynsei

##://----------------------------------------------------------------------------------------------------------------
##:// I provisioned a ubuntu 14.4 trusty ec2 instance with 15G space on SSD, then ran the following:
##://----------------------------------------------------------------------------------------------------------------
sudo apt-get update
sudo apt-get install apt-transport-https ca-certificates
sudo apt-key adv --keyserver hkp://p80.pool.sks-keyservers.net:80 --recv-keys 58118E89F3A912897C070ADBF76221572C52609D
sudo vi /etc/apt/sources.list.d/docker.list
sudo apt-get update
sudo apt-get purge lxc-docker
sudo apt-cache policy docker-engine

lynsei

INSTANT RANCHER-SERVER ON AUTOMATED SSL in 10 Lines of Bash Code

# make a rancher-server:443 for ca-validated A+ SSL using Ubuntu-Trusty/jWilder-Nginx-Reverse-Proxy/LetsEncrypt+proxy-companion on AWS EC2 (or basically any cloud host using Ubuntu Trusty)
# by Dr. C.Hogan


# install docker fresh on ubuntu-trusty & set things up proper 
sudo apt-get install apt-transport-https ca-certificates
sudo apt-key adv --keyserver hkp://p80.pool.sks-keyservers.net:80 --recv-keys 58118E89F3A912897C070ADBF76221572C52609D
sudo echo "deb https://apt.dockerproject.org/repo ubuntu-trusty main" >> /etc/apt/sources.list.d/docker.list; sudo apt-get-update

lynsei

// Use Gists to store code you would like to remember later on
console.log(window); // log the "window" object to the console

lynsei

D:\Dockistry-Au\loop-models λ slc loopback

datyl logic:

not cool

     _-----_

lynsei

<template>
  <require from="./dynamic-expression-binding-behavior"></require>
  <require from="./debug"></require>
  
  <label>
    Address 1:
    <input value.bind="model & dynamicExpression:'address.address1'">
  </label>
  <label>
    Address 2:

lynsei

<template>
  <require from="./dynamic-expression-binding-behavior"></require>
  <require from="./debug"></require>
  
  <label>
    Address 1:
    <input value.bind="model & dynamicExpression:'address.address1'">
  </label>
  <label>
    Address 2: