CoreBOSBB

Firstly, it's become painfully clear that the reason my code and data is so out of date is because I didn't understand that "I" was responsible to taking certain steps to occasionally run the necessary git commands to sync the code on my server and then apply updates. My fault entirely.

So now, I find myself wanting to get my installation of CoreBOS completely up-to-date. I've been fighting with migrating my installation to a new server - the current code-base runs fine on the new server however I really do need to get this critter up to date.

I'm wondering what the difference in git pull and git merge is.

When I run git pull on my current installation I receive the following information on the console:

I can guarantee I haven't changed any of these files if that is what is stopping the process from completing successfully. I have to admit that there is a lot about this process that clearly I don't understand... yet. I really want to understand this. I'm also aware of the fact that because I've not paid the proper attention to keeping my code up to date the database has suffered because it appears to be in a state where I might be stuck at this code level.

Another question i have is: Can I combine the git commands like this:
 
in order to force the process to merge the new files into the existing system? I haven't tried it yet because I don't understand enough about how git works.

Joe: I've been really frustrated the past week or so and its mostly due to the fact that I've taken on too much at one time while trying to keep up with my regular work-load. So, I think I'll just concentrate on this one thing here. Your help and guidance is much appreciated.

One step at a time. there are a lot of little concepts to learn and small hurdles to jump over. be patient you'll get there and I will personally help you all the way. In fact, do not hesitate at all to contact me directly for help, you have my email and I am very easy to find on hangouts and gitter (where I invite you to join: https://gitter.im/corebos/discuss). I owe you that much at least !!

Now, to answer you question. "git pull" = "git fetch" + "git merge", so it isn't the same. Let me try to explain that. When you download a copy of coreBOS with "git clone" you get all the code in the state it is at that moment and ALL the history of changes that it has gone through. That historical information is saved in the .git directory. Now suppose we keep developing and a week goes by. Now your code is not up to date with the latest changes, so you have to launch "git fetch", that will bring into the history all the changes since you downloaded the code (or launched your last "fetch"). The "git fetch" command only updates the history, it does not update your code. So you could study each of the changes before applying them to your code. Mostly, we all just apply them, which is done by executing the "git merge" command. "git merge" will look in the history and apply any changes that are there that haven't been applied to your code. So every time you want to update your code you have to launch "git fetch" and "git merge". This is so common, and we do it so often that they have added a short cut for us: "git pull" = "git fetch" + "git merge".

In the end you can actually forget about all that and just always do a "git pull", that is what you need.

One last comment. Note that git will update your code, but it has no idea about your database. If that new code needs a new field to do some magic, that field will NOT be created by the code update. In fact, that code will break because it will look for the field and it won't find it. This is where coreBOS updater comes in. coreBOS updater is capable of analyzing the state of your code and compare it with the state of the database and apply any changes that are missing. It sounds like magic,.... and it is :-)

Finally, the error you are running into is most probably all about file permissions. It turns out that git controls the attributes of the files also, not just their contents. That means that if I set a file to have permission 664, and you have it set to 644, git sees that as a change and won't apply the update, even if the file contents hasn't changed at all. The easiest way around this is to deactivate the file permission/attribute control:

git config --global core.fileMode false

http://stackoverflow.com/questions/1580596/how-do-i-make-git-ignore-file-mode-chmod-changes

git status will show you a list of changed files, try that before and after the fileMode false command and you should see the difference.

Let me know how it goes.

getting fuzzy brain like I used to in college but it's all good. That is good information and I really appreciate it. I'll refresh my copy of the production install on Merlin (that's the new server I'm migrating to and currently testing on).

well... this was slightly different...

execute this and show me the output:

git diff config.template.php

(03-04-2017, 11:50 PM)joebordes Wrote: [ -> ]execute this and show me the output:

git diff config.template.php

Ok, that was not a good example, that file shows you have made changes there. you do not need to change this file so you can "git checkout config.template.php"
now show me

git status include/language/hu_hu.lang.php

(03-05-2017, 12:39 AM)joebordes Wrote: [ -> ]Ok, that was not a good example, that file shows you have made changes there. you do not need to change this file so you can "git checkout config.template.php"
now show me

git status include/language/hu_hu.lang.php

[mweaver@merlin corebos]$ git status include/language/hu_hu.lang.php

# On branch master
# Your branch is behind 'origin/master' by 3343 commits, and can be fast-forwarded.
#   (use "git pull" to update your local branch)
#
# Changes not staged for commit:
#   (use "git add <file>..." to update what will be committed)
#   (use "git checkout -- <file>..." to discard changes in working directory)
#
#       modified:   include/language/hu_hu.lang.php
#
no changes added to commit (use "git add" and/or "git commit -a")

sorry, I must have fallen asleep when I wrote that :-(
the correct command I'm looking for is:

git diff include/language/hu_hu.lang.php

Holy cow! The response from that query is so long I've attached it as a text file. Not sure what any of it means but... see attached.