As a Xibo newbie, I spend a fair amount of time experimenting with the incredibly feature rich Xibo system (CMS Cloud / Windows Player). So far, it has been ok since we are in learn/development/test/QA phase. However, we are about to take our first production display online ( April/2, April/1 avoided to prevent the launch announcement to the community we serve being deemed a prank).
Going forwards, we would like to isolate the development/test/QA environment from the production environment. Given the need to test updates (e.g. Xibo for Windows v2 R252 / CMS 2.3.2 - Currently on Xibo for Windows v2 R201 / CMS 2.3.1) and sandbox exploring features, what is the best practice to achieve this? (Possibly a new category - Best Practices?)
I anticipate the solution would be to buy a new CMS/Player license for the second environment. The dev and production environments can be on the same PC or separate PCs. There are separate displays available for the 2 environments, one each, expecting to expand production displays to 5 in near future.
Any suggestions much appreciated.