I think that DB patches should be managed differently.
Actually, is impossibile to create custom paches, because when a new ISPConfig release will be available, your patch will overwrite the custom ones.
I think that you should create a 'custom' directory where developers can add own patches, that will be run after yours.
or, maybe better:
If you would contribute improvements back to the ispconfig main svn like the other devs are do it and as its common with OS projects, then you dont need custom patches.
|All times are GMT +2. The time now is 22:48.|
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.