Upgrade to trunk

To get the very latest version of FOG you need to follow one of the following methods. Each has its pros so you will need to figure out which you want to use:
- SVN
- Git
Remember these are mostly betas so there are bound to be bugs, but with bugs also comes fixes of the issues found in the "Stable Release"
If you have nodes they will also need to be upgraded! (Excluding Beta Windows Nodes)

SVN

Update and then Install SVN (or 'yum' instead of 'apt-get' if you are running a RedHat based OS)

sudo -i
apt-get update && apt-get install svn

Checkout the latest SVN version and place it into /root/fogproject

svn co https://svn.code.sf.net/p/freeghost/code/trunk /root/fogproject

Then navigate to the folder you specified and run:

cd /root/fogproject/bin
./installfog.sh

Update to latest

As the development tree of FOG changes quiet often (pretty much daily!) you might want to update to the very latest version from time to time. To do this use the following commands:

sudo -i
cd /root/fogproject
svn up
cd bin
./installfog.sh

NOTE: You must run svn up in the "/root/fogproject" and not in on of its subdirectories (e.g. "/root/fogproject/bin")

Check your SVN version

cd /root/fogproject
svn log -v

Upgrade to specific revision

This is recommended only for experienced FOG users: Upgrade to Revision

Git

Update and then Install git (or 'yum' instead of 'apt-get' if you are running a RedHat based OS)

sudo apt-get update && apt-get install git

Initial checkout

sudo -i
git clone https://github.com/FOGProject/fogproject.git /root/fogproject

Then navigate to the folder you specified and run:

cd /root/fogproject/bin
./installfog.sh

Update to latest

As the development tree of FOG changes quiet often (pretty much daily!) you might want to update to the very latest version from time to time. To do this use the following commands:

cd /root/fogproject
git pull
cd bin
./installfog.sh

Check your git version

cd /root/fogproject
git log -1

Congratulations

Congrats! You have now upgraded to the "bleeding edge" of FOG deployment. It is your responsibility to keep upgraded until the next "Stable Release". Until then you will see in the cloud of your Web Gui rXXXX. This indicates the revision you are now on.
You can check for updates to the revisions under Fog Configuration. This will state the version you are on and what the lastest revision is.

Additional information on SVN and git & FOG Trunk

Subversion (often abbreviated SVN, after the command name svn) is a software package that allows you to 'check out' software. SVN in and of itself is not FOG, but a lot of FOG users use it. FOG's SVN repository is provided by SourceForge. Git allows the same general functions as SVN, and FOG's Git repository is provided by GitHub. Either method is as valid as the other, albeit the commands are different for each.

FOG developmental versions are called "revisions." Revisions are normally stable for the PRIMARY functions of FOG: IMAGE > NAME > JOIN TO DOMAIN using UNICAST and MULTICAST

Other features in FOG revisions (not directly related to the imaging process) are sometimes broken. The developers are pretty good about fixing issues when someone finds and reports it. These other features usually do not impact imaging. Additionally, if you encounter an issue, let us know about it in the forums and someone is likely to help and/or fix it quickly, making a new "revision" that you can download and install very quickly using the above methods.

However, with the current revisions, you'll benefit from a plethora of bug fixes, a much wider range of supported host hardware, and new features!

Updating FOG from one revision to a newer one usually takes less than a minute or two. Fog uses your settings from previous installations so you don't have to answer questions about the installation or set additional configurations. FOG supports upgrading, but not downgrading. If you would like to roll-back to a previous version, generally, this can only be done by reverting to a previous snap-shot taken from a virtualized machine that FOG is installed on.

It's advised to backup your database and export your hosts (and label the files) prior to upgrading. You can do that like this on 1.2.0 and higher: