Hi Anvar, As I said before, minigems can only be installed system-wide; this means that you don't have to go to your app folder to manage it. So once you did the steps above, you should indeed run 'minigem prepare ...' - I'm sorry that I forgot about that step before:
sudo rake install minigems; sudo minigem install; sudo minigem prepare merb-core; If however, you bundled your app, you should be able to run 'merb' from 'bin/merb' instead. The last step above isn't needed in that case, since the local bin/merb is already setup to use minigems. The 'prepare' step is meant for system-wide adoption of the 'merb-core' releated bin executables. As you can see I'm using thin on 'merb-core', specifically because this gem has bin executables that need to be adapted; so it's only needed for gems that provide their own executables. Meaning that this isn't needed for gems like merb-auth or any other normal merb-stack component (merb-slices and it's bin/slice is an exception, should you need to run 'slice'). Remember that minigems only aims to improve efficiency for apps or scripts that actually benefit from it, as in our case the 'merb' binary. If you have it setup like this, it should just work. Unless you see a message that RubyGems has been loaded instead, it's indeed using MiniGems. Here's a good alternative that's available with the new merb.thor (0.0.51): sudo merb:stack:minigems install (uninstall is also available) Good luck! - Fabien --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
