Difference between revisions of "Opasnet update 2017"

From Testiwiki
Jump to: navigation, search
m (Opasnet-wiki server)
Line 2: Line 2:
  
 
== RTools server ==
 
== RTools server ==
 +
CentOS 6.4: full support ended, but still get maintenance updates.
 +
 
Key software, upgrade paths and related issues:
 
Key software, upgrade paths and related issues:
 
*apache 2.2.15 -> 2.2.32 or 2.4.25
 
*apache 2.2.15 -> 2.2.32 or 2.4.25
Line 19: Line 21:
  
 
== Opasnet-wiki server ==
 
== Opasnet-wiki server ==
 +
CentOS 6.5: full support ended, but still get maintenance updates.
 +
 
Key software, upgrade paths and related issues:
 
Key software, upgrade paths and related issues:
 
*apache 2.2.15 -> 2.2.32 or 2.4.25
 
*apache 2.2.15 -> 2.2.32 or 2.4.25
Line 31: Line 35:
 
**Composer might be useful for managing PHP dependencies
 
**Composer might be useful for managing PHP dependencies
 
*RTools MediaWiki extension
 
*RTools MediaWiki extension
**RTools special page class
+
**RTools special page class (now named SpecialRtools)
 +
***Creates instance of rtools_client
 +
***separate config file, which is included by SpecialRTools instead of rtools_client for some reason
 +
***fixed: mysql->mysqli
 +
***fixed: wfMsg->wfMessage
 
**<nowiki><rcode></nowiki> tag
 
**<nowiki><rcode></nowiki> tag
**hooks
+
***Detected by parser hooks
***live code
+
***RToolsParser class
***UI?
+
****fixed: wfMsg->wfMessage
**xmlrpc library used for something
+
****fixed: class instead of global functions
***
+
*****create class instance in parser given by hook in order to retain variable values
 
**rtools_client
 
**rtools_client
 
***handles connections and job submissions etc. to server
 
***handles connections and job submissions etc. to server
**separate config file, which is included by RTools instead of rtools_client for some reason
+
***xml-rpc library
 +
****communicates with rtools_server API
 
**javascripts
 
**javascripts
 
***UI?
 
***UI?
 
***ajax?
 
***ajax?
 +
**livecode?
 +
**Current issues:
 +
***Show code button does not work
 +
***Run page throws: Didn't receive 200 OK from remote server. (HTTP/1.0 500 Internal Server Error), which is a xml-rpc related error
 
*table2base MediaWiki extension
 
*table2base MediaWiki extension

Revision as of 08:50, 15 June 2017

This page contains notes produced while updating Opasnet server systems during the summer of 2017.

RTools server

CentOS 6.4: full support ended, but still get maintenance updates.

Key software, upgrade paths and related issues:

  • apache 2.2.15 -> 2.2.32 or 2.4.25
    • newer branch not particularly important
  • PHP 5.3.3 -> 5.6.x or 7.1.x
    • incompatibilities in mysql functions
      • "mysql" -> "mysqli" (5.5)
    • should upgrade to latest version
  • MySQL 5.1 -> 5.7
  • mongoDB 2.4 -> 3.2
    • should be relatively easy as we are not using sharding etc.
  • rtools_server PHP application
    • starts on test server after minor changes
    • further testing needed
  • opasnet_base2

Opasnet-wiki server

CentOS 6.5: full support ended, but still get maintenance updates.

Key software, upgrade paths and related issues:

  • apache 2.2.15 -> 2.2.32 or 2.4.25
  • PHP 5.4.28 -> 5.6.x or 7.1.x
    • 5.5.9+ required by currently supported mediawiki releases
    • latest php also supported
    • incompatibilities likely to occur in 5.4->5.5, hence might as well upgrade to latest
  • MySQL 5.5.37 -> 5.5.56 or 5.7.x
  • MediaWiki 1.20.0 -> 1.27 (LTS) or 1.28.2 (latest)
    • need to check supported extensions
    • MyExtension.php no longer supported, need extension.json for registering extensions
    • Composer might be useful for managing PHP dependencies
  • RTools MediaWiki extension
    • RTools special page class (now named SpecialRtools)
      • Creates instance of rtools_client
      • separate config file, which is included by SpecialRTools instead of rtools_client for some reason
      • fixed: mysql->mysqli
      • fixed: wfMsg->wfMessage
    • <rcode> tag
      • Detected by parser hooks
      • RToolsParser class
        • fixed: wfMsg->wfMessage
        • fixed: class instead of global functions
          • create class instance in parser given by hook in order to retain variable values
    • rtools_client
      • handles connections and job submissions etc. to server
      • xml-rpc library
        • communicates with rtools_server API
    • javascripts
      • UI?
      • ajax?
    • livecode?
    • Current issues:
      • Show code button does not work
      • Run page throws: Didn't receive 200 OK from remote server. (HTTP/1.0 500 Internal Server Error), which is a xml-rpc related error
  • table2base MediaWiki extension