You're saying multiple times that the cached values are expired, that's a bit false I think.
The cache key changes and there is no cached value with the new key, but the cached value with the old key is still cached in there. It can grow big if not expired from time to time.
Hum, just wondering, I don't know nginx much, but as the unicorn socket has the app name in it, shouldn't the upstream be something like unicorn_<%= application %> so that there can be more than one ?
You're saying multiple times that the cached values are expired, that's a bit false I think.
The cache key changes and there is no cached value with the new key, but the cached value with the old key is still cached in there. It can grow big if not expired from time to time.
No one mentioned it, but if you sent type="date" HTML5 compatible browsers will give you a datepicker without any need for javascript.
Ok, thanks for testing that :-)
Hum, just wondering, I don't know nginx much, but as the unicorn socket has the app name in it, shouldn't the upstream be something like unicorn_<%= application %> so that there can be more than one ?
I think there are a couple of
.js.coffee
files that have a.rb
extension here.Hum, unless I can't read ActiveRecord::QueryCache, it only clears the query cache if there's an exception, not at every request.
For the routes, I use the js-routes gem quite extensively, it has always worked well for me.
Must be me, but lib/tasks/resque.rake has the content of config/initializers/resque_auth.rb.