This config assumes that nginx is run from docker image _/nginx.
docker network create nginx
mkdir -p /etc/myproject/nginx
cd /etc/myproject/nginx
curl -H 'Authorization: token INSERTACCESSTOKENHERE' -H 'Accept: application/vnd.github.v3.raw' -O -L https://api.github.com/repos/owner/repo/contents/path |
'Update or create a stack given a name and template + params' | |
from __future__ import division, print_function, unicode_literals | |
from datetime import datetime | |
import logging | |
import json | |
import sys | |
import boto3 | |
import botocore |
This config assumes that nginx is run from docker image _/nginx.
docker network create nginx
mkdir -p /etc/myproject/nginx
cd /etc/myproject/nginx
#!/bin/bash | |
resourceGroupName="cosmosdbshardedtest" | |
name="mongodboncosmosdb" | |
databaseName="mongodb" | |
collectionName="mongodbcoll" | |
kind="MongoDB" | |
partition="/'\$v'/YourShardID/'\$v'" | |
az login |
Start-Date: 2018-11-19 14:23:29 | |
Commandline: apt-get -y install less vim | |
Install: vim-common:amd64 (2:8.0.0197-4+deb9u1, automatic), vim-runtime:amd64 (2:8.0.0197-4+deb9u1, automatic), vim:amd64 (2:8.0.0197-4+deb9u1), xxd:amd64 (2:8.0.0197-4+deb9u1, automatic), libgpm2:amd64 (1.20.4-6.2+b1, automatic), less:amd64 (481-2.1) | |
End-Date: 2018-11-19 14:23:37 | |
Start-Date: 2018-11-19 14:25:58 | |
Commandline: apt-get remove vim | |
Remove: vim:amd64 (2:8.0.0197-4+deb9u1) | |
End-Date: 2018-11-19 14:25:59 |
import hudson.model.* | |
def q = Jenkins.instance.queue | |
q.items.each { | |
if (it =~ /deploy-to/) { | |
q.cancel(it.task) | |
} | |
} |
def cmd = 'hostname' | |
def sout = new StringBuffer(), serr = new StringBuffer() | |
def proc = cmd.execute() | |
proc.consumeProcessOutput(sout, serr) | |
proc.waitForOrKill(1000) | |
println sout |
PRs are a great way of sharing information, and can help us be aware of the changes that are occuring in our codebase. They are also an excellent way of getting peer review on the work that we do, without the cost of working in direct pairs.
Ultimately though, the primary reason we use PRs is to encourage quality in the commits that are made to our code repositories
Done well, the commits (and their attached messages) contained within tell a story to people examining the code at a later date. If we are not careful to ensure the quality of these commits, we silently lose this ability.