strukturedkaos

MailChimp's default popup scripts can break on WordPress sites that use jQuery/jQuery UI unless you include their embed code as the final elements before the closing body tag.

Including them in this way isn't always possible or easy with WordPress.

The code below is an alternative implementation of the loader that forces MailChimp's popup scripts to appear below all other scripts upon page load.

To use it, modify the baseUrl, uuid, and lid attributes with the ones from the original popup script that MailChimp supplies.

strukturedkaos

module Tokenable
  extend ActiveSupport::Concern

  included do
    before_save :ensure_token

    def ensure_token
      generate_token(length: 32) if token.blank?
    end

strukturedkaos

worker_processes  1;

error_log  /usr/local/var/log/nginx.error.log;

events {
    worker_connections  1024;
}

http {
    include            mime.types;

strukturedkaos

# Sets up elasticsearch in Codeship build

set -e
CACHED_DOWNLOAD="${HOME}/cache/elasticsearch-${ELASTICSEARCH_VERSION}.tar.gz"
mkdir -p "${ELASTICSEARCH_DIR}"
wget --continue --output-document "${CACHED_DOWNLOAD}" "https://download.elastic.co/elasticsearch/elasticsearch/elasticsearch-${ELASTICSEARCH_VERSION}.tar.gz"
tar -xaf "${CACHED_DOWNLOAD}" --strip-components=1 --directory "${ELASTICSEARCH_DIR}"
echo "http.port: ${ELASTICSEARCH_PORT}" >> ${ELASTICSEARCH_DIR}/config/elasticsearch.yml
# Copy elasticsearch scripts to elasticsearch config
mkdir ${ELASTICSEARCH_DIR}/config/kevy

strukturedkaos

Setup snapshot repo:

curl -XPUT 'http://localhost:9200/_snapshot/demo_nyc_accidents' -d '{
  "type": "url",
  "settings": {
    "url": "http://download.elasticsearch.org/demos/nycopendata/snapshot/"
  }
}'

strukturedkaos

chruby can be installed in various ways. For OSX, it is as simple as:

brew install chruby

Next, add the two following lines to your shell profile file (.bashrc, .zshrc, etc.)

source '/usr/local/share/chruby/chruby.sh'
source '/usr/local/share/chruby/auto.sh'

strukturedkaos

import Ember from 'ember';


// ==========================================================================
// Project:   Ember EasyForm
// Copyright: Copyright 2013 DockYard, LLC. and contributors.
// License:   Licensed under MIT license (see license.js)
// ==========================================================================

// Version: 1.0.0.beta.1

strukturedkaos

#! /bin/bash

# directory to save backups in, must be rwx by postgres user
BASE_DIR="/var/backups/postgres"
YMD=$(date "+%Y-%m-%d")
DIR="$BASE_DIR/$YMD"
mkdir -p $DIR
cd $DIR

# make database backup

strukturedkaos

# config/routes.rb
get "/doc"     => "docs#show", id: "index"
get '/doc/*id' => 'docs#show'

# app/controllers/docs_controller.rb
class DocsController < HighVoltage::PagesController
  respond_to :html
  layout false

  def show

strukturedkaos

Data Integrity

Programming is hard. We must valiantly fight complexity on a daily basis. Conditional statements quickly increase the complexity of a system. Every time we’re unsure about a value, we add a conditions to decide how to proceed. If only we could become more confident with the state of the system…

Hurrah! Data integrity can give us this confidence. By constraining our data, we can make some assumptions about the state of the system. Gone are the days of guarding potentially nil values. Out with orphaned and duplicate records! Data is the [life] of our software. Let’s take [life] by the reigns.