Hi all,
I’ve had a quick search for this but either found data related to SugarCRM or very old SuiteCRM info.
At the moment, I’m a sole developer using AWS EC2 to host our SuiteCRM instances. When I want to test a new feature, I’ll spin up a duplicated copy of the production instance and make the changes on there. If all OK, I’ll replicate it in the production instance. Major ball ache as it doubles the work! However I was unsure how to tackle the the version control/database sync side of things with SuiteCRM. As we were in the testing stages of trying out various CRMs, I wasn’t too concerned.
I’m now at the stage where SuiteCRM is definitely going to be used by the company, so I need to implement a proper version control/database sync setup.
Of course, when I’m making changes to a development instance, the production copy is still live. Users are uploading files, adding accounts etc. I need to be able to import the necessary new changes from the development instance.
.gitignore
Am I ignoring the correct folders? Anything else that should be added?
.htaccess
config.php
config_override.php
/*.log
/26d7-upload/
/cache/
!/cache/index.html
/custom/application/Ext/
/custom/blowfish/
/custom/history/
/custom/modulebuilder/
/custom/modules/*/Ext/
/custom/modules/Connectors/connectors/sources/ext/*/*/config.php
/custom/working/
/install/status.json
/modules/AOD_Index/Index/*
/upgrades/
/upload/
!/upload/index.html
SQL Tables
I have a script to make various backups including Full, Data Only, Structure Only, Fields_Meta_Data table only.
With regards to the database, am I right in saying only the fields_meta_data needs to be imported back in to the production instance?
Any help greatly appreciated on this.