Kubernetes dashboard comes pre-installed on each PKS cluster. The following instructions are for how create credentials and obtain the access token. If there is an easier way, please let me know.
This command only needs to be run once.
cat <
#!/usr/bin/env python2.7 | |
""" Print all of the (git/ssh or http) urls for all repos (public or | |
private+public with personal_token) in a GitHub account (user or organization). | |
Usage example:: | |
[HTTP_URLS=1] python2.7 list-all-repos.py account_name [personal_token] | |
It requires the pygithub3 module, which you can install on macos (Mac OSX) like this:: | |
# get pip if you don't have it |
Kubernetes dashboard comes pre-installed on each PKS cluster. The following instructions are for how create credentials and obtain the access token. If there is an easier way, please let me know.
This command only needs to be run once.
cat <
version: '3' | |
services: | |
# FRONT | |
chronograf: | |
# Full tag list: https://hub.docker.com/r/library/chronograf/tags/ | |
image: chronograf | |
deploy: | |
replicas: 1 | |
placement: | |
constraints: |
# ======================================================== | |
# Setup a Dumb AP, Wired backbone for OpenWRT / LEDE | |
# ======================================================== | |
# Set lan logical interface as bridge (to allow bridge multiple physical interfaces) | |
uci set network.lan.type='bridge' | |
# assign WAN physical interface to LAN (will be available as an additional LAN port now) | |
uci set network.lan.ifname="$(uci get network.lan.ifname) $(uci get network.wan.ifname)" | |
uci del network.wan.ifname | |
# Remove wan logical interface, since we will not need it. | |
uci del network.wan |
#!/boot/bzImage | |
# Linux kernel userspace initialization code, translated to bash | |
# (Minus floppy disk handling, because seriously, it's 2017.) | |
# Not 100% accurate, but gives you a good idea of how kernel init works | |
# GPLv2, Copyright 2017 Hector Martin <[email protected]> | |
# Based on Linux 4.10-rc2. | |
# Note: pretend chroot is a builtin and affects the current process | |
# Note: kernel actually uses major/minor device numbers instead of device name |
#Introduction to Devops Resources:
##Chapter 1
2015 State of DevOps Report https://puppet.com/resources/white-paper/2015-state-of-devops-report
Knight Capital https://en.wikipedia.org/wiki/Knight_Capital_Group
Linux source1 3.10.0-327.36.1.el7.x86_64 #1 SMP Sun Sep 18 13:04:29 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux | |
CentOS Linux release 7.2.1511 (Core) | |
NAME="CentOS Linux" | |
VERSION="7 (Core)" | |
ID="centos" | |
ID_LIKE="rhel fedora" | |
VERSION_ID="7" | |
PRETTY_NAME="CentOS Linux 7 (Core)" | |
ANSI_COLOR="0;31" | |
CPE_NAME="cpe:/o:centos:centos:7" |
package main | |
import ( | |
"io/ioutil" | |
"log" | |
"os" | |
"os/user" | |
"strconv" | |
) |
The purpose of this document is to make recommendations on how to browse in a privacy and security conscious manner. This information is compiled from a number of sources, which are referenced throughout the document, as well as my own experiences with the described technologies.
I welcome contributions and comments on the information contained. Please see the How to Contribute section for information on contributing your own knowledge.
I've been asked a few times over the last few months to put together a full write-up of the Git workflow we use at RichRelevance (and at Precog before), since I have referenced it in passing quite a few times in tweets and in person. The workflow is appreciably different from GitFlow and its derivatives, and thus it brings with it a different set of tradeoffs and optimizations. To that end, it would probably be helpful to go over exactly what workflow benefits I find to be beneficial or even necessary.