FROM alpine:latest | |
LABEL maintainer="[email protected]" | |
ENV SPHINX_VERSION='1.6.4' | |
RUN apk add --update python3 make bash && \ | |
ln -s /usr/bin/python3 /usr/bin/python && \ | |
ln -s /usr/bin/pip3 /usr/bin/pip && \ | |
rm -rf /var/cache/apk/* |
--- | |
apiVersion: v1 | |
kind: ConfigMap | |
metadata: | |
name: l5d-config | |
data: | |
config.yaml: |- | |
admin: | |
ip: 0.0.0.0 | |
port: 9990 |
set -g default-terminal "screen-256color" | |
setw -g xterm-keys on | |
# start window numbering at 1 | |
set -g base-index 1 | |
set -g mouse on | |
setw -g monitor-activity on | |
# use C-j instead of C-b |
Probably one of the easiest things you'll ever do with gpg
Install Keybase: https://keybase.io/download and Ensure the keybase cli is in your PATH
First get the public key
keybase pgp export | gpg --import
Next get the private key
checking build system type... x86_64-unknown-linux-gnu | |
checking host system type... x86_64-unknown-linux-gnu | |
Beginning configuration for readline-7.0 for x86_64-unknown-linux-gnu | |
checking whether make sets $(MAKE)... yes | |
checking for gcc... gcc | |
checking whether the C compiler works... yes | |
checking for C compiler default output file name... a.out | |
checking for suffix of executables... |
I hereby claim:
- I am webframp on github.
- I am sme (https://keybase.io/sme) on keybase.
- I have a public key ASA9asReenv-2MESOFOZ8UTYEBZI2olORsj-gyXB8N6LWAo
To claim this, I am signing this object:
function ConvertTo-CIPolicy { | |
<# | |
.SYNOPSIS | |
Converts a binary file that contains a Code Integrity policy into XML format. | |
Author: Matthew Graeber (@mattifestation) | |
License: BSD 3-Clause | |
.DESCRIPTION |
Especially starting with Windows 10, it isn't all that bad to work on day to day. It just requires a bit of setup out of the box to make it behave better just like those other platforms, and is sufficiently different so as to be non obvious to experienced Linux or macOS users.
Pick and choose what to do from below that fits your needs.
Note: I use emacs, like emacs keybindings and do a bit of Chef development,
A checklist for designing and developing internet scale services, inspired by James Hamilton's 2007 paper "On Desgining and Deploying Internet-Scale Services."
- Does the design expect failures to happen regularly and handle them gracefully?
- Have we kept things as simple as possible?