create different ssh key according the article Mac Set-Up Git
$ ssh-keygen -t rsa -C "[email protected]"
| import javax.xml.bind.annotation._ | |
| @XmlRootElement(name = "person") | |
| @XmlAccessorType(XmlAccessType.FIELD) | |
| case class Person(fullname: String, username: Option[String], age: Int) |
create different ssh key according the article Mac Set-Up Git
$ ssh-keygen -t rsa -C "[email protected]"
| #!/usr/bin/env python | |
| # Compare a file on S3 to see if we have the latest version | |
| # If not, upload it and invalidate CloudFront | |
| import fnmatch | |
| import os | |
| import boto | |
| import pprint | |
| import re |
| import scala.concurrent.duration._ | |
| import scala.concurrent.ExecutionContext | |
| import scala.concurrent.Future | |
| import akka.pattern.after | |
| import akka.actor.Scheduler | |
| /** | |
| * Given an operation that produces a T, returns a Future containing the result of T, unless an exception is thrown, | |
| * in which case the operation will be retried after _delay_ time, if there are more possible retries, which is configured through | |
| * the _retries_ parameter. If the operation does not succeed and there is no retries left, the resulting Future will contain the last failure. |
| #!/bin/sh - | |
| #title :backup_neo4j_to_s3.sh | |
| #description :This script is creating a NEO4J Backup through neo4j-backup tool, | |
| # compress the backup folder via LZMA2 algorithm compression, and upload it to AWS S3. | |
| #author :Quentin Rousseau <[email protected]> | |
| #date :2014-07-28 | |
| #version :1.1 | |
| #usage :sh backup_neo4j_to_s3.sh ip port destination | eg. sh backup_neo4j_to_s3.sh 127.0.0.1 6362 /mnt/datadisk/backup | |
| #dependencies :apt-get update && apt-get install p7zip-full && apt-get install awscli. | |
| #============================================================================== |
| --- | |
| sockets: | |
| - id: 'one' | |
| address: '127.0.0.1' | |
| port: '8001' | |
| - id: 'two' | |
| address: '127.0.0.2' | |
| port: '8002' |
I recently needed to apply CORS (Cross Origin Request Scripting) to a project that I'm working on. If found 2 posts that helped to achieve it:
I combined both to solve my problem: I have a User CRUD (Play!) webservice and a (Play!) web app that services a SPA (Single Page Application). The SPA needs to access the CRUD webservice, but to acheive this, I would need to apply some CORS rules on both applications.
| # This file is: ~/.ssh/config | |
| # You may have other (non-CodeCommit) SSH credentials stored in this | |
| # config file – in addition to the CodeCommit settings shown below. | |
| # NOTE: Make sure to run [ chmod 600 ~/.ssh/config ] after creating this file! | |
| # Credentials for Account1 | |
| Host awscc-account1 # 'awscc-account1' is a name you pick | |
| Hostname git-codecommit.us-east-1.amazonaws.com # This points to CodeCommit in the 'US East' region |
These commands generate and use private keys in unencrypted binary (not Base64 “PEM”) PKCS#8 format. The PKCS#8 format is used here because it is the most interoperable format when dealing with software that isn't based on OpenSSL.
OpenSSL has a variety of commands that can be used to operate on private
key files, some of which are specific to RSA (e.g. openssl rsa and
openssl genrsa) or which have other limitations. Here we always use