tonythere

#!/bin/sh

ls Postman*.tar.gz > /dev/null 2>&1
if [ $? -eq 0 ]; then
	echo "Removing old Postman tarballs"
	rm -f $(ls Postman*.tar.gz)
fi

curlExists=$(command -v curl)

tonythere

export MACOSX_DEPLOYMENT_TARGET=11.0
brew install pyenv bzip2 zlib xz [email protected]

## 3.6.8
CFLAGS="-I$(brew --prefix openssl)/include -I$(brew --prefix bzip2)/include -I$(brew --prefix readline)/include -I$(xcrun --show-sdk-path)/usr/include" LDFLAGS="-L$(brew --prefix openssl)/lib -L$(brew --prefix readline)/lib -L$(brew --prefix zlib)/lib -L$(brew --prefix bzip2)/lib" pyenv install --patch 3.6.8 < <(curl -sSL https://github.com/python/cpython/commit/8ea6353.patch\?full_index\=1)

## 3.6.12
CFLAGS="-I$(brew --prefix openssl)/include -I$(brew --prefix bzip2)/include -I$(brew --prefix readline)/include -I$(xcrun --show-sdk-path)/usr/include" LDFLAGS="-L$(brew --prefix openssl)/lib -L$(brew --prefix readline)/lib -L$(brew --prefix zlib)/lib -L$(brew --prefix bzip2)/lib" pyenv install --patch 3.6.12 < <(curl -sSL https://github.com/python/cpython/commit/8ea6353.patch\?full_index\=1)

## 3.7.9

tonythere

FWIW: I didn't produce the content presented here (the outline from Edmond Lau's book). I've just copy-pasted it from somewhere over the Internet, but I cannot remember what exactly the original source is. I was also not able to find the author's name, so I cannot give him/her the proper credits.

---

Effective Engineer - Notes

• By Edmond Lau
• Highly Recommended 👍
• http://www.theeffectiveengineer.com/

What's an Effective Engineer?

tonythere

# Official framework image. Look for the different tagged releases at:
# https://hub.docker.com/r/library/node/tags/
image: node:6

before_script:
  - npm install

# This folder is cached between builds
# http://docs.gitlab.com/ce/ci/yaml/README.html#cache
cache:

tonythere

#!/bin/bash

echo "\n\n--- Killing Stupid Adobe Auto Load Crap ---\n\n"

launchctl unload -w /Library/LaunchAgents/com.adobe.AdobeCreativeCloud.plist
launchctl unload -w /Library/LaunchAgents/com.adobe.AAM.Updater-1.0.plist

echo "\n\n--- Done! ---\n\n"

tonythere

# to generate your dhparam.pem file, run in the terminal
openssl dhparam -out /etc/ssl/dhparam.pem 2048

tonythere

deploy:live:
  image: 1drop/docker:git
  stage: deploy
  when: manual
  environment:
    name: production
    url: https://www.somecustomer.de
  before_script:
    - eval $(ssh-agent -s)
    - ssh-add <(echo "$SSH_PRIVATE_KEY")

tonythere

How to setup Let's Encrypt for Nginx on Ubuntu 16.04 (including IPv6, HTTP/2 and A+ SLL rating)

There are two main modes to run the Let's Encrypt client (called Certbot):

• Standalone: replaces the webserver to respond to ACME challenges
• Webroot: needs your webserver to serve challenges from a known folder.

Webroot is better because it doesn't need to replace Nginx (to bind to port 80).

In the following, we're setting up mydomain.com. HTML is served from /var/www/mydomain, and challenges are served from /var/www/letsencrypt.

tonythere

If anyone is interested in setting up their system to automatically (or manually) sign their git commits with their GPG key, here are the steps:

1. Generate and add your key to GitHub
2. $ git config --global commit.gpgsign true ([OPTIONAL] every commit will now be signed)
3. $ git config --global user.signingkey ABCDEF01 (where ABCDEF01 is the fingerprint of the key to use)
4. $ git config --global alias.logs "log --show-signature" (now available as $ git logs)
5. $ git config --global alias.cis "commit -S" (optional if global signing is false)
6. $ echo "Some content" >> example.txt
7. $ git add example.txt
8. $ git cis -m "This commit is signed by a GPG key." (regular commit will work if global signing is enabled)

tonythere

Key-Type: 1
Key-Length: 2048
Subkey-Type: 1
Subkey-Length: 2048
Name-Real: Root Superuser
Name-Email: [email protected]
Expire-Date: 0