Bruce brucemead

Deploying Kubernetes 1.11 on DigitalOcean with Rancher 2.0

This guide will help you add support for DigitalOcean volumes and load balancers to a freshly deployed Kubernetes 1.11 cluster. It assumes you already have a cluster deployed through Rancher, have kubectl set up, and helm installed.

Set up helm

kubectl apply -f helm-rbac.yaml
helm init --service-account tiller

helm-rbac.yaml:

You do not need a separate /boot partition unless you have an LVM setup (used in dm-crypt setups).

Run ubiquity -b to open the installer with the option of skipping grub installation (since we're using systemd-boot).

When you get to the screen "Ubuntu has finished installation" choose Continue testing.

Open a Terminal.

Chroot into the new system.

npm v3.10 - ◾

⚠️ This gist is outdated, but most of the commands are still relevant. ⚠️

Update npm itself

npm install -g npm
# Downgrade to a specific version
npm install -g npm@6

To use this hook:

add the prepare-commit-msg file at .git/hooks/prepare-commit-msg and edit as needed
make it executable: chmod +x .git/hooks/prepare-commit-msg
disable fast-forward merges: git config branch.master.mergeoptions "--no-ff"
that's it!

NOTE: after a failed merge from a forbidden branch, the working tree will still be in a MERGING state. To discard the local working copy state, run: git reset --merge

	stages:
	- get_reference
	- regression_test
	- publish

	backstopjs_reference:
	stage: get_reference
	image:
	name: backstopjs/backstopjs:latest
	entrypoint: [""]

	#!/bin/bash

	# Copyright © 2017 Google Inc.
	# Licensed under the Apache License, Version 2.0 (the "License");
	# you may not use this file except in compliance with the License.
	# You may obtain a copy of the License at
	#
	# http://www.apache.org/licenses/LICENSE-2.0
	#
	# Unless required by applicable law or agreed to in writing, software

	# wp-secure.conf
	#
	#
	# This file includes common security considerations for wordpress using nginx.
	#
	# The goal is to block actions which are usually dangerous to wordpress.
	# Additionally, we block direct access to PHP files and folders which should not
	# be accessed directly from a browser.
	#
	# Also have included exceptions for plugins that are known to require this access.

	url - https://aws.amazon.com/blogs/security/a-safer-way-to-distribute-aws-credentials-to-ec2/

	Finding hard-coded credentials in your code
	Hopefully you’re excited about deploying credentials to EC2 that are automatically rotated. Now that you’re using Roles, a good security practice would be to go through your code and remove any references to AKID/Secret. We suggest running the following regular expressions against your code base:

	Search for access key IDs: (?<![A-Z0-9])[A-Z0-9]{20}(?![A-Z0-9]). In English, this regular expression says: Find me 20-character, uppercase, alphanumeric strings that don’t have any uppercase, alphanumeric characters immediately before or after.
	Search for secret access keys: (?<![A-Za-z0-9/+=])[A-Za-z0-9/+=]{40}(?![A-Za-z0-9/+=]). In English, this regular expression says: Find me 40-character, base-64 strings that don’t have any base 64 characters immediately before or after.
	If grep is your preferred tool, run a recursive, Perl-compatible search using the following commands

	# filter by request host header
	varnishlog -q 'ReqHeader ~ "Host: example.com"'

	# filter by request url
	varnishlog -q 'ReqURL ~ "^/some/path/"'

	# filter by client ip (behind reverse proxy)
	varnishlog -q 'ReqHeader ~ "X-Real-IP: .*123.123.123.123"'

	# filter by request host header and show request url and referrer header

	<?php
	require_once 'abstract.php';

	class Mage_Shell_CheckImages extends Mage_Shell_Abstract
	{
	const CATALOG_PRODUCT = '/catalog/product';

	const CACHE = '/cache/';

	protected function _glob_recursive($pattern, $flags = 0)