Jack Fiallos jackfiallos

Multiple SSH Keys settings for different github account

create different public key

create different ssh key according the article Mac Set-Up Git

$ ssh-keygen -t rsa -C "[email protected]"

Multiple SSH Keys settings for different github account

create different public key

create different ssh key according the article Mac Set-Up Git

$ ssh-keygen -t rsa -C "[email protected]"

How to configure multiple deploy keys for different private github repositories on the same computer without using ssh-agent

Let's say alice is a github.com user, with 2 or more private repositories repoN. For this example we'll work with just two repositories named repo1 and repo2

https://github.com/alice/repo1

https://github.com/alice/repo2

You need to be to pull from these repositories without entering a passwords probably on a server, or on multiple servers.

##Windows users:

Download wamp: http://www.wampserver.com/en/
Download and extract cmder mini: https://github.com/cmderdev/cmder/releases/download/v1.1.4.1/cmder_mini.zip
Update windows environment variable path to point to your php install folder (inside wamp installation dir) (here is how you can do this http://stackoverflow.com/questions/17727436/how-to-properly-set-php-environment-variable-to-run-commands-in-git-bash)

cmder will be refered as console

##Mac Os, Ubuntu and windows users continue here:

Create a database locally named homestead utf8_general_ci

Shallow

Real unit test (isolation, no children render)

Simple shallow

Calls:

constructor
render

(wherever it says url.com, use your server's domain or IP)

Login to new server as root, then add a deploy user

sudo useradd --create-home -s /bin/bash deploy
sudo adduser deploy sudo
sudo passwd deploy

And Update the new password

	# post_loc.txt contains the json you want to post
	# -p means to POST it
	# -H adds an Auth header (could be Basic or Token)
	# -T sets the Content-Type
	# -c is concurrent clients
	# -n is the number of requests to run in the test

	ab -p post_loc.txt -T application/json -H 'Authorization: Token abcd1234' -c 10 -n 2000 http://example.com/api/v1/locations/

	version: '2.2'
	services:
	elasticsearch:
	image: docker.elastic.co/elasticsearch/elasticsearch:6.4.1
	container_name: elasticsearch
	environment:
	- cluster.name=docker-cluster
	- bootstrap.memory_lock=true
	- "ES_JAVA_OPTS=-Xms512m -Xmx512m"
	ulimits:

	# Convert the .cer file into a .pem file:
	$ openssl x509 -in aps_development.cer -inform der -out PushChatCert.pem

	# Convert the private key’s .p12 file into a .pem file:
	$ openssl pkcs12 -nocerts -in PushChatKey.p12 -out PushChatKey.pem

	# Finally, combine the certificate and key into a single .pem file
	$ cat PushChatCert.pem PushChatKey.pem > ck.pem

	# At this point it’s a good idea to test whether the certificate works.

	var express = require('express');
	var app = express();
	var fs = require('fs');