WebPlatformDocs

0 info it worked if it ends with ok
1 verbose cli [ 'node', '/bin/npm', 'install' ]
2 info using npm@1.3.6
3 info using node@v0.10.32
4 verbose node symlink /bin/node
5 info shrinkwrap file "/data/fxa-auth-server/npm-shrinkwrap.json"
6 verbose readDependencies returned deps { 'aws-sdk': 'https://registry.npmjs.org/aws-sdk/-/aws-sdk-2.0.21.tgz',
6 verbose readDependencies returned deps   bigint: 'https://registry.npmjs.org/bigint/-/bigint-0.4.2.tgz',
6 verbose readDependencies returned deps   'binary-split': 'https://registry.npmjs.org/binary-split/-/binary-split-0.1.2.tgz',
6 verbose readDependencies returned deps   'browserid-crypto': 'https://registry.npmjs.org/browserid-crypto/-/browserid-crypto-0.7.0.tgz',

WebPlatformDocs

#!/bin/sh

#
# Source: http://stackoverflow.com/questions/3258243/git-check-if-pull-needed
#
COUNT=$(git rev-list HEAD...origin/master --count)

if [ "$COUNT" -ge  "1" ]; then
    echo 'Must update'
    git pull

WebPlatformDocs

Getting the role list under SaltStack based on the instance name

Idea is that once a VM is instantiated it knows what services he’ll handle.

Canonical

• https://gist.github.com/WebPlatformDocs/563cb12326b92b22a452
• https://gist.github.com/renoirb/b2e0222ad52e5d453298

WebPlatformDocs

<form>
	<fieldset>
		<legend>Check boxes</legend>
		<input type="checkbox" name="check1" id="check1" value="Option 1">
		<label for="check1">Option 1</label><br>
		<input type="checkbox" name="check2" id="check2" value="Option 2" checked>
		<label for="check2">Option 2</label><br>
		<input type="checkbox" name="check3" id="check3" value="Option 3">
		<label for="check3">Option 3</label><br>
		<input type="checkbox" name="check4" id="check4" value="Option 4" checked>				<label for="check4">Option 4</label>			

WebPlatformDocs

<form>
	<fieldset>
		<legend>Check boxes</legend>
		<input type="checkbox" name="check1" id="check1" value="Option 1">
		<label for="check1">Option 1</label><br>
		<input type="checkbox" name="check2" id="check2" value="Option 2" checked>
		<label for="check2">Option 2</label><br>
		<input type="checkbox" name="check3" id="check3" value="Option 3">
		<label for="check3">Option 3</label><br>
		<input type="checkbox" name="check4" id="check4" value="Option 4" checked>				<label for="check4">Option 4</label>			

WebPlatformDocs

<form>
	<fieldset>
		<legend>Radio buttons</legend>
		<input type="radio" name="rad1" id="rad1">
		<label for="rad1">Option 1</label><br>		
		<input type="radio" name="rad2" id="rad2" checked>
		<label for="rad2">Option 2</label><br>
		<input type="radio" name="rad3" id="rad3">
		<label for="rad3">Option 3</label><br>	
		<input type="radio" name="rad4" id="rad4">		

WebPlatformDocs

/**
 * The first commented line is your codelet’s title
 */

p {
	color: #f06;
	font: italic 200% Georgia, serif;
	transition: 1s cubic-bezier(.2,.6,.8,.8);
	width: 400px;
}

WebPlatformDocs

/**
 * The first commented line is your codelet’s title
 */

p {

}

html:hover p {
}

WebPlatformDocs

Based on documentation from ElasticSearch about snapshots

To create backup with ElasticSearch

1. Create on elasticsearch node a backup folder

    mkdir /srv/webplatform/elastic_backup
    chown -R elasticsearch:elasticsearch /srv/webplatform/elastic_backup

WebPlatformDocs

WebPlatform Docs Dream Compute setup

Configuration we are using on DreamCompute to run WebPlatform Docs server setup.

• Salt-Cloud configuration
• cloud-init bootstraper
• ssh jump box configuration