social-doc/html/admin/upgrading.html

{HEADING:SECTION:gs1.1_to_gs1.2:Nightly or GNU social 1.1.x to GNU social 1.2.x}

<p>If you are tracking the GNU social git repository, we currently recommend using the "master" branch (or nightly if you want to use latest features) and follow this procedure:</p>

<ol>

<li>
	<p>Back up your data. The StatusNet upgrade discussions below have some guidelines to back up the database and files (mysqldump and rsync).</p>
</li>

<li>
	<p>Stop your queue daemons (you can run this command even if you do not use the queue daemons):</p>
	
	<p><tt>$ bash scripts/stopdaemons.sh</tt></p>
</li>
    
<li>
	<p>Run the command to fetch the latest sourcecode:</p>
	
	<p><tt>$ git pull</tt></p>
	
	<p>If you are not using git we recommend following the instructions below for upgrading "StatusNet 1.1.x to GNU social 1.2.x" as they are similar.</p>
</li>

<li>
	<p>Run the upgrade script:</p>
	
	<p><tt>$ php scripts/upgrade.php</tt></p>
	
	<p>The upgrade script will likely take a long time because it will upgrade the tables to another character encoding and make other automated upgrades. Make sure it ends without errors. If you get errors, create a new issue on the <a href="https://git.gnu.io/gnu/gnu-social/issues">GNU social project page</a>.
</li>

<li>
	<p>Start your queue daemons again (you can run this command even if you do not use the queue daemons):</p>
	
	<p><tt>$ bash scripts/startdaemons.sh</tt></p>
</li>

<li>
	<p>Report any issues at <a href="https://git.gnu.io/gnu/gnu-social/issues">https://git.gnu.io/gnu/gnu-social/issues</a></p>
</li>

</ol>

<p>If you are using ssh keys to log in to your server, you can make this procedure pretty painless (assuming you have automated backups already). Make sure you "cd" into the correct directory (in this case "htdocs") and use the correct login@hostname combo:</p>

<pre>    $ ssh social@domain.example 'cd htdocs
            && bash scripts/stopdaemons.sh
            && git pull
            && time php scripts/upgrade.php
            && bash scripts/startdaemons.sh'
</pre>


            
{HEADING:SECTION:sn1.1_to_gs1.2:StatusNet 1.1.x to GNU social 1.2.x}

<p>We cannot support migrating from any other version of StatusNet than 1.1.1. If you are running a StatusNet version lower than this, please follow the upgrade procedures for each respective StatusNet version.</p>

<p>You are now running StatusNet 1.1.1 and want to migrate to GNU social 1.2.x. Beware there may be changes in minimum required version of PHP and the modules required, so review the INSTALL file (php5-intl is a newly added dependency for example).</p>

<p><b>Before you begin: Make backups</b>. Always make backups. Of your entire directory structure and the database too. All tables. All data. Alles.</p>

<ol>

<li>
	<p>Make a backup of everything. To backup the database, you can use a variant of this command (you will be prompted for the database password):</p>
	
	<p><tt>$ mysqldump -u dbuser -p dbname > social-backup.sql</tt></p>
</li>

<li>
	<p>Stop your queue daemons.</p>
	
	<p><tt>$ bash scripts/stopdaemons.sh</tt></p>
	
	<p>Not everyone runs queue daemons, but the above command won't hurt.</p>
</li>

<li>
	<p>Unpack your GNU social code to a fresh directory. You can do this by cloning our git repository:</p>
	
	<p><tt>$ git clone https://git.gnu.io/gnu/gnu-social.git gnusocial</tt></p>
</li>

<li>
	<p>Synchronize your local files to the GNU social directory. These will be the local files such as avatars, config and files:</p>
	
	<ul>
		<li><tt>avatar/*</tt></li>
		<li><tt>file/*</tt></li>
		<li><tt>local/*</tt></li>
		<li><tt>.htaccess</tt></li>
		<li><tt>config.php</tt></li>
	</ul>

	<p>This command will point you in the right direction on how to do it:</p>
	
	<p><tt>$ rsync -avP statusnet/{.htaccess,avatar,file,local,config.php} gnusocial/</tt></p>
</li>

<li>
	<p>Replace your old StatusNet directory with the new GNU social directory in your webserver root.</p>
</li>

<li>
	<p>Run the upgrade script:</p>
	
	<p><tt>$ php scripts/upgrade.php</tt></p>
	
	<p>The upgrade script will likely take a long time because it will upgrade the tables to another character encoding and make other automated upgrades. Make sure it ends without errors. If you get errors, create a new issue on the <a href="https://git.gnu.io/gnu/gnu-social/issues">GNU social project page</a>.
</li>

<li>
	<p>Start your queue daemons:</p>
	
	<p><tt>$ bash scripts/startdaemons.sh</tt></p>
</li>

<li>
	<p>Report any issues at <a href="https://git.gnu.io/gnu/gnu-social/issues">https://git.gnu.io/gnu/gnu-social/issues</a></p>
</li>

</ol>