Xibo upgrade and installation on virtual machine windows server 2012 r2

1

Hi. Am one of the IT guy who has been assigned the responsibility of maintaining the already running Xibo setup of 1.4.0 on a Windows workgroup PC. Now I wanted this setup to be upgraded to the latest version to 1.7.9. As am new to Xibo, for testing purpose, I have installed the latest CMS version with XAMPP 5.6.24 & with Signage players to another machine. After testing, now I wanted to install it permanently to a machine for production purpose. My few questions is:

  1. Is it possible to upgrade 1.4.0 directly to 1.7.9 ? If so please instruct with necessary steps.
  2. Can I install the new setup of 1.7.9 to a Virtual Machine of Windows Server 2012 R2 ? Does this setup have any limitations pertaining to the number of displays?
  3. Does the version of XAMPP 7.0.13 support with CMS 1.7.9 ?
  4. Do I have to wait for too long for the release of 1.8.0 stable version?
2

  1. Yes, although it might be safer to do 1.4.0- 1.6 - 1.7.9

  2. I don’t think that would be an issue

  3. I believe it uses php 7? If so, no, 1.7 series will not support it ( 1.8 as of now will not either, but will in the future)

  4. 1.8.0-rc2 is available now, rc3 should come very soon, depending on the feedback etc the full release should be out not long after that.

3

Thank you Peter :slight_smile:
So I hope I can proceed with the installation on VM Machine. And I would like to know whether is it very important to install Docker before we start the installation? Because I tried installing it on a test machine but I found it bit difficult for me to understand it. So is there any pre procedures like installing any other application before installing Xampp or just I can start with Xampp installation and with CMS? Please suggest. Thanks a lot.

4

Docker is recommended for 1.8 series - not required, but recommended :slight_smile:

For 1.7.9 please see http://xibo.org.uk/manual/en/install_environment_windows_xampp.html and then http://xibo.org.uk/manual/en/install_cms.html

I assume the above is exactly what you did when you installed it on your test environment.