install and configure docker
curl -sSL https://get.docker.io | bash
mkdir -p /etc/systemd/system/docker.service.d
tee /etc/systemd/system/docker.service.d/kolla.conf <<-'EOF'
[Service]
#compdef openstack aodh barbican ceilometer cinder cloudkitty designate glance gnocchi heat ironic keystone magnum manila mistral monasca murano neutr | |
# https://wiki.openstack.org/wiki/OpenStackClients | |
# http://docs.openstack.org/user-guide/common/cli-install-openstack-command-line-clients.html | |
local curcontext="$curcontext" state line expl ret=1 | |
local -a clnts_compl_new clnts_compl_old clnts_swift_like | |
# |
1.) Download a Nerd Font
2.) Unzip and copy to ~/.fonts
3.) Run the command fc-cache -fv
to manually rebuild the font cache
#!/usr/bin/env sh | |
# Generate an AUTHORS file based on the output of git shortlog. It uses ABC | |
# order, strips out leading spaces and numbers, then filters out specific | |
# authors. | |
git shortlog -se \ | |
| perl -spe 's/^\s+\d+\s+//' \ | |
| sed -e '/^CommitSyncScript.*$/d' \ | |
> AUTHORS |
# PowerView's last major overhaul is detailed here: http://www.harmj0y.net/blog/powershell/make-powerview-great-again/ | |
# tricks for the 'old' PowerView are at https://gist.github.com/HarmJ0y/3328d954607d71362e3c | |
# the most up-to-date version of PowerView will always be in the dev branch of PowerSploit: | |
# https://github.com/PowerShellMafia/PowerSploit/blob/dev/Recon/PowerView.ps1 | |
# New function naming schema: | |
# Verbs: | |
# Get : retrieve full raw data sets | |
# Find : ‘find’ specific data entries in a data set |
Ubuntu 16.04
/etc/systemd/system/certbot.service
[Unit]
Description=Let's Encrypt renewal
[Service]
Type=oneshot
ExecStart=/usr/bin/certbot renew --quiet --agree-tos
if [[ -f "/mnt/c/WINDOWS/system32/wsl.exe" ]]; then | |
# We're in WSL, which defaults to umask 0 and causes issues with compaudit | |
umask 0022 | |
if [[ "${PWD}" = "/mnt/c/Users/${USER}" ]]; then | |
# We're in a default WSL shell | |
cd "${HOME}" | |
fi | |
fi | |
if [[ ! -d "$HOME/.zinit" ]]; then |
The always enthusiastic and knowledgeable mr. @jasaltvik shared with our team an article on writing (good) Git commit messages: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the
SSL Labs
is great, but only support port 443
.