Changes between Version 2 and Version 3 of ServerMigration

Timestamp:

Apr 4, 2016, 11:08:54 PM (11 years ago)

Author:

steve.winter

Comment:

--

ServerMigration

@@ -24 +24 @@
 siteMode                                                        = offline
 }}}
- 4. save and exit nano
+ 4. save (CTRL-O) and exit (CTRL-X) nano
 All requests from that moment forward will receive an error message saying that the site is offline and that they should try again at a later time.
 
@@ -78 +78 @@
 this may vary depending on the specific version of *nix in use, other virtual hosts etc. Amend subsequent commands to match the specific path to the web root. Note also that the default user for Apache is www_data, however that may not be the case on the server in question, again, amend subsequent commands as required.
 
+1. find the current version of the site from the subversion repository
+ - browse to https://svn.msdev.co.uk/blinc/release/ (you will have to login using the credentials supplied)
+ - in the list identify the most recent version. '''Note''' that the list sorts alphabetically, not numerically, so the latest version may not be at the bottom. At the time of writing 2014-04-04 the current version is 1.11
 1. make the web root writeable by PHP
 {{{
 sudo chown www_data:www_data /var/www/app.blincref.com
 }}}
-2. find the current version of the site from the subversion repository
- - browse to https://svn.msdev.co.uk/blinc/release/ (you will have to login using the credentials supplied)
- - in the list identify the most recent version. '''Note''' that the list sorts alphabetically, not numerically, so the latest version may not be at the bottom. At the time of writing 2014-04-04 the current version is 1.11
 3. save the attached install.php file to the web root folder. This can be achieved using
 {{{
+wget https://trac.msdev.co.uk/blinc/raw-attachment/wiki/ServerMigration/install.php -O /var/www/app.blincref.com/install.php
+}}}
+4. edit the install.php file to set three parameters in the file, the supplied SVN username and password, and the current version identified in step 1 above.
+{{{
+nano /var/www/app.blincref.com/install.php
 
+and modify:
+
+$svnUsername                                            = '** SVN Username **';
+$svnPassword                                            = '** SVN Password **';
+$version                                                = '** Current version **';
 }}}
+5. in a web browser navigate to the install.php file, e.g. https://app.blincref.com/install.php. This will export the necessary code into place on the server. It may take several minutes to complete.
+6. once complete delete install.php
+{{{
+rm /var/www/app.blincref.com/install.php
+}}}
+7. create the local configuration file by copying the default file
+{{{
+sudo cp /var/www/app.blincref.com/assets/implementation/impl.config.default /var/www/app.blincref.com/assets/implementation/impl.config
+}}}
+8. modify the config file to set the correct !FileMaker host (as for moving the DB server above). Depending on other changes which may also have occurred it may be necessary to adjust other settings in this file, for example the configuration for sending mail.
+9. create the certificate and upload folders and give PHP write access to them
+{{{
+sudo mkdir /var/www/app.blincref.com/assets/certificates
+sudo mkdir /var/www/app.blincref.com/assets/uploads
+sudo chown www_data:www_data /var/www/app.blincref.com/assets/certificates
+sudo chown www_data:www_data /var/www/app.blincref.com/assets/uploads
+}}}
+10. browse to the site to confirm that all is working: https://app.blincref.com
+
+=== Troubleshooting ===
+The most likely problems will arise form file permissions or module configuration. 
+1. If the install fails, ensure that you have given the (correct) web user write access to the document root folder
+2. if you receive errors when attempting to run the app, firstly ensure that you have set the DB server parameters correctly, and that they have been saved to the config file.
+3. depending on the server configuration other error messages may be displayed on screen to indicate where issues may lie. If not (which they shouldn't be - all errors should be turned off in the php.ini file on a production server), add the following to the top of index.php immediately after <?php:
+{{{
+error_reporting(E_ALL);
+ini_set("display_errors", 1);
+}}}
+ - you may see (many) depreciation errors, these can be ignored
+ - you should see the cause of the actual problem, likely a php fatal error, this should indicate where the cause of the problem is, and Google should be able to provide a solution to that issue.