Capistrano 食谱和其他杂项的 Git 存储库结构
我的问题是，我有一堆不同的 capistrano 配方和代码片段，可以在多个项目中使用。我的本地文件结构是一个名为 helper-snibbits 的文件夹，其下有名为 ./capistrano、./php-bits 和 .py-bits 的文件夹，
我可以使用存储库单独跟踪每个片段，但这变得很难在服务器上管理，并且在我的项目中。我更愿意为所有内容建立一个存储库。您认为组织这次活动的最佳方式是什么？我喜欢子模块工作流程，但据我了解，每个子模块都需要一个单独的存储库。这是真的吗？如果单独的存储库是最好的方法，我最终会这样做。
My problem is that I have a bunch of different capistrano recipes and code snippets that I use across multiple projects. My local file structure is a folder called helper-snibbits with folders under that called ./capistrano, ./php-bits, and .py-bits
I can track each snippet individually with a repo but that becomes hard to manage on the server and in my projects. I'd prefer to set up one repo with everything. What do you think is the best way to organize this? I love the submodule workflow but as I understand it would need a separate repo for each submodule. Is that true? If separate repos are the best way I'll end up doing that.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
抱歉这么晚了... :D
我们最近发布了一个工具，用于通过单独的存储库组织 capistrano 配置和配方。
http://pulsar.nebulab.it
如果您有许多项目和配方需要使用 capistrano 进行管理，并且您希望减少代码重复并普遍过上更好的生活。
Sorry for being so late... :D
We recently released a tool for organizing capistrano configurations and recipes via a separate repository.
http://pulsar.nebulab.it
It's really useful if you have many projects and recipes to manage with capistrano and you want to reduce code duplication and generally live a better life.