Have Geek Brain

How do I complete a full cms installation (how do you manage official CMS files with your own modules)?

I have read several topics that SO have suggested ("The question you are asking seems subjective and will probably be closed") but could not find an answer to what I was looking for.

I am using Joomla on a project. With Joomla, I have about 8 different third party modules, each with its own version number and Joomla compatibility. Some might actually be upgraded to Joomla (now it's 1.5.10), some might not. Some of the modules were made by us. They all work and they are all necessary to fulfill the requirements of our company website.

Fact: What's the best way to put it all in original control? Are you "linking" the Joomla source code inside your repository, even if it is a third party, and it is very unlikely that you will modify these files? Or are you just browsing the main files that are really under your control?

IMHO:

The advantages of putting the core Joomla files inside the repository is that I can create tags and have a complete system in one go, if needed, without reading the txt documentation file which says "these modules are compatible with joomla XX, joomla component XX with joomla version XX ", etc.

The disadvantage is that when installing files that aren't really versioned unless there is a new version of joomla.

What do you think is the best idea? What do you usually do when your project (for example, our portal) is created by many different components from different sources?

+1


a source to share


3 answers


I would create a concrete "deployment state" tree that uses svn: externals to point to my own Joomla, my modules, etc. - each in its own tree. The deployment tree will only keep track of how the modules are aggregated.



0


a source


We usually include the compiled versions of third party modules in their own folder in SVN. Build scripts (or external: properties) can then be used to copy them wherever they are.



0


a source


First, if your changes are general and improving, you should send it back to the project.

Otherwise, place it in the original control. Copy the changes as they come in and merge them. In other words, treat the "real" source repository as if they were a different developer.

0


a source






More articles:


All Articles