Don't instantiate Resque::Server in routes

It still works, and it cleans up the output of `rake routes`.

Don't instantiate Resque::Server in routes
It still works, and it cleans up the output of `rake routes`.
Robert Speicher
1 parent caef9ed1
Showing 1 changed file with 1 additions and 1 deletions Show diff stats
config/routes.rb
@@ -10,7 +10,7 @@ Gitlab::Application.routes.draw do
   # Optionally, enable Resque here
   require 'resque/server'
-  mount Resque::Server.new, at: '/info/resque', as: 'resque'
+  mount Resque::Server => '/info/resque', as: 'resque'
   # Enable Grack support
   mount Grack::Bundle.new({
	@@ -10,7 +10,7 @@ Gitlab::Application.routes.draw do		@@ -10,7 +10,7 @@ Gitlab::Application.routes.draw do
10		10
11	# Optionally, enable Resque here	11	# Optionally, enable Resque here
12	require 'resque/server'	12	require 'resque/server'
13	- mount Resque::Server.new, at: '/info/resque', as: 'resque'	13	+ mount Resque::Server => '/info/resque', as: 'resque'
14		14
15	# Enable Grack support	15	# Enable Grack support
16	mount Grack::Bundle.new({	16	mount Grack::Bundle.new({