package main | |
import ( | |
"database/sql" | |
"fmt" | |
"net/http" | |
"os" | |
"github.com/go-chi/chi" | |
"github.com/go-chi/chi/middleware" |
# Specify the name of the kubernetes context that has permissions to create the service account in your | |
# target cluster and namespace. To get the list of contexts, you can run "kubectl config get-contexts" | |
export CONTEXT="$(kubectl config current-context)" | |
# Enter the namespace that you want to install Spinnaker in. This can already exist, or can be created. | |
export NAMESPACE="spinnaker" | |
# Enter the name of the service account you want to create. This will be created in the target namespace | |
export SERVICE_ACCOUNT_NAME="spinnaker" |
cd ~ | |
mkdir -p $HOME/bin | |
# KUBECTX | |
git clone https://github.com/ahmetb/kubectx.git ~/.kubectx | |
ln -s $HOME/.kubectx/kube $HOME/bin/ | |
ln -s $HOME/.kubectx/kubectx $HOME/bin/ | |
# MICRO | |
wget https://github.com/zyedidia/micro/releases/download/nightly/micro-1.4.2-dev.61-linux64.tar.gz |
# source https://stackoverflow.com/questions/3103589/how-can-i-easily-fixup-a-past-commit?noredirect=1&lq=1 | |
git add . | |
git commit --fixup HEAD | |
git rebase -i --autosquash HEAD~2 |
// run this in the web console when logged in | |
Array.from(document.querySelectorAll('tr.plugin')) | |
.map(x => [x.attributes.name.textContent, x.querySelector('.excerpt').textContent]) |
From time to time, Musk will send out an e-mail to the entire company to enforce a new policy or let them know about something that's bothering him. One of the more famous e-mails arrived in May 2010 with the subject line: Acronyms Seriously Suck:
There is a creeping tendency to use made up acronyms at SpaceX. Excessive use of made up acronyms is a significant impediment to communication and keeping communication good as we grow is incredibly important. Individually, a few acronyms here and there may not seem so bad, but if a thousand people are making these up, over time the result will be a huge glossary that we have to issue to new employees. No one can actually remember all these acronyms and people don't want to seem dumb in a meeting, so they just sit there in ignorance. This is particularly tough on new employees.
That needs to stop immediately or I will take drastic action - I have given enough warning over the years. Unless an acronym is approved by me, it should not enter the SpaceX glossary.
from sys import argv | |
import os | |
import re | |
import subprocess | |
import urllib.request | |
import urllib.parse | |
import youtube_dl | |
from gi.repository import Notify | |