ChuckJHardy

class MyJob < ActiveJob::Base
  queue_as :urgent

  rescue_from(NoResultsError) do
    retry_job wait: 5.minutes, queue: :default
  end

  def perform(*args)
    MyService.call(*args)
  end

denji

Moved to git repository: https://github.com/denji/nginx-tuning

NGINX Tuning For Best Performance

For this configuration you can use web server you like, i decided, because i work mostly with it to use nginx.

Generally, properly configured nginx can handle up to 400K to 500K requests per second (clustered), most what i saw is 50K to 80K (non-clustered) requests per second and 30% CPU load, course, this was 2 x Intel Xeon with HyperThreading enabled, but it can work without problem on slower machines.

You must understand that this config is used in testing environment and not in production so you will need to find a way to implement most of those features best possible for your servers.

iwinux

def compile_asset?(path)
  # ignores any filename that begins with '_' (e.g. sass partials)
  # all other css/js/sass/image files are processed
  if File.basename(path) =~ /^[^_].*\.\w+$/
    puts "Compiling: #{path}"
    true
  else
    puts "Ignoring: #{path}"
    false
  end

ddemaree

This code is extracted/adapted from Mat Brown's Sunspot gem. One of Sunspot's nicest features is an expressive DSL for defining search indexes and performing queries. It works by instance_eval-ing a block you pass into it in the context of its own search builder object. In this code, the pig thing1 statement is roughly equivalent to zoo = Zoo.new; zoo.pig(thing1).

Sunspot's DSL has to resort to trickery: the instance_eval_with_context method uses eval to get the block to give up the object it considers to be self, then sets up an elaborate system of delegates and method_missing calls so any methods not handled by the DSL are forwarded to the surrounding object. But as a result, this syntax is minimal and beautiful, and it works the way you expect whether or not you prefer blocks to yield an object.

Without this trick the block would be restricted to either the original, "calling" context (as a closure) or the DSL's "receiving" context (using instance_eval), but not both.

Using `ins

moski

(function () {
  Backbone.syncWithoutUpload = Backbone.sync
  Backbone.syncWithUpload = function(method, model, options) {
	  var methodMap = {
	    'create': 'POST',
	    'update': 'PUT',
	    'delete': 'DELETE',
	    'read'  : 'GET'
	  };
		var type = methodMap[method];

unixcharles

(function () {
  Backbone.syncWithoutUpload = Backbone.sync
  Backbone.syncWithUpload = function(method, model, options) {
    // Create iframe
    var iframe_id = 'file_upload_iframe_' + Date.now()
      , iframe = jQuery('<iframe id="' + iframe_id + '" name="' + iframe_id + '" ></iframe>').hide()

    // Create an hidden form
    var authToken = jQuery('meta[name=csrf-token]').attr('content')
      , authParam = jQuery('meta[name=csrf-param]').attr('content')

jwo

class Api::RegistrationsController < Api::BaseController
  
  respond_to :json
  def create

    user = User.new(params[:user])
    if user.save
      render :json=> user.as_json(:auth_token=>user.authentication_token, :email=>user.email), :status=>201
      return
    else