[Vtigercrm-developers] Tips on how to setup vtiger dev environment

Sukhdev Mohan s.mohan at myti.it
Mon Apr 27 09:47:13 GMT 2020


Hi Martin,

This sounds clean and elegant! Can you share how you log sql changes?

Best Regards,
Sukhdev Mohan
———————————
Cel. (+39) 320 7020345
Email s.mohan at myti.it




> Il giorno 27 apr 2020, alle ore 11:09, Martin Allen <martin.allen at clystnet.com> ha scritto:
> 
> We maintain a Git repositories separately to the public vTiger one. 
> We found that because the public repository is the code pre-installation, then we cannot simply clone that and use it as otherwise everytime we want to update a site, it goes back to pre-installation state. So we installed a plain version of vTiger and created a repository with this code. This is left untouched, and whenever a new version of vTiger is released we update the changes to this repository so we can track all changes between each version of vTiger.
> 
> We have created our own .gitignore file, which prevents files and directories that can potentially be changed during day-to-day operation (after several months of trial-and-error we think we have a complete list). 
>  
> This repository is then cloned for each new system we want to create and development can occur on each system individually. We use the following GIT branching strategy (https://nvie.com/posts/a-successful-git-branching-model/ <https://nvie.com/posts/a-successful-git-branching-model/>)
> 
> Our developers run VMs locally, and can develop changes and test against a development database (simple copy of the live database after installation). Each installation also has its own development site for user testing of new features, again using the development database. We have tried several methods of logging database changes in GIT (Phinx, migrations similar to Laravel) but found that simple PHP scripts that record SQL database changes seems to be best so far.
> 
> We discovered problems with our process when installing external extensions that are encrypted etc, but procedural workarounds prevent those becoming issues.
> When we roll changes to the live site, we record any PHP/SQL scripts that need to be run as part of our rollout process (which depending upon the complexity may be overnight).
> 
> We use Vagrant/VirtualBox to run our VMs and are currently investigating the ability to include the setup files for Vagrant into the repository as well to ensure all testing is done using the same system environment etc and minimise setup time for developers. 
> 
> Martin Allen
> 
> >>Call me now for free<< <https://emailrtc.voiceflex.com/?c=7b355216c4>
> 01392 248692 - Main Office
> 01392 690659 - Direct Line
> 
> 
> 
> Have you visited our website recently? http://www.clystnet.com <http://www.clystnet.com/>
> 
> The information in this email is confidential If you are not the intended recipient, you must not read or use that information. This email and any attachments are believed to be virus free however no responsibility is accepted by Clystnet for any loss or damage arising in any way from receipt or use thereof. Clystnet Ltd (company reg number 7164503) is based at Silverdown Park, Fair Oak Close, Clyst Honiton, EX5 2UX
> 
> <image001.png>_______________________________________________
> http://www.vtiger.com/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20200427/f7f2983e/attachment-0001.html>


More information about the vtigercrm-developers mailing list