swrobel

#!/usr/bin/env ruby


def changelog_for_gem(gem)
  changelogs = `bundle exec gem contents #{gem}`.lines.grep(/history|changelog|news/i)
  if changelogs.empty?
    puts "No changelog found for gem #{gem}"

    return nil
  end

kinopyo

Override Devise RegistrationsController

Overview

Here I'll show you

• How to override devise registrations_controller(related to create/update user account)
• How to change redirect path after updating user

Override RegistrationsController

chipotle

# Capistrano Laravel 4 Deployment Tasks
# Watts Martin (layotl at gmail com)
# https://gist.github.com/chipotle/5506641
# updated 14-Aug-2013

# Assumptions:
#
#   - You are using a .gitignore similar to Laravel's default, so your
#     vendor directory and composer(.phar) are *not* under version control
#   - Composer is installed as an executable at /usr/local/bin/composer

mikedamage

#!/usr/bin/env ruby
#
# = Email Ping
#
# Check to see if an email address exists by looking up MX records and connecting
# to the address's home SMTP server. It then starts to send a message to the address
# but quits before the message is actually sent.

require 'resolv'
require 'net/smtp'

branneman

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

const Article = require('../../../../app/models/article');

Those suck for maintenance and they're ugly.

Possible solutions

dideler

TL;DR

Create a backup:

pg_dumpall > mybackup.sql

Perform the upgrade:

sudo pg_dropcluster 9.4 main --stop

johnbintz

# be sure to comment out the require 'capistrano/deploy' line in your Capfile!

# config valid only for Capistrano 3.1
lock '3.2.1'

set :application, 'my-cool-application'

# the base docker repo reference
set :name, "johns-stuff/#{fetch(:application)}"

mfazekas

unless File.exist?('Gemfile')
  File.write('Gemfile', <<-GEMFILE)
    source 'https://rubygems.org'
    gem 'rails', '4.1.8'
    #gem 'rails', '4.2.0.rc3'
    gem 'sqlite3'
    gem 'pg'
    gem 'byebug'
  GEMFILE

jgillman

# Assumes the database container is named 'db'

DOCKER_DB_NAME="$(docker-compose ps -q db)"
DB_HOSTNAME=db
DB_USER=postgres
LOCAL_DUMP_PATH="path/to/local.dump"

docker-compose up -d db
docker exec -i "${DOCKER_DB_NAME}" pg_restore -C --clean --no-acl --no-owner -U "${DB_USER}" -d "${DB_HOSTNAME}" < "${LOCAL_DUMP_PATH}"
docker-compose stop db

robertpainsi

Commit Message Guidelines

Short (72 chars or less) summary

More detailed explanatory text. Wrap it to 72 characters. The blank
line separating the summary from the body is critical (unless you omit
the body entirely).

Write your commit message in the imperative: "Fix bug" and not "Fixed
bug" or "Fixes bug." This convention matches up with commit messages