that makes a lot of sense as i was already beginning to struggle with
keeping gem versions consistent between developers, test and production.

thanks for the link

Levi Rosol




On Tue, Nov 11, 2008 at 12:15 PM, Carl Fyffe <[EMAIL PROTECTED]> wrote:

>
> For gems you usually just have to install them on the machine. However
> the GitHub guys suggest putting everything in vendor:
> http://errtheblog.com/posts/50-vendor-everything
>
> They also cover a couple of other approaches. Since you are new to RoR
> I would suggest reading as much of the errtheblog as you can. They
> give good tips on how to handle many tricky situations. You might
> learn some neat Ruby tricks along the way as well.
>
> Hope that helps,
>
> Carl
>
> On Tue, Nov 11, 2008 at 12:04 PM, Levi Rosol <[EMAIL PROTECTED]> wrote:
> > Carl-
> >
> > Sorry to jump in here, but I'm curious. How should you install your
> plugins
> > for an easy deployment? I have a feeling I will run into a similar issue
> > once I deploy as everything i've installed is sitting in the gems folder,
> > not in the plugins folder. bare in mind that I'm new to ror, so what
> would
> > be the proper command to install say, haml.
> >
> > I do know that when i pulled down my src code to a second machine, i
> needed
> > to setup everything again. Will i need to do that when going to prod? i
> > assume there's a better, programatic way to handle this.
> >
> > thanks!
> >
> > Levi Rosol
> >
> >
> >
> >
> > On Tue, Nov 11, 2008 at 7:59 AM, Carl Fyffe <[EMAIL PROTECTED]>
> wrote:
> >>
> >> It seems that the plugins are not being saved to your repository in a
> >> way that allows them to be retrieved. How are you installing your
> >> plugins?
> >>
> >> On 11/11/08, Christopher <[EMAIL PROTECTED]> wrote:
> >> >
> >> > Creating a vanilla CE project according to the documentation provided
> >> > runs fine on my local machine (OS X) in development mode. I've created
> >> > a slice on SliceHost (Ubuntu Hardy) to do a test deployment with
> >> > capistrano and git and this is kinda where things get a bit stuck. All
> >> > setup etc works fine up until running "cap deploy:cold", which aborts
> >> > with the following error:
> >> >
> >> > --------
> >> >   * executing "cd /home/deploy/myapp/releases/20081111055938; rake
> >> > RAILS_ENV=production  db:migrate"
> >> >     servers: ["my ip"]
> >> >     [my ip] executing command
> >> >  ** [out :: my ip] (in /home/deploy/myapp/releases/20081111055938)
> >> >  ** [out :: my ip] rake aborted!
> >> >  ** [out :: my ip]
> >> >  ** [out :: my ip] Could not locate the following plugins: engines,
> >> > community_engine, and white_list
> >> >  ** [out :: my ip]
> >> >  ** [out :: my ip]
> >> >  ** [out :: my ip] (See full trace by running task with --trace)
> >> >  ** [out :: my ip]
> >> > ---------
> >> >
> >> > This is what my environment.rb looks like:
> >> >
> >> > ---------
> >> > RAILS_GEM_VERSION = '2.1.2' unless defined? RAILS_GEM_VERSION
> >> > require File.join(File.dirname(__FILE__), 'boot')
> >> > require File.join(File.dirname(__FILE__), '../vendor/plugins/engines/
> >> > boot')
> >> >
> >> > Rails::Initializer.run do |config|
> >> >   #resource_hacks required here to ensure routes like /:login_slug
> >> > work
> >> >   config.plugins = [:engines, :community_engine, :white_list, :all]
> >> >   config.plugin_paths += ["#{RAILS_ROOT}/vendor/plugins/
> >> > community_engine/engine_plugins"]
> >> > .
> >> > .
> >> > .
> >> > end
> >> >
> >> > # Include your application configuration below
> >> > require "#{RAILS_ROOT}/vendor/plugins/community_engine/engine_config/
> >> > boot.rb"
> >> > ---------
> >> >
> >> > I've created a vanilla CE project on the slice itself and that worked
> >> > fine. Dumping that into a repo and deploying it caused the same
> >> > problem.
> >> >
> >> > My suspicion is that there might be an issue with symlinks - anybody
> >> > come across something like this?
> >> >
> >> > >
> >> >
> >>
> >>
> >
> >
> > >
> >
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"CommunityEngine" 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/communityengine?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to