Create a file called /media/state/units/docker-local.service that has the following contents:
[Unit]
Description=docker local
[Service]
PermissionsStartOnly=true
| #!/bin/bash | |
| IFNET="eth0" | |
| IPNET="8.8.8.8" | |
| PORTS="20 21 25 80 8000 8888 12000 12001 12002 12003" | |
| BANLIST="64.205.0.18" | |
| if [ "$1" = "start" ]; then | |
| echo "Starting firewall..." |
| #!/bin/bash | |
| function tip { echo -e '\E[37;44m'"\033[1m$1\033[0m"; } | |
| set +h | |
| umask 022 | |
| export LFS="/srv/lfs/6.6" | |
| export LC_ALL=POSIX | |
| export LFS_TGT=$(uname -m)-lfs-linux-gnu | |
| export PATH=/tools/bin:/bin:/usr/bin |
| HOST=x86_64-unknown-linux-gnu | |
| #TARGET=mips-unknown-linux-gnu | |
| #CROSS_TOOL=$HOME/tmp/mips-2013.05/bin | |
| #CXX=mips-linux-gnu-g++ | |
| #CXXFLAGS="-shared -fPIC -mips32r2 -msoft-float -mabi=32" | |
| #LLCFLAGS="-march=mips -mcpu=mips32r2 -soft-float -mattr=+mips32r2,+o32 -relocation-model=pic -disable-fp-elim -segmented-stacks" | |
| TARGET=arm-unknown-linux-gnueabihf | |
| CROSS_TOOL=$HOME/tmp/rpi-tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin |
| extern mod extra; | |
| use extra::json::*; | |
| /* | |
| * This function manages to do absolutely no copying, which is pretty cool. | |
| * | |
| * "What are all those `'r`s?" you ask. Well, they're liftime parameters. They | |
| * indicate how long something lasts (before it's freed). They can't change how | |
| * long something lives for, they only allow you to tell the compiler stuff it |
These instructions will install salt-master and salt-cloud on recent Ubuntu releases. Consult the SaltStack Installation Documentation should you require instructions for other distributions.
echo deb http://ppa.launchpad.net/saltstack/salt/ubuntu `lsb_release -sc` main | sudo tee /etc/apt/sources.list.d/saltstack.listUnionize lets you connect together docker containers in arbitrarily complex scenarios.
Just check those examples.
Let's create two containers, running the web tier and the database tier:
| function printStackTrace() { | |
| var callstack = []; | |
| var isCallstackPopulated = false; | |
| try { | |
| i.dont.exist+=0; //doesn't exist- that's the point | |
| } catch(e) { | |
| if (e.stack) { //Firefox | |
| var lines = e.stack.split('\n'); | |
| for (var i=0, len=lines.length; i<len; i++) { | |
| if (lines[i].match(/^\s*[A-Za-z0-9\-_\$]+\(/)) { |
| #!/bin/sh | |
| ## Node.js for Raspberry Pi Packaging Script | |
| ## ========================================= | |
| ## Execute this script from within node.js git repo | |
| ## Use like this: | |
| ## ~/node/$ VERSION=v0.10.0 ./buildnode.sh | |
| if [ -z $VERSION ]; then | |
| echo "set the VERSION first" | |
| exit 1 |
| #!/usr/bin/env node | |
| /* | |
| * This module can verify that packages installed during development are | |
| * identical to those installed during deployment. The standard npm shrinkwrap | |
| * only ensures that package versions are the same, but does not verify contents. | |
| * This module checks the shasum of the package tarballs downloaded by npm during | |
| * development and deployment to ensure they are the same. | |
| * | |
| * Usage: |