twetzel

# Clear existing task so we can replace it rather than "add" to it.
Rake::Task["deploy:compile_assets"].clear 

namespace :deploy do
  
  desc 'Compile assets'
  task :compile_assets => [:set_rails_env] do
    # invoke 'deploy:assets:precompile'
    invoke 'deploy:assets:precompile_local'
    invoke 'deploy:assets:backup_manifest'

melnikaite

# lib/capistrano/tasks/assets.rake

Rake::Task['deploy:assets:precompile'].clear

namespace :deploy do
  namespace :assets do
    desc 'Precompile assets locally and then rsync to remote servers'
    task :precompile do
      local_manifest_path = %x{ls public/assets/manifest*}.strip

clarkware

#!/usr/bin/env ruby

# API Documentation at http://api.wikia.com/wiki/LyricWiki_API

require 'open-uri'
require 'json'
require 'tmpdir'

ARTIST = "Johnny Cash"

driehle

# --------------------------------------------
# This code is for Twitter Bootstrap 2! 
# --------------------------------------------
# 
# The MIT License (MIT)
# Copyright (c) 2012-2015 Dennis Riehle
# 
# Permission is hereby granted, free of charge, to any person obtaining a copy
# of this software and associated documentation files (the "Software"), to deal
# in the Software without restriction, including without limitation the rights

tmcallister

FAYE_TOKEN = 'secretToken'

if defined? Rails

  if Rails.env == 'development'
    FAYE_URI   = "http://#{APP_CONFIG[:nameremoved_service][:host]}:9292/faye"
  else
    FAYE_URI   = "https://#{APP_CONFIG[:nameremoved_service][:host]}/faye"
  end

wycats

# Just wanted to clarify my points at the meetup last night.
#
# There were two different issues intertwined:
# (1) Whether to use extend or "include as extend"
# (2) When using "include as extend", what is the simplest way to achieve the goal?
#
# My personal opinion is that the answer to (1) is "extend", not "include as extend", but that
# is just my personal opinion. My answer to (2) is a more empirical question.

# Using the "extend" approach. Again, I personally prefer the simplicity of this approach, but

chetan

YARD CHEATSHEET http://yardoc.org

May 2020 - updated fork: https://gist.github.com/phansch/db18a595d2f5f1ef16646af72fe1fb0e

cribbed from http://pastebin.com/xgzeAmBn

Templates to remind you of the options and formatting for the different types of objects you might want to document using YARD.

Modules

steve9001

module MyApp
  class Application < Rails::Application
    if Rails.env == 'test'
      require 'diagnostic'
      config.middleware.use(MyApp::DiagnosticMiddleware)
    end
  end
end

guilleiguaran

# coffee_script_tag
# Usage:
#
# <%= coffee_script_tag do %>
#  alert 'Hello World'
# <% end %>
#
#
# You will get in your page:
#

pietern

# Author: Pieter Noordhuis
# Description: Simple demo to showcase Redis PubSub with EventMachine
#
# Update 7 Oct 2010:
# - This example does *not* appear to work with Chrome >=6.0. Apparently,
#   the WebSocket protocol implementation in the cramp gem does not work
#   well with Chrome's (newer) WebSocket implementation.
#
# Requirements:
# - rubygems: eventmachine, thin, cramp, sinatra, yajl-ruby