amuntasim

##Create a migration
### rails g migration make_unicode_friendly

class MakeUnicodeFriendly < ActiveRecord::Migration
  def change
    alter_database_and_tables_charsets "utf8", "utf8_general_ci"
  end

  private
  def alter_database_and_tables_charsets charset = default_charset, collation = default_collation

lsauer

/* lsauer.com, 2015 */
.left-flexible-right-fixed .container {
   height: auto;
   overflow: hidden;
}
.left-flexible-right-fixed .left-inner{
    width: 100%;
}
.left-flexible-right-fixed .right {
    width: 180px;

sindresorhus

#!/usr/bin/env bash
# MIT © Sindre Sorhus - sindresorhus.com

# git hook to run a command after `git pull` if a specified file was changed
# Run `chmod +x post-merge` to make it executable then put it into `.git/hooks/`.

changed_files="$(git diff-tree -r --name-only --no-commit-id ORIG_HEAD HEAD)"

check_run() {
	echo "$changed_files" | grep --quiet "$1" && eval "$2"

jed

How to set up stress-free SSL on an OS X development machine

One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.

Most workflows make the following compromises:

• Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.

• Use production SSL certificates locally. This is annoying

jameslafa

ActiveAdmin.register Project do

  # Don't forget to add the image attribute (here thumbnails) to permitted_params
  controller do
    def permitted_params
      params.permit project: [:title, :summary, :description, :thumbnail, :date, :url, :client_list, :technology_list, :type_list]
    end
  end

  form do |f|

bxt

<?php
/**
 * One-pointer Circular Buffer
 *
 * This comes without any overwrite 
 * checks or FIFO functionality. 
 * You'll need SPL. 
 *
 * @author Bernhard Häussner
 * @date 2011-09-07