Install cask
that extends the brew
command :
brew install phinze/cask/brew-cask
Install calibre
using cask
:
brew cask install calibre
'use strict'; | |
exports.handler = (event, context, callback) => { | |
// Get request and request headers | |
const request = event.Records[0].cf.request; | |
const headers = request.headers; | |
// Configure authentication | |
const authUser = 'user'; | |
const authPass = 'pass'; |
curl -OL http://ftpmirror.gnu.org/libtool/libtool-2.4.2.tar.gz | |
tar -xzf libtool-2.4.2.tar.gz | |
cd libtool-2.4.2 | |
./configure && make && sudo make install | |
# brew install 'https://raw.github.com/simonair/homebrew-dupes/e5177ef4fc82ae5246842e5a544124722c9e975b/ab.rb' | |
# brew test ab | |
curl -O https://archive.apache.org/dist/httpd/httpd-2.4.2.tar.bz2 | |
tar zxvf httpd-2.4.2.tar.bz2 |
Install cask
that extends the brew
command :
brew install phinze/cask/brew-cask
Install calibre
using cask
:
brew cask install calibre
vbell off | |
autodetach on | |
startup_message off | |
shell -$SHELL | |
allpartial off | |
defc1 off | |
defencoding utf8 | |
bind b encoding big5 utf8 | |
bind u encoding utf8 utf8 |
#!/bin/bash | |
# Usage: | |
# | |
# ssl_setup [--self] <name> <csr_config> | |
# | |
# This script is used to generate key and CSR for use HTTPS in Nginx. | |
# | |
# --self Generate self-signed certificate in addition to key and CSR. | |
# name Output files will be named as <name>.key and <name>.csr. |
Uses v0.1-alpha.21
boilerplate.go.txt
/*
Copyright 2017 The Kubernetes Authors.
Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.
In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.
Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j
#!/bin/sh | |
# Usage: | |
# wget -O- https://gist.githubusercontent.com/ifduyue/dea03b4e139c5758ca114770027cf65c/raw/install-proxychains-ng.sh | sudo bash -s | |
set -eu | |
version=4.12 | |
wget https://github.com/rofl0r/proxychains-ng/archive/v$version.tar.gz | |
tar xf v$version.tar.gz |
// some updates for https://rsmitty.github.io/Kubernetes-Events/ | |
// and http://blog.ctaggart.com/2016/09/accessing-kubernetes-api-on-google.html | |
import ( | |
"encoding/base64" | |
"fmt" | |
"log" | |
"net/http" | |
"time" |