On Wed, Feb 18, 2009 at 22:39, sergio_101 <[email protected]>wrote:
> > for some reason (i am investigating this too), those plugins never > show up in any of my commits to my git repository.. That's because you only have those plugins in your local working copy; they are never tied to your repository in any way. You can easily connect them to your version control (and by that, to your deployments too) with git submodule command. Suppose you have a plugin checked out with git at "vendor/plugins/foo". If you did a regular clone, the foo plugin is its own repository and has the "vendor/plugins/foo/.git" directory. Let's suppose that you cloned the plugin from "git://github.com/example/plugin.git". First, ensure that your working copy (of the main application) is clean (`git status`). Now, add the plugin as submodule with: git submodule add git://github.com/example/plugin.git vendor/plugins/foo Then commit this change: git commit -m "added foo plugin as submodule" Note that the plugins code isn't physically added to your main repository; it's just that the plugin repository got linked to your main one and now you can deploy your full application. http://github.com/guides/developing-with-submodules Now you need to put this in your "deploy.rb" for capistrano: set :git_enable_submodules, true set :deploy_via, :remote_cache You definitely want the "remote_cache" strategy, otherwise deployments will be too slow (especially if you have lots of plugins as submodules). You're set to deploy now. --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
