Comments for Technical Ramblings

Comment on Passenger can’t find Rails by tib

tib — Mon, 08 Aug 2011 13:18:10 +0000

MiddleEarther : I spent a good part of a day reading google posts before I gave up on this… came back to it and your post fixed it. I went and added a line to the boot.rb prior to the complaint about failing to load the gem: $stderr.puts “Actual load error: ” + load_error I really don’t see why rails would ever purposefully obscure the real error – sounds like a mistake.

thanks ! and thanks for the author ! you saved my day ! By the way, I'd like to congratulate the author of the original function, this is just magic ! ^^

Comment on Rails 3 Engines/Plugins and Static Assets by Les Nightingill

Les Nightingill — Sat, 09 Apr 2011 19:08:43 +0000

Well I kinda solved the problem with blank assets, with a bit of hacking. Not sure if there will be side effects but would be interested if others can use this too.

I moved my ::ActionDispatch::Static middleware up in the rack stack. Instead of app.middleware.use (as Jon has suggested, above) I inserted my engine’s static-serving middleware near the top of the rack stack with
app.middleware.insert_before ::Rack::Lock, ::ActionDispatch::Static, “#{root}/public”
and presto!

Comment on Rails 3 Engines/Plugins and Static Assets by Les Nightingill

Les Nightingill — Sat, 09 Apr 2011 18:23:36 +0000

Just to add info to the problems that others (and I) are seeing with blank asset files being delivered…
The engine’s asset files ARE being found (if I try to include a non-existent css file, I get http not found response, but the blank files include http 200, OK, code). But the content is empty!
(OK locally on my dev machine, though).

Comment on Chrome Campfire Notifications by Jon Swope

Jon Swope — Tue, 15 Mar 2011 20:33:48 +0000

I am looking into some way to do this. I’m no longer using Campfire, and don’t think it would be a good idea to pay for a campfire subscription solely to develop this extension. Even if I put the code up on Github, I wouldn’t be able to test contributions before publishing them to the Chrome extension gallery. I’ll likely put the source up and then change the name of the extension so someone else can take over development.

Being an extension, its source is inherently “open” (that is you can poke around at it), if you want to mess with it in the mean time.

Comment on Chrome Campfire Notifications by Brock Bland

Brock Bland — Tue, 15 Mar 2011 18:16:15 +0000

Are you looking to open source the code for this or interested in contributors? I might be willing to help out with some of the requested features and have a few features I’d like to see myself.

Comment on Rails 3 Engines/Plugins and Static Assets by Bala Paranj

Bala Paranj — Sun, 06 Mar 2011 21:59:48 +0000

Symlinks is a workaround and not a ideal solution. Ideally you want a Rack app to handle all the static assets (html, css, js, images etc). Any pointers on how to do that?

Comment on Chrome Campfire Notifications by Jon Swope

Jon Swope — Mon, 07 Feb 2011 21:19:27 +0000

I’ve updated it with an icon in the address bar that allows you to disable/enable notifications, but was waiting for someone to actually say that they needed the persistence options before I implemented them. Guess it’s time to get to work.

Comment on Chrome Campfire Notifications by Gyi Tsakalakis

Gyi Tsakalakis — Mon, 07 Feb 2011 18:32:14 +0000

Thanks for the great campfire extension! Any word on updates? I’d like to be able to change notification settings (i.e. display time, permanency, etc.)

Is there are quick way to make notifications remain permanently on desktop until closed?

you can email me direct at gt[at]attorneysync.com

Comment on Rails 3 Engines/Plugins and Static Assets by cowboycoded.com

cowboycoded.com — Mon, 03 Jan 2011 15:12:47 +0000

Thanks Jon. I found this to be helpful in including some static assets from my engine in my main rails app, but I wanted to append these assets to my main rails app public dir, and not replace the public directory altogether. I ended up using the engine initializer, but I just created symlinks to the files from the plugin directory to the app directory:

initializer “static assets” do |app|
system(“ln -nfs #{root}/public/stylesheets/* #{app.root}/public/stylesheets/”)
system(“ln -nfs #{root}/public/javascripts/* #{app.root}/public/javascripts/”)
end

Comment on Rails 3 Engines/Plugins and Static Assets by Hussein Morsy

Hussein Morsy — Thu, 16 Dec 2010 07:44:02 +0000

In production mode all assets (stylesheets, images, javascripts) from the engines are empty. Any solution ?