How do you control your version control in Magento

Question

I'm trying to find a better way to get started creating Magento extensions for release. I would like to be able to have separate svn repositions for each extension. It seems that there are some difficulties trying to find the best way to develop them in such a way as to simplify version control. Obviously, you want to work with the extension inside the Magento application, but do not want to worry about ignoring all files except those intended for the extension.

I thought about using svn: externals, but I don’t think this is the answer because you need some files to be moved to other directories, and this should not be completely autonomous. From what I read with external ones, it does not seem that this is a good choice.

So I just want to see what others are doing to set up the extension development environment, maybe just ignoring all the other files is the way to go. We also thought about sym linking, but that would mean writing a script that would do it for all developers, and I'm not sure if that would be so great as people can set up their projects differently.

Answer 1

The symbolic link script you are thinking of already exists. It was called Module Manager (modman), and it is great for managing multiple modules in a single Magento installation. Modman allows you to check and manage multiple SVN repositories in one folder.

However, note that a security change in Magento 1.4.2.0 makes it impossible to map template files in the application / design, so a workaround is needed. More information in this bug report .

Answer 2

Ashley Schroeder introduced such methods in magento, imagining a conference. You can visit his website: Designing Your Purple Shop

Answer 3

I use git to control the codebase extension, deploy and symlinking + override the error mentioned in each extension