whiteinge

#!/usr/bin/env python
'''\
Welcome to the Salt repl which exposes the execution environment of a minion in
a pre-configured Python shell

__opts__, __salt__, __grains__, and __pillar__ are available.

Jinja can be tested with full access to the above structures in the usual way:

    JINJA("""\\

rgbkrk

#!/usr/bin/env python
# -*- coding: utf-8 -*-

'''

Bootstrapping the salt minions on Rackspace (using fabric rather than
salt-cloud).

This is not the most effective way to do this, but it gets it done.

njpatel

<contents of normal file>
 
# Add any additional locations to look for master runners
runner_dirs: [/srv/runners]
 
# Register a reactor whenever a cloud provider emits 'created'
# the * is the name of the VM, we want any, but you could
# do something like salt/cloud/Webservers-*/created if you only
# wanted your webservers
reactor:

whiteinge

#!/bin/sh
# A self-extracting installer for RPMs
#
# Requires: POSIX env, base64, and mktemp.
#
# To create: make a gzip-compressed tarball of RPMs (with no subdirectory),
# convert to base64, then concatenate onto the end of this file::
#
#   cd /some/directory/of/rpm/files
#   tar -cz *.rpm | base64 -w0 >> selfinstaller.bzx

Kartones

PSQL

Magic words:

psql -U postgres

Some interesting flags (to see all, use -h or --help depending on your psql version):

• -E: will describe the underlaying queries of the \ commands (cool for learning!)
• -l: psql will list all databases and then exit (useful if the user you connect with doesn't has a default database, like at AWS RDS)

akras14

Git Cheat Sheet

Commands

Getting Started

git init

or

UtahDave

#!/bin/sh
# A self-extracting installer for RPMs
#
# To create: make a gzip-compressed tarball of RPMs (with no subdirectory),
# convert to base64, then concatenate onto the end of this file::
#
#   cd /some/directory/of/rpm/files
#   tar -cz *.rpm | base64 -w0 >> selfinstaller.bzx

main() {

vasanthk

System Design Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

Basic Steps

1. Clarify and agree on the scope of the system

• User cases (description of sequences of events that, taken together, lead to a system doing something useful)
  • Who is going to use it?
  • How are they going to use it?

lcherone

#!/bin/bash

#
# Run command in all running containers
# Usage: $ ./lxc-exec-all.sh apt update && apt upgrade
#

for container in $(lxc list volatile.last_state.power=RUNNING -c n --format csv); do    
    lxc exec "$container" "$@"
done

simonw

# Fetch latest configuration:
*/5 * * * * cd /home/ubuntu/dogsheep-config && python3 git_pull_and_run_scripts.py . && sudo python3 ensure_symlinks.py files-to-symlink

# Goodreads
46 * * * * cd /home/ubuntu && /home/ubuntu/datasette-venv/bin/goodreads-to-sqlite books goodreads.db -a auth.json

# Twitter
1,11,21,31,41,51 * * * * /home/ubuntu/datasette-venv/bin/twitter-to-sqlite user-timeline /home/ubuntu/twitter.db -a /home/ubuntu/auth.json --since
2,7,12,17,22,27,32,37,42,47,52,57 * * * * run-one /home/ubuntu/datasette-venv/bin/twitter-to-sqlite home-timeline /home/ubuntu/timeline.db -a /home/ubuntu/auth.json --since
4,14,24,34,44,54 * * * * run-one /home/ubuntu/datasette-venv/bin/twitter-to-sqlite mentions-timeline /home/ubuntu/twitter.db -a /home/ubuntu/auth.json --since