russ/lacquer

Rails drop in for Varnish support.

lacquer's Issues

not load the static file

not load such kind of file which is basically static files in cahce.rb file
this issue is raised in rails 6

uninitialized constant ActiveSupport::Notifications with 0.5.6 on rails 2.3.14

NameError (uninitialized constant ActiveSupport::Notifications):
  vendor/bundle/ruby/1.9.1/gems/activesupport-2.3.14/lib/active_support/dependencies.rb:469:in `load_missing_constant'
  vendor/bundle/ruby/1.9.1/gems/activesupport-2.3.14/lib/active_support/dependencies.rb:106:in `const_missing_with_dependencies
'  vendor/bundle/ruby/1.9.1/gems/lacquer-0.5.6/lib/lacquer/varnish.rb:17:in `block in purge'
  vendor/bundle/ruby/1.9.1/gems/lacquer-0.5.6/lib/lacquer/varnish.rb:16:in `each'
  vendor/bundle/ruby/1.9.1/gems/lacquer-0.5.6/lib/lacquer/varnish.rb:16:in `all?'
  vendor/bundle/ruby/1.9.1/gems/lacquer-0.5.6/lib/lacquer/varnish.rb:16:in `purge'
  vendor/bundle/ruby/1.9.1/gems/radiant-lacquer-extension-1.0.0/lib/lacquer/resource_controller_extension.rb:29:in `purge_all_p
ages'

Probably introduced by c447853

[Ruby 2.1] send_command failure

Hi, first of all thanks for this great piece of software, we have been using lacquer for some years now and it works really good.

Now we are upgrading our application from ruby 1.8.7 to 2.1 (yes, is hell) and I found that with the newer versions of the gem send_command is failing.

I traced the error to lib/lacquer/varnish.rb line 50. And seems to be related with this commit fe5ff85
Removing the "\n" is making my telnets to fail at authenticating with varnish, so send_command is returning "ERROR"

Adding the removed "\n" seems to fix the error.
Again, I'm not sure if this is a lacquer problem or something changed inside OpenSSL::Digest library (Also OpenSSL::Digest::Digest.new seems to be deprecated on ruby 2.1 and is printing a deprecation warning).

I will try to test this with ruby 1.9 and see If I can replicate the error, but other than that I haven't done much more search. I just thought I should let you know about this problem.

Best regards

Varnish 4 support?

Is this something that will come?

NoMethodError: undefined method `instance' for Capistrano::Configuration:Class

I run through an issue after requiring require 'lacquer/capistrano' .

Here's the trace to the issue

 cap staging deploy --trace
 cap aborted! 
 NoMethodError: undefined method `instance' for Capistrano::Configuration:Class
 /home/pamio/.rvm/gems/ruby-2.1.1/gems/lacquer-0.5.6/lib/lacquer/capistrano.rb:3:in `<top    (required)>'
 /home/pamio/dev/rails_apps/remote/khojguru/Capfile:15:in `require'
 /home/pamio/dev/rails_apps/remote/khojguru/Capfile:15:in `<top (required)>'
 /home/pamio/.rvm/gems/ruby-2.1.1/gems/rake-10.4.2/lib/rake/rake_module.rb:28:in `load'
 /home/pamio/.rvm/gems/ruby-2.1.1/gems/rake-10.4.2/lib/rake/rake_module.rb:28:in `load_rakefile'
 /home/pamio/.rvm/gems/ruby-2.1.1/gems/rake-10.4.2/lib/rake/application.rb:689:in  `raw_load_rakefile'
 /home/pamio/.rvm/gems/ruby-2.1.1/gems/rake-10.4.2/lib/rake/application.rb:94:in `block in load_rakefile'
 /home/pamio/.rvm/gems/ruby-2.1.1/gems/rake-10.4.2/lib/rake/application.rb:176:in `standard_exception_handling'
 /home/pamio/.rvm/gems/ruby-2.1.1/gems/rake-10.4.2/lib/rake/application.rb:93:in `load_rakefile'
 /home/pamio/.rvm/gems/ruby-2.1.1/gems/rake-10.4.2/lib/rake/application.rb:77:in `block in run'
 /home/pamio/.rvm/gems/ruby-2.1.1/gems/rake-10.4.2/lib/rake/application.rb:176:in `standard_exception_handling'
 /home/pamio/.rvm/gems/ruby-2.1.1/gems/rake-10.4.2/lib/rake/application.rb:75:in `run'
 /home/pamio/.rvm/gems/ruby-2.1.1/gems/capistrano-3.3.5/lib/capistrano/application.rb:15:in `run'
 /home/pamio/.rvm/gems/ruby-2.1.1/gems/capistrano-3.3.5/bin/cap:3:in `<top (required)>'
 /home/pamio/.rvm/gems/ruby-2.1.1/bin/cap:23:in `load'
 /home/pamio/.rvm/gems/ruby-2.1.1/bin/cap:23:in `<main>'
 /home/pamio/.rvm/gems/ruby-2.1.1/bin/ruby_executable_hooks:15:in `eval'
 /home/pamio/.rvm/gems/ruby-2.1.1/bin/ruby_executable_hooks:15:in `<main>'

Im on ruby 2.1.1 & rails 4.2.1. Any pointers on this ?

Thanks

Job failed to load: undefined class/module Lacquer::DelayedJobJob

I've updated to the latest gem release, and when I set the backend to delayed job, the varnish purge will not execute with this last_error:

Job failed to load: undefined class/module Lacquer::DelayedJobJob

Any clue? Is there somewhere I need to require the file that defines the DelayedJobJob class?