natelandau

#  ---------------------------------------------------------------------------
#
#  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

tsiege

ANNOUNCEMENT

I have moved this over to the Tech Interview Cheat Sheet Repo and has been expanded and even has code challenges you can run and practice against!






\

ChuckJHardy

DigitalOcean Ubuntu 14.04 x64 + Rails 4 + Nginx + Unicorn + PostgreSQL + Capistrano 3

Create a Droplet

SSH into Root

$ ssh [email protected]

Change Root Password

midwire

#!/usr/bin/env bash
# Reset routing table on OSX

# display current routing table
echo "********** BEFORE ****************************************"
netstat -r
echo "**********************************************************"

for i in {0..4}; do
  sudo route -n flush # several times

gwillem

#!/usr/bin/env python3

"""

Parse scan.io archive to find specific HTTP responses.
Will save positive hits to <timestamp>/<ip>.log

Usage: 

$ parse-scans.io.py https://scans.io/data/rapid7/sonar.http/20151110-http.gz

mikesouza

require 'rubygems'
require 'yaml'

# A demonstration of YAML anchors, references and handling of nested values
# For more info, see: 
#   http://atechie.net/2009/07/merging-hashes-in-yaml-conf-files/

stooges = YAML::load( File.read('stooges.yml') )
# =>  {
#             "default" => {

LeCoupa

# Redis Cheatsheet
# All the commands you need to know


redis-server /path/redis.conf  # start redis with the related configuration file
redis-cli                      # opens a redis prompt


# Strings.

HyperBrain

Overview

Currently the Serverless framework only offers lifecycle events that are bound to commands and also are very coarse. Each core plugin only exposes the events that are defined by the framework. This is suboptimal for plugin authors as they want to hook special events within the deployment process.

The PR adds fine grained lifecycles to the AWS deployment process (see below for the current implementation process) and makes the package/deploy plugin implementation non-breaking.

enricofoltran

package main

import (
	"context"
	"flag"
	"fmt"
	"log"
	"net/http"
	"os"
	"os/signal"

bwinant

'use strict';

// This plugin will bind to all available lifecycle events and print them out as they are invoked
class LifecyclePrinter {
    constructor(serverless, options) {
        this.serverless = serverless;
        this.options = options;

        this.provider = this.serverless.getProvider('aws');