Making multiple MySQL versions work with Homebrew was tricky to say the least. Fortunately there are 2 new easy ways that I learned of to achieve this.
As @4unkur and @henrytirla commented below, there is this extremely easy to use app called DBngin, which lets you setup multiple databases (not only MySQL) simultaneously using different ports:
| Use the -f option to git tag: | |
| -f | |
| --force | |
| Replace an existing tag with the given name (instead of failing) | |
| You probably want to use -f in conjunction with -a to force-create an annotated tag instead of a non-annotated one. | |
| Example |
| #!/usr/bin/env bash | |
| # Authorize to GitHub to get the latest release tar.gz | |
| # Requires: oauth token, https://help.github.com/articles/creating-an-access-token-for-command-line-use/ | |
| # Requires: jq package to parse json | |
| # Your oauth token goes here, see link above | |
| OAUTH_TOKEN="34k234lk234lk2j3lk4j2l3k4j2kj3lk" | |
| # Repo owner (user id) | |
| OWNER="your-user-name" |
| #!/usr/bin/env python | |
| #-*- coding:utf8 -*- | |
| # paramiko の ProxyCommandの Sample | |
| # ------------------------------------------------- | |
| # | |
| # ~/.ssh/config | |
| # | |
| # Host proxy-server | |
| # User hoge |
| #!/bin/bash | |
| set -e | |
| set -o pipefail | |
| # Add user to k8s using service account, no RBAC (must create RBAC after this script) | |
| if [[ -z "$1" ]] || [[ -z "$2" ]]; then | |
| echo "usage: $0 <service_account_name> <namespace>" | |
| exit 1 | |
| fi |
| # A part of the Halyard config file declaring the ECR registries. | |
| # There can be multiple registries, each in different AWS account. | |
| # In this example there are 3 "stages" accounts - dev, stage & live. | |
| # NOTE: The declared password files must exist and provide valid base64 encoded values, | |
| # otherwise Halayrd will endup with an exception during deployment. | |
| # The values can be fake, they will be updated later by the Kubernetes Job (see 2-nd attached file). | |
| # NOTE: replace ${YOUR_DEV_AWS_ACCOUNT_ID} ${YOUR_DEV_AWS_REGION} | |
| # with appropriate values (same for STAGE & LIVE). | |
| dockerRegistry: |
Kubernetes is great! It helps many engineering teams to realize the dream of SOA (Service Oriented Architecture). For the longest time, we build our applications around the concept of monolith mindset, which is essentially having a large computational instance running all services provided in an application. Things like account management, billing, report generation are all running from a shared resource. This worked pretty well until SOA came along and promised us a much brighter future. By breaking down applications to smaller components, and having them to talk to each other using REST or gRPC. We hope expect things will only get better from there but only to realize a new set of challenges awaits. How about cross services communication? How about observability between microservices such as logging or tracing? This post demonstrates how to set up OpenTracing inside a Kubernetes cluster that enables end-to-end tracing between serv
| #!/usr/bin/python | |
| import sys | |
| import smtplib | |
| subject = sys.argv[1] | |
| body = sys.argv[2] | |
| recipients = sys.argv[3] | |
| gmail_user = '[email protected]' | |
| gmail_pwd = 'password' |
| import paramiko | |
| k = paramiko.RSAKey.from_private_key_file("/Users/whatever/Downloads/mykey.pem") | |
| c = paramiko.SSHClient() | |
| c.set_missing_host_key_policy(paramiko.AutoAddPolicy()) | |
| print "connecting" | |
| c.connect( hostname = "www.acme.com", username = "ubuntu", pkey = k ) | |
| print "connected" | |
| commands = [ "/home/ubuntu/firstscript.sh", "/home/ubuntu/secondscript.sh" ] | |
| for command in commands: | |
| print "Executing {}".format( command ) |
TL;DR
Install Postgres 9.5, and then:
sudo pg_dropcluster 9.5 main --stop
sudo pg_upgradecluster 9.3 main
sudo pg_dropcluster 9.3 main