codemedic

/**
 * jQuery Plugin: Table of Contents with Smooth Scrolling
 * @link    http://www.1stwebdesigner.com/css/jquery-plugin-smooth-scrolling/
 * @author  Rochester Oliveira
 */

(function($){
    $.fn.stoc = function(options) {
        //Our default options
        var defaults = {

codemedic

How to use kickstart in VirtualBox

This short howto describes how to install VMs via kickstart in VirtualBox. It's using PXE functionality built into the NAT network mode of the VirtualBox. The following instructions apply to CentOS installation but it should work for any RedHat-based distro.

Prepare directory structure

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 bash

# Link up docker network via IPSec VPN on docker-host.
#
# NOTE: This script can either be "sourced" into your .bashrc or executed directly. Be
# it sourced or executed, the usage syntax below is the same.
#
# Usage: [dry_run=1] [debug=1] vpn-docker-fix [docker-network-1 [docker-network-2 ...]]
#
# Env Variables:

codemedic

#!/usr/bin/env ruby

require 'json'
require 'Simplenote'

class ZimDirectory < Hash
  class ZimException < Exception
  end

  attr_reader :dir