Your setup looks fine (FYI I did just push an update to rack mini profiler)
A common reason this happens is resource caching, rails is very aggressive about caching pages using etags and so forth, mini-profiler is aggressive about stopping it.
However if you happen to already have a page cached, mini profiler has no clean way of forcing a local expire.
Can you try:
- browsing to your page in incognito mode, do you see mini profiler (if so do a cache dump)
- check for that the “__profilin=stylin” cookie is being set, if it is, your auth is all good.
- check if you are getting any 404s (using chrome dev tools) to any mp resources. (perhaps they are being blocked)
- look at the html of the page, do you see the profiling snippet at the bottom?
- try disabling whitelist mode in your environment (on a temp basis) to see if it works:
Rack::MiniProfiler.authorization_mode = :allow_all
To run latest git version:
- Pull the code
bundle in the
bundle exec rake build (or
bundle exec rake compile_less)
gem "rack-mini-profiler", :path => "path\to\mini-profiler\Ruby" to your Gemfile