Oh I see.I thought that had to be there due to issues with init.rb being double loaded - or is that issue fixed now? I still have an entry in my Gemfile...
On Thu, Oct 15, 2009 at 1:29 AM, MarkMT <[email protected]> wrote: > > My understanding was that a change is required in merb-gen so that the > default skeleton application doesn't put cache registration in the > gemfile. > > Nicholas Orr wrote: > > I don't see where I'm suppose to provide this feedback. > > As far as I can tell there is nothing broken, it is purely a lack of > docs... > > > > :/ > > > > On Wed, Oct 14, 2009 at 10:48 PM, Pavel Kunc <[email protected]> > wrote: > > > > > > > > Would it be possible to add this as Lighthouse ticket? So we can track > > > the progress and ideas? Please add your proposed solution as well and > > > we're going to find some sort of solution. I know that I bother > > > everyone to put the issues to the LH but when I'm fixing issues you > > > found I go just to the LH and not the google group. > > > > > > Pavel > > > > > > On Oct 13, 11:25 pm, Nicholas Orr <[email protected]> wrote: > > > > Yeah I spent a bit of time trying to figure out where to put this as > > > > well.Eventually > > > > got it :) > > > > > > > > Merb::BootLoader.after_app_loads do > > > > # This will get executed after your app's classes have been loaded. > > > > Merb::Cache.setup do > > > > register(:layout_haml, Merb::Cache::FileStore, :dir => Merb.root > / > > > "app" > > > > / "views" / "temp") > > > > end > > > > end > > > > > > > > > > > > > > > > On Tue, Oct 13, 2009 at 11:21 PM, Amit <[email protected]> > wrote: > > > > > > > > > Moving the cache registration code to > Merb::BootLoader.after_app_loads > > > > > in init.rb worked. > > > > > I wasted a lot of time trying to figure this out on my own. I think > > > > > this should have been documented, especially when the skeleton app > > > > > generated by merb-gen adds the registration of default cache to > > > > > Gemfile prompting user to modify it in place to make other caching > > > > > stores to work. > > > > > > > > > Amit > > > > > > > > > On Oct 8, 1:04 pm, Amit <[email protected]> wrote: > > > > > > I recently upgraded to Merb 1.1 and am not able to get caching to > > > work > > > > > > ever since. I want to use memcached store. This is what I do > > > currently > > > > > > - > > > > > > > > > > In Gemfile, I have the following lines to register cache store - > > > > > > > > > > gem("merb-cache", merb_gems_version) do > > > > > > Merb::Cache.setup do > > > > > > register(:memcached, > > > > > > Merb::Cache::MemcachedStore, :namespace => "my_app", :servers => > > > > > > ["127.0.0.1:11211"]) > > > > > > end > > > > > > end > > > > > > > > > > And in my controller, I'm just tring to check if the entry exists > in > > > > > > cache using the following line - > > > > > > > > > > if Merb::Cache[:memcached].exists?(api_name, > > > > > > cache_params) > > > > > > > > > > which is resulting in following error - > > > > > > > > > > merb : worker (port 4000) ~ Could not find the :memcached > store - > > > > > > (Merb::Cache::StoreNotFound) > > > > > > > > > > Any idea what could be wrong? This was working perfectly in Merb > > > > > > 1.0.12 where the only difference was that the cache registering > > > > > > statements were in development.rb file. > > > > > > > > > > thanks > > > > > > Amit > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/merb?hl=en -~----------~----~----~----~------~----~------~--~---
