codemedic

#!/bin/bash

# Author: Erik Kristensen
# Email: erik@erikkristensen.com
# License: MIT
# Nagios Usage: check_nrpe!check_docker_container!_container_id_
# Usage: ./check_docker_container.sh _container_id_
#
# The script checks if a container is running.
#   OK - running

codemedic

# Change Java Runtime:
sudo update-alternatives --config java

# Delete Open-JDK
sudo apt-get purge openjdk-\* icedtea-\* icedtea6-\*

# Change fonts - remove hinting:
http://askubuntu.com/questions/32624/ugly-fonts-in-netbeans-how-can-i-make-it-use-the-system-font

# Change RubyMine AntiAliasing first:

codemedic

Rate limiting with Redis

June 2011 - Chris O'Hara - (archived original post)

Rate limiting can be an effective way of conserving resources and preventing automated or nefarious activities on your site.

A common use case is to limit the amount of requests an IP can make over a certain time frame. For example, you might want to restrict users from using an expensive search utility on your site. If the user attempts to search more than 5 times a minute, you can redirect them to another page informing them that they need to wait.

IP based rate limiting is already in use on larger sites. Google and Yahoo both employ the technique to prevent (or at least complicate) automated requests to their services.

codemedic

Docker stats collection for collectd

This script can be used to feed collectd with cpu and memory usage statistics for running docker containers using the collectd exec plugin.

This script will report the used and cached memory as well as the user and system cpu usage by inspecting the appropriate cgroup stat file for each running container.

Usage

This script is intented to be executed by collectd on a host with running docker containers. To use, simply configure the exec plugin in collectd to execute the collectd-docker.sh script. You may need to adjust the script to match your particulars, such as the mount location for cgroup.

codemedic

{
  "title": "Collectd: Blackbox",
  "services": {
	"query": {
	  "list": {
		"0": {
		  "query": "plugin:\"load\"",
		  "alias": "Load",
		  "color": "#7EB26D",
		  "id": 0,

codemedic

This is an example of using ELK to parse and view collectd data.

Caveat - I haven't fully tested this mapping yet, it doesn't take into account any other fields that may be added with other collectd plugins, just the ones I have specified below.

codemedic

#!/usr/bin/env ruby

require 'json'
require 'Simplenote'

class ZimDirectory < Hash
  class ZimException < Exception
  end

  attr_reader :dir

codemedic

{
  "path":"/home/foo/icons/",
  "domain":"example.com",
  "icons":[
      {"host":"aaa.example.com", "icon":"red.png"},
      {"host":"bbb.example.com", "icon":"green.png"},
      {"host":"ccc.example.com", "icon":"yellow.png"},
      {"host":"ddd.example.com", "icon":"orange.png"},
      {"host":"eee.example.com", "icon":"blue.png"},
      {"host":"fff.example.com", "icon":"cyan.png"},

codemedic

Keybase proof

I hereby claim:

• I am codemedic on github.
• I am codemedic (https://keybase.io/codemedic) on keybase.
• I have a public key ASBeG9h2YLQvxBVErQ4zzZIlPPBzG1-D3ldD2Pi4zI4S5go

To claim this, I am signing this object:

codemedic

#!/bin/bash

: "${branch:="$(git rev-parse --abbrev-ref HEAD)"}"
: "${tag_or_branch:="$branch"}"

spec=( *spec )
spec=${spec%%.spec}

# Relies on git-describe being functional; so git-flow AVH edition is essential
version="$(git describe --abbrev=0 "$branch")"