Best practice for managing changes to a large PHP project [message #1810410] |
Fri, 09 August 2019 16:43 |
Richard Gate Messages: 1 Registered: August 2019 |
Junior Member |
|
|
Hi, I'm doing some work on a number of relatively small changes to a SuiteCRM system (PHP and JS). I've been using Eclipse for some to as an IDE for PHP and JS but I'm getting to the stage where I need to manage the changes in a much more structured way. For these who know about SuiteCRM, I do understand about the use of the "custom" folder to override changes and made them "upgrade safe" but its not always possible to use this structure to make certain that changes are "upgrade safe". So I've been looking at Git mechanisms in the Eclipse "Team" to produce patch files for modifications that can be re-applied after a system upgrade (or changes generated by the SuiteCRM Module Builder).
Any suggestions on Best Practice for this?
Thanks, Richard
|
|
|
Powered by
FUDForum. Page generated in 0.08420 seconds