12-10-2016, 08:38 PM
That all sounds perfect!
What you need to know about git is basically that, not much more.
Effectively not all updates will have database changes, but you have to run the updater just in case. You can look to see if there are any changes inside the build/changesets directory when you "pull", but, in general it is easier to just load+apply
I'm glad you got it working. Following your log problem I started to look into the issue. Since we forked vtiger CRM we have been dedicating a lot of time to eliminate all the warnings in the code. We have almost all of them and you should be able to run the application in that mode. Now I started looking into the Notice. I have spent the better part of the last two days eliminating those but there are just too many still. I'll keep working on it. In any case, it is best to run E_ERROR in production, you don't need the additional logging there.
What you need to know about git is basically that, not much more.
Effectively not all updates will have database changes, but you have to run the updater just in case. You can look to see if there are any changes inside the build/changesets directory when you "pull", but, in general it is easier to just load+apply
I'm glad you got it working. Following your log problem I started to look into the issue. Since we forked vtiger CRM we have been dedicating a lot of time to eliminate all the warnings in the code. We have almost all of them and you should be able to run the application in that mode. Now I started looking into the Notice. I have spent the better part of the last two days eliminating those but there are just too many still. I'll keep working on it. In any case, it is best to run E_ERROR in production, you don't need the additional logging there.
Joe
TSolucio
TSolucio