blocks|key|837645|text|你提到的那些方法对我来说都不管用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|837646|目前，我正在使用pear安装和管理核心模块和社区模块的升级，并使用以下.gitignore文件将整个magento结构提交到git存储库：|offset|length|837647|#+Dynamic+data+that+doesn't+need+to+be+in+the+repo
/var/*
/media/*
/downloader/pearlib/cache/*
/downloader/pearlib/download/*
/app/etc/use_cache.ser
local.xml|code-block|syntax|javascript|837648|并使用以下shell命令保留空目录：|837649|for+i+in+$(find+.+-type+d+-regex+``./[%5E.].*''+-empty);+do+touch+$i"/.gitignore";+done;|837650|我想过的另一个想法是尝试一个供应商分支模型，但我担心这会增加额外的麻烦，特别是在一些大型依赖树的情况下，即为了真正的效率，它必须集成在pear级别上，即每个下载的模块必须自动分支，所以，目前看来只使用付费扩展是很好的。|837651|我试图在magento论坛上发起这个话题，但也没有得到任何回复：http://www.magentocommerce.com/boards/viewthread/78976/|837652|更新：|837653|Magento+Composer+Installer+-值得一看。|837654|Composer正在成为标准的依赖项管理工具，因此，在项目中使用它将获得更多的好处。|837655|你不需要提交或者分支扩展，主题，库到你的项目树中，但是总是有合适的版本和依赖项。|837656|谢谢。|837657|entityMap|0|LINK|mutability|MUTABLE|url|http://www.magentocommerce.com/wiki/1_-_installation_and_configuration/installing_magento_via_shell_ssh#installing_magento_with_the_pear_downloader|1|http://www.magentocommerce.com/boards/viewthread/78976/|2|https://github.com/magento-hackathon/magento-composer-installer|3|http://getcomposer.org/^0|0|8|4|0|0|0|0|0|0|W|1J|1|0|0|0|Q|2|0|0|8|3|0|0|0^^$0|@$1|2|3|4|5|6|7|1G|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1H|8|@]|9|@$D|1I|E|1J|1|1K]]|A|$]]|$1|F|3|G|5|H|7|1L|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|1M|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|1N|8|@]|9|@]|A|$I|J]]|$1|O|3|P|5|6|7|1O|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1P|8|@]|9|@$D|1Q|E|1R|1|1S]]|A|$]]|$1|S|3|T|5|6|7|1T|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1U|8|@]|9|@$D|1V|E|1W|1|1X]]|A|$]]|$1|W|3|X|5|6|7|1Y|8|@]|9|@$D|1Z|E|20|1|21]]|A|$]]|$1|Y|3|Z|5|6|7|22|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|23|8|@]|9|@]|A|$]]|$1|12|3|-4|5|6|7|24|8|@]|9|@]|A|$]]]|13|$14|$5|15|16|17|A|$18|19]]|1A|$5|15|16|17|A|$18|1B]]|1C|$5|15|16|17|A|$18|1D]]|1E|$5|15|16|17|A|$18|1F]]]]

Non of those methods you mention really worked for me...

Currently I'm using <a href="http://www.magentocommerce.com/wiki/1_-_installation_and_configuration/installing_magento_via_shell_ssh#installing_magento_with_the_pear_downloader" rel="nofollow">pear</a> to install and manage upgrades of core and community modules, and committing entire magento structure into the git repository with the following .gitignore file:

<pre><code># Dynamic data that doesn't need to be in the repo
/var/*
/media/*
/downloader/pearlib/cache/*
/downloader/pearlib/download/*
/app/etc/use_cache.ser
local.xml
</code></pre>

and using the following shell command to keep empty directories:

<pre><code>for i in $(find . -type d -regex ``./[^.].*'' -empty); do touch $i"/.gitignore"; done;
</code></pre>

Another idea I thought about it's to give a try a vendor branching model, but I'm afraid it will add extra headache especially in case of some large dependency trees, i.e. for the real efficiency it's must be integrated on the pear level, i.e. every downloaded module must be branched automatically, so, for now it's seems good to use with paid extensions only.

I was tried to fire up the subject on magento forum, but also didn't got any replies:
<a href="http://www.magentocommerce.com/boards/viewthread/78976/" rel="nofollow">http://www.magentocommerce.com/boards/viewthread/78976/</a>

<h2>Update:</h2>

<a href="https://github.com/magento-hackathon/magento-composer-installer" rel="nofollow">Magento Composer Installer</a> - worth looking.

<a href="http://getcomposer.org/" rel="nofollow">Composer</a> becoming standard dependency management tool for PHP, so, you'll get much more advantages utilizing it with in your project.

You won't need commit nor branch extensions, themes, libs into your project tree, but always have proper versions and dependencies.

Thanks.

blocks|key|1052450|text|我想你说的是不同的东西。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1052451|Yauhen的建议完全正确。您可以在git中完成所有这些操作，并且不需要子模块或子树。|1052452|我有和你一样的.gitignore文件，所以看起来不错。|1052453|我写了一篇关于我们如何使用git作为一个团队来管理magento商店的文章，也许它会对你有用：|1052454|Best+practices+for+Magento+Deployment|offset|length|1052455|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/1377338/best-practises-for-magento-deployment/6299087#6299087^0|0|0|0|0|0|11|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@$J|Y|K|Z|1|10]]|A|$]]|$1|L|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]]]

I think you are talking about different things.

Yauhen's suggestions are totally correct. You can accomplish all of this in git, and you don't need submodules or subtrees.

I have about the same .gitignore file as you, so that looks good.

I did a writeup about how we use git as a team for managing magento stores here, maybe it will be useful to you:

<a href="https://stackoverflow.com/questions/1377338/best-practises-for-magento-deployment/6299087#6299087">Best practices for Magento Deployment</a>

blocks|key|837704|text|我认为你可以使用modgit工具来做这件事：https://github.com/jreinke/modgit你可以用modgit+clone命令克隆一些Magento模块。这里有一个完整的例子：http://www.bubblecode.net/en/2012/02/06/install-magento-modules-with-modgit/|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|837705|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/jreinke/modgit|1|http://www.bubblecode.net/en/2012/02/06/install-magento-modules-with-modgit/^0|M|X|0|2Q|24|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

I think you can use modgit tool for this: <a href="https://github.com/jreinke/modgit" rel="nofollow">https://github.com/jreinke/modgit</a>
You'll be able to clone some Magento modules with modgit clone command. A full example is available here: <a href="http://www.bubblecode.net/en/2012/02/06/install-magento-modules-with-modgit/" rel="nofollow">http://www.bubblecode.net/en/2012/02/06/install-magento-modules-with-modgit/</a>

I'm working at figuring out how to best work within my own repo for custom code while integrating with a vendor's library (in this case Magento). In my case, I will not need to push up patches to the vendor (although that would be a great side benefit).

I've looked into git submodule and git subtree. I don't think git submodule will work for what I need. Magento has the following type of tree structure:

<pre><code>/app
 /code
 /community *
 /core
 /local *
 /design
 /adminhtml
 /frontend
 /base
 /yourtheme *
/lib
 /Zend
 /Varien
 /yourlib *
/js
 /yourjs *
 /varien
 /mage
</code></pre>

Using git submodule seems to work best in separate folders (e.g. / is your app and /vendor/magento is the submodule). However, with this degree of intertwining, a submodule doesn't seem like a good solution. Am I wrong about this?

That leaves me with git subtree. But with git subtree, the same core assumption (that the vendor branch is, as implied by the name, a subtree) doesn't hold true. Magento isn't a subtree, but the core library that my project fits within. Is that correct?

If those two methods of git don't work, are there other ones I should know about that would do what I'm trying to accomplish?

The final option I'm reluctant to pursue is having a repo that I then just apply over the latest vendor changes (pulled in from a tarball). I'm reluctant to pursue this as I feel that having the vendor's log information (pulled from <a href="https://github.com/magentomirror/magento-mirror" rel="nofollow noreferrer">https://github.com/magentomirror/magento-mirror</a>) would be greatly helpful in sorting through new updates and figuring out what changes have affected me.

Best practices for using Git with Magento?

我正在研究如何在自己的repo中最好地使用自定义代码，同时与供应商的库(在本例中是Magento)集成。在我的例子中，我不需要向供应商推送补丁(尽管这将是一个很大的附带好处)。我已经研究了git子模块和git子树。我不认为git子模块能满足我的需求。Magento具有以下类型的树结构：/app  /code     /...

问使用Git和Magento的最佳实践？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用Git和Magento的最佳实践？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用Git和Magento的最佳实践？
EN