On Tue, Jan 20, 2009 at 05:44, Jamis Buck <[email protected]> wrote:
> > I'd just like to have a > few experienced capistrano/git users chime in. Perhaps post it on > lighthouse (did you already?) and request comments. I'm a heavy user of submodules myself. Whenever a submodule changes (the source, the path or it just gets removed) I update it with cap shell, like so: $ cap shell >> cd path/to/deployment/shared/cached-copy/vendor/plugins/awesomeness_plugin && git config remote.origin.url git://github.com/new/awesomeness/source.git (Ultimately, I think git's concept of submodules is flawed, but that's > neither here nor there.) Why submodules rock: - Easy vendor management without polluting your project's repo - Commit and push from a submodule -- great for opensource - Keep track of edge plugins and libraries just by bumping up the requried SHA Why they suck: - Replacing a vendored plugin with a submodule (at the same path) results in not being able to go back to those old times without temporarily moving the submodule checkout somewhere else - Change the source URL means everyone must do the same, otherwise their subsequent ` git submodule update` commands will fail to find the new SHAs in the old origin - People are not always aware that they need to `git submodule update` after pulling from upstream and the indicator that your submodule checkouts are out of date (`git status`) is vague --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
