This script will pull down an S3 remote configuration before running any terraform actions. Assumes the following structure:
main.tf
terraform.cfg
env/dev/vars
env/staging/vars
env/whatever/vars
env/whatever/somefile.tf
This script will pull down an S3 remote configuration before running any terraform actions. Assumes the following structure:
main.tf
terraform.cfg
env/dev/vars
env/staging/vars
env/whatever/vars
env/whatever/somefile.tf
# | |
# Makefile to perform "live code reloading" after changes to .go files. | |
# | |
# n.b. you must install fswatch (OS X: `brew install fswatch`) | |
# | |
# To start live reloading run the following command: | |
# $ make serve | |
# | |
# binary name to kill/restart |
# This is an example of the Stack Exchange Tier 1 HAProxy config | |
# The only things that have been changed from what we are running are: | |
# 1. User names have been removed | |
# 2. All Passwords have been remove | |
# 3. IPs have been changed to use the example/documentation ranges | |
# 4. Rate limit numbers have been changed to randome numbers, don't read into them | |
userlist stats-auth | |
group admin users $admin_user | |
user $admin_user insecure-password $some_password |
#!/bin/bash | |
CONSUL="localhost:8500" | |
main() { | |
case "$1" in | |
info) | |
curl -s "$CONSUL/v1/kv/$2" | jq -r .[] | |
;; | |
get) |
- action: ec2_facts | |
- apt: pkg=lvm2 state=present | |
- apt: pkg=mdadm state=present | |
- pip: name=boto state=latest | |
- ec2_vol: instance="{{ hostvars[inventory_hostname]['ansible_ec2_instance-id'] }}" | |
volume_size=20 | |
device_name="{{ item }}" |
There are a lot of ways to serve a Go HTTP application. The best choices depend on each use case. Currently nginx looks to be the standard web server for every new project even though there are other great web servers as well. However, how much is the overhead of serving a Go application behind an nginx server? Do we need some nginx features (vhosts, load balancing, cache, etc) or can you serve directly from Go? If you need nginx, what is the fastest connection mechanism? This are the kind of questions I'm intended to answer here. The purpose of this benchmark is not to tell that Go is faster or slower than nginx. That would be stupid.
So, these are the different settings we are going to compare:
These packages are obsolete! Please use the official packages from http://www.Graylog2.org
=================================================
To setup your computer to work with *.test domains, e.g. project.test, awesome.test and so on, without having to add to your hosts file each time.
{ | |
graphitePort: 2003 | |
, graphiteHost: "127.0.0.1" | |
, port: 8125 | |
, debug: true | |
, backends: ['./backends/graphite'] | |
, histogram: [{ metric: "foo", bins: [0, 10, 20, 30] }] | |
, keyFlush: { | |
interval: "10000" | |
, log: "top-keys.log" |