We are a team of several developers working on a website that uses both jumla and custom PHP scripts. The problem is that many developers are working on different features, which need to update information in Joomla (adding modules, changing existing ones or changing settings) and when a developer changes, it is usually the first local Makes changes in the form and then does the same thing (hopefully) not only on the production server but it is very error prone, but developers often turn to other developers Do not forget to tell about the stems. Custom PHP scripts are easily shared between developers, but often forgetting changes in Joomla and when they try to change the developer to their local changes in production then they make serious strife.
I'm a Mercurial repository of Joomla, but how can we distribute changes in the database between development, testing and production machines?
We all run Joomla sites in reversal, check them as necessary whenever we are large in a project Changes are required, even then we do branches.
In general, we run a single test database that is shared among all to ensure that we have consistent data but you can easily run with local DB.
Comments
Post a Comment