Goals: Add links that are reasonable and good explanations of how stuff works. No hype and no vendor content if possible. Practical first-hand accounts of models in prod eagerly sought.
| %%279 : Undefined Access (no effect) Bit 7 | |
| %%1536 : Unused message ID | |
| %%1537 : DELETE | |
| %%1538 : READ_CONTROL | |
| %%1539 : WRITE_DAC | |
| %%1540 : WRITE_OWNER | |
| %%1541 : SYNCHRONIZE | |
| %%1542 : ACCESS_SYS_SEC | |
| %%1543 : MAX_ALLOWED | |
| %%1552 : Unknown specific access (bit 0) |
| dash_id=xxxx | |
| api_key=xxx | |
| app_key=xxx | |
| # 1. export | |
| curl -X GET "https://app.datadoghq.com/api/v1/dash/${dash_id}?api_key=${api_key}&application_key=${app_key}" > dash.json | |
| # 2. edit dash.json | |
| move "graphs", "title", "description" up one level in the json hierarchy, from being beneath "dash" to being at the same level |
| #!/bin/bash | |
| set -e | |
| set -x | |
| # create certs for a kubernetes cluster | |
| usage() { | |
| echo $0 [cluster_name] [service_ip] [additional_names] | |
| echo additional name is generally the dns name | |
| exit -1 | |
| } |
| { | |
| "AWSTemplateFormatVersion": "2010-09-09", | |
| "Description": "An etcd cluster based off an auto scaling group", | |
| "Mappings" : { | |
| "RegionMap" : { | |
| "eu-central-1" : { | |
| "AMI" : "ami-840a0899" | |
| }, | |
| "ap-northeast-1" : { | |
| "AMI" : "ami-6c5ac56c" |
| { | |
| "AWSTemplateFormatVersion": "2010-09-09", | |
| "Description": "CoreOS on EC2 (Hipmunk): http://coreos.com/docs/running-coreos/cloud-providers/ec2/", | |
| "Mappings" : { | |
| "RegionMap" : { | |
| "ap-northeast-1" : { | |
| "AMI" : "ami-1fb9e61e" | |
| }, |
| require 'rubygems' | |
| require 'mechanize' | |
| FIRST_NAME = 'FIRST_NAME' | |
| LAST_NAME = 'LAST_NAME' | |
| PHONE = 'PHONE' | |
| EMAIL = '[email protected]' | |
| PARTY_SIZE = 2 | |
| SCHEDULE_RANGE = { :start_time => '19:00', :end_time => '20:30' } |
| SVNodes = riak_core_vnode_manager:all_vnodes(riak_search_vnode). | |
| GetMIPid = fun(VNodePid) -> element(3,element(4,element(4,element(2,hd(element(2,lists:nth(3,lists:nth(5,element(4,sys:get_status(VNodePid)))))))))) end. | |
| [merge_index:compact(GetMIPid(VNodePid)) || {_,_,VNodePid} <- SVNodes]. | |
| vagrant@vagrant-vm:~$ sudo chef-solo -c /tmp/vagrant-chef-1/solo.rb -j /tmp/vagrant-chef-1/dna.json | |
| vagrant@vagrant-vm:~$ sudo chef-solo -c /tmp/vagrant-chef-1/solo.rb -j /tmp/vagrant-chef-1/dna.json --why-run > /tmp/why-run.out |
Locate the section for your github remote in the .git/config file. It looks like this:
[remote "origin"]
fetch = +refs/heads/*:refs/remotes/origin/*
url = [email protected]:joyent/node.git
Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this: