-
Notifications
You must be signed in to change notification settings - Fork 155
RoutingError on all my public/system.... image files #132
Comments
It seems that your images are not served statically (otherwise those requests would not hit Rails routing at all). Could you post relevant config of your web server (apache, nginx or whatever you are using)? |
Ho yes you are totally right. I'm in a transition phase where I try of migrate the application to having all the asset served statically but it is not the case yet. My bad for having say that in the first comment. The thing is that I get this error in development mode. So in this mode there is no apache or nginx involved. |
And you don't happen to have |
I did not set the config.serve_static_assets in my development environment so it has the default value. My app runs just fine. the problems happen when I add delayed_paperclip in my gem file and I bundle install. I do not even have to set the process_in_background to see the problem happening. Here is my development.rb :
Gemfile
|
Maybe you can solve my problem in a different way. I'm using gem 'paperclip-av-transcoder', "0.6.2" for my video processing. I simply need to write this code to have my video converted into many formats:
But this code is synchrone and the user that upload the video is stuck during the conversion. I would like to add an asynch wrapper (worker) around :transcoder so I can call:
I have installed resque and redis and everything work. How can I create this asynch wrapper (worker) around :transcoder ? |
Your issue seems to be the same as #126. Try locking paperclip at 4.2.0 until delayed_paperclip gets patched. |
Nice! thanks it works |
Hi,
I wanted to use delayed_paperclip to relay the processing of video with paperclip-ffmpeg.
My images files are served statically (I bypass rails) so I do not want my images to be affected by delayed_apaperclip.
generate a stack like this on all my pictures when they are loaded on the page:
I use Redis with Resque (I tested this part and everything work)
The text was updated successfully, but these errors were encountered: