Managing Plugins With Capistrano

Hello,

What's the best way to manage plugins with Capistrano?

I am running Mephisto 0.7.3 with a couple of plugins from
the  
community and one of my own.  Normally when I build a Rails
app the  
app is in my own Subversion repository so I can install
plugins to my  
heart's content and they all get pulled out of svn into the
right  
place on the server.

Mephisto of course is in its own Subversion repository.  I
can  
happily deploy it with Capistrano to my server but I'm not
entirely  
sure how to pull in the plugins I am using because they live
in  
different repositories.

I was wondering about writing an after_update_code task
(yes, old- 
school, I know) to do an svn checkout on all of the plugins
I am  
using and stick them in vendor/plugins.  Is this sensible or
am I  
missing something?

Thanks and regards,
Andy Stewart


--~--~---------~--~----~------------~-------~--~----~
Mephisto: http://mephistoblog.com |
Mephisto Help: http://mephisto.stikipad
.com

To post to this group, send email to MephistoBloggooglegroups.com
To unsubscribe from this group, send email to
MephistoBlog-unsubscribegooglegroups.com
For more options, visit this group at http
://groups-beta.google.com/group/MephistoBlog
-~----------~----~----~----~------~----~------~--~---

Well, YMMV, but I typically use svn:externals for things
like that
(http:
//svnbook.red-bean.com/en/1.0/ch07s03.html)

The hitch there is that if one of the remote repositories
goes away
and you need to deploy something, it can give you a pretty
decently
sized headache.  If that's an issue for you, you might also
want to
look at setting up a little mirrored meta-repository of what
you need
with something like svk.

Hope that helps,

-Chris

On May 17, 4:33 am, Andrew Stewart <b...airbladesoftware.com> wrote:
> Hello,
>
> What's the best way to manage plugins with Capistrano?
>
> I am running Mephisto 0.7.3 with a couple of plugins
from the  
> community and one of my own.  Normally when I build a
Rails app the  
> app is in my own Subversion repository so I can install
plugins to my  
> heart's content and they all get pulled out of svn into
the right  
> place on the server.
>
> Mephisto of course is in its own Subversion repository.
 I can  
> happily deploy it with Capistrano to my server but I'm
not entirely  
> sure how to pull in the plugins I am using because they
live in  
> different repositories.
>
> I was wondering about writing an after_update_code task
(yes, old-
> school, I know) to do an svn checkout on all of the
plugins I am  
> using and stick them in vendor/plugins.  Is this
sensible or am I  
> missing something?
>
> Thanks and regards,
> Andy Stewart


--~--~---------~--~----~------------~-------~--~----~
Mephisto: http://mephistoblog.com |
Mephisto Help: http://mephisto.stikipad
.com

To post to this group, send email to MephistoBloggooglegroups.com
To unsubscribe from this group, send email to
MephistoBlog-unsubscribegooglegroups.com
For more options, visit this group at http
://groups-beta.google.com/group/MephistoBlog
-~----------~----~----~----~------~----~------~--~---

On 5/17/07, f1chris <chris.ingrassiagmail.com> wrote:
>
> Well, YMMV, but I typically use svn:externals for
things like that
> (http:
//svnbook.red-bean.com/en/1.0/ch07s03.html)
>
> The hitch there is that if one of the remote
repositories goes away
> and you need to deploy something, it can give you a
pretty decently
> sized headache.  If that's an issue for you, you might
also want to
> look at setting up a little mirrored meta-repository of
what you need
> with something like svk.
>
> Hope that helps,

I dump my plugins in shared/plugins/* and symlink them over
in an
after_update_code task. I don't update my plugins enough to
worry
about writing something smoother.

-- 
Rick Olson
http://lighthouseapp.com

http://weblog.techno-
weenie.net
http://mephistoblog.com

--~--~---------~--~----~------------~-------~--~----~
Mephisto: http://mephistoblog.com |
Mephisto Help: http://mephisto.stikipad
.com

To post to this group, send email to MephistoBloggooglegroups.com
To unsubscribe from this group, send email to
MephistoBlog-unsubscribegooglegroups.com
For more options, visit this group at http
://groups-beta.google.com/group/MephistoBlog
-~----------~----~----~----~------~----~------~--~---

Hi Chris and Rick,

On 17 May 2007, at 18:53, Rick Olson wrote:
> On 5/17/07, f1chris <chris.ingrassiagmail.com> wrote:
>>
>> Well, YMMV, but I typically use svn:externals for
things like that
>> (http:
//svnbook.red-bean.com/en/1.0/ch07s03.html)
>>
>> The hitch there is that if one of the remote
repositories goes away
>> and you need to deploy something, it can give you a
pretty decently
>> sized headache.  If that's an issue for you, you
might also want to
>> look at setting up a little mirrored
meta-repository of what you need
>> with something like svk.
>>
>> Hope that helps,
>
> I dump my plugins in shared/plugins/* and symlink them
over in an
> after_update_code task. I don't update my plugins
enough to worry
> about writing something smoother.

Thanks for the tips.  I particularly like the symlinking --
it's  
simple and it'll do the job.

Regards,
Andy Stewart

--~--~---------~--~----~------------~-------~--~----~
Mephisto: http://mephistoblog.com |
Mephisto Help: http://mephisto.stikipad
.com

To post to this group, send email to MephistoBloggooglegroups.com
To unsubscribe from this group, send email to
MephistoBlog-unsubscribegooglegroups.com
For more options, visit this group at http
://groups-beta.google.com/group/MephistoBlog
-~----------~----~----~----~------~----~------~--~---