Jose M Leon leonj1

Workflow Source: https://dzone.com/articles/why-i-never-use-maven-release
git flow tutorial: https://www.youtube.com/watch?v=BYrt6luynCI

TL;DR

git flow release start 6.0.0
git checkout release/6.0.0
mvn versions:set -DnewVersion=6.0.0
git flow release finish 6.0.0
git push origin --all --follow-tags

Adding 2 nodes to an existing 3-node ZooKeeper ensemble without losing the Quorum

Since many deployments may start out with 3 nodes and so little is known about how to grow a cluster from 3 memebrs to 5 members without losing the existing Quorum, here is an example of how this might be achieved.

In this example, all 5 nodes will be running on the same Vagrant host for the purpose of illustration, running on distinct configurations (ports and data directories) without the actual load of clients.

YMMV. Caveat usufructuarius.

Step 1: Have a healthy 3-node ensemble

Deploying a subfolder to GitHub Pages

Sometimes you want to have a subdirectory on the master branch be the root directory of a repository’s gh-pages branch. This is useful for things like sites developed with Yeoman, or if you have a Jekyll site contained in the master branch alongside the rest of your code.

For the sake of this example, let’s pretend the subfolder containing your site is named dist.

Step 1

Remove the dist directory from the project’s .gitignore file (it’s ignored by default by Yeoman).

	curl -O https://releases.hashicorp.com/vagrant/2.0.2/vagrant_2.0.2_x86_64.deb
	curl -O https://releases.hashicorp.com/vagrant/2.0.2/vagrant_2.0.2_SHA256SUMS
	curl -O https://releases.hashicorp.com/vagrant/2.0.2/vagrant_2.0.2_SHA256SUMS.sig
	curl -sS https://keybase.io/hashicorp/key.asc \| gpg --import
	gpg --verify vagrant_2.0.2_SHA256SUMS.sig vagrant_2.0.2_SHA256SUMS
	shasum -a 256 -c <(cat vagrant_2.0.2_SHA256SUMS \| grep 64.deb) -s
	sudo apt install ./vagrant_2.0.2_x86_64.deb

	# setup Idea
	export ANT_OPTS="-Xmx1024m -Xss1g"
	ant idea
	# build
	cd /<source_root>/solr
	ant ivy-bootstrap
	ant compile
	ant server
	# verification
	cd /bin

	#!/bin/bash

	# This is NOT for Raspberry Pi.
	# For RasPi try a diff script in my gists
	apt-get -y remove docker docker-engine docker.io
	apt-get update
	apt-get -y install \
	apt-transport-https \
	ca-certificates \
	curl \

	#!/bin/bash

	sudo curl -sSL https://get.docker.com \| sh
	sudo usermod -aG docker $USER
	# show the installed version
	docker version

	# Boot to recovery mode and disable system integrity protection
	csrutil disable

	# Reboot to regular mode and purge these motherfuckin plists
	sudo rm -f /System/Library/Extensions/IOPlatformPluginFamily.kext/Contents/PlugIns/ACPI_SMC_PlatformPlugin.kext/Contents/Resources/*.plist

	# Reboot to recovery mode and enable system integrity protection
	csrutil enable

	# Reboot

	git branch -m old_branch new_branch # Rename branch locally
	git push origin :old_branch # Delete the old branch
	git push --set-upstream origin new_branch # Push the new branch, set local branch to track the new remote

	#!/bin/bash

	set -e

	TAG=$1
	GIT_MERGE_AUTOEDIT=no
	export GIT_MERGE_AUTOEDIT

	#git checkout develop
	git flow release start ${TAG} \|\| true