| FROM armhf/debian:jessie | |
| RUN apt-get update && apt-get install -y \ | |
| libssl-dev \ | |
| logrotate \ | |
| sudo \ | |
| curl \ | |
| jq \ | |
| && rm -rf /var/lib/apt/lists/* |
| FROM ubuntu:16.04 | |
| RUN \ | |
| sed -i 's/# \(.*multiverse$\)/\1/g' /etc/apt/sources.list && \ | |
| apt-get update && \ | |
| apt-get -y upgrade && \ | |
| apt-get install -y build-essential curl && \ | |
| apt-get install -y software-properties-common && \ | |
| curl -sL https://deb.nodesource.com/setup_8.x | bash - && \ | |
| apt-get install -y nodejs |
| #!/bin/bash | |
| # Sometimes you need to move your existing git repository | |
| # to a new remote repository (/new remote origin). | |
| # Here are a simple and quick steps that does exactly this. | |
| # | |
| # Let's assume we call "old repo" the repository you wish | |
| # to move, and "new repo" the one you wish to move to. | |
| # | |
| ### Step 1. Make sure you have a local copy of all "old repo" | |
| ### branches and tags. |
I've been using a lot of Ansible lately and while almost everything has been great, finding a clean way to implement ansible-vault wasn't immediately apparent.
What I decided on was the following: put your secret information into a vars file, reference that vars file from your task, and encrypt the whole vars file using ansible-vault encrypt.
Let's use an example: You're writing an Ansible role and want to encrypt the spoiler for the movie Aliens.
| #!/usr/bin/env node | |
| // Minimal example of loading a PEM certificate using pkijs (in node) | |
| // babel-polyfill needs to be loaded for pkijs | |
| // It uses webcrypto which needs browser shims | |
| require('babel-polyfill') | |
| const Pkijs = require('pkijs') | |
| const Asn1js = require('asn1js') | |
| const FS = require('fs') |
| const fs = require('fs') | |
| const path = require('path') | |
| const process = require('process') | |
| const { spawnSync } = require('child_process') | |
| const { GITHUB_TOKEN, GITHUB_USERNAME, GITHUB_EMAIL } = process.env | |
| // leaving this without https:// in order to reuse it when adding the remote | |
| const gitRepositoryURL = 'github.com/owner/repo-name.git' | |
| const repositoryName = 'repo-name' |
If a project has to have multiple git repos (e.g. Bitbucket and Github) then it's better that they remain in sync.
Usually this would involve pushing each branch to each repo in turn, but actually Git allows pushing to multiple repos in one go.
If in doubt about what git is doing when you run these commands, just
This article will briefly describe how to install SonarQube as Docker container on Amazon EC2 and integrate it with Jenkins.
Go to RDS > Parameter Groups
Create a new Parameter Group with the following parameter:
max_allowed_packet = 268435456
We need to create a new RDS database for SonarQube (you may use an existing MySQL instance)
UPDATE (March 2020, thanks @ic): I don't know the exact AMI version but yum install docker now works on the latest Amazon Linux 2. The instructions below may still be relevant depending on the vintage AMI you are using.
Amazon changed the install in Linux 2. One no-longer using 'yum' See: https://aws.amazon.com/amazon-linux-2/release-notes/
sudo amazon-linux-extras install docker
sudo service docker start