xibodan

If you're unwilling or unable to consider Docker, install Xibo without docker, as you did before. There are instructions for doing that here: Xibo Documentation. You just need to take care with your webroot, mod_rewrite and ZMQ bindings (if you want push messaging).

You've got the right archive and extracted in the right place, so everything looks good there. The only thing to watch out for is that the Apache installation you already have on the host machine will most likely be using Port 80, so you may want to follow the section regarding "using different ports": Xibo Documentation I believe this means that the Docker install itself wasn't able to install correctly - on Windows Docker uses a small VM to orchestrate various Docker commands and the creation of containers, etc. I've looked through our guide, and it appears that the Docker documentation has moved around again, and the link we've got in the manual is for an overview page rather than the actual installation instructions which are here: https://docs.docker.com/toolbox/toolbox_install_windows/ - were you able to find these OK?

It was a joint decision amongst the project maintainers, but principally it was me that pushed for the change. I still believe it was the right decision, however I would encourage anyone that doesn't want to use Docker to simply not use Docker. As mentioned above there is a section in the manual that deals with custom installations - there are a few additional changes required for 1.8, but nothing too troublesome for someone with a little technical background. As for your issue of it not pulling builds - it will be trying to connect to Docker hub (an online repository for Docker containers), perhaps something is blocking that connection.

We switched to Docker for several reasons, the principle one being the introduction of Push Messaging (via something called ZeroMQ). ZeroMQ can be difficult to install, so wrapping it all up in a "docker" container made a lot of sense to us. In the past we've also spent many many hours on support incidents that turned out to be a problem with the environment rather than Xibo - Docker eliminates this as everyone is effectively running on the same environment. We found Docker easy to get to grips with, having used it with other software packages, however I can understand that it is something new to learn. We've tried our best with the installation process and the information we've presented - however there are complaints about it being unclear. Dockers own instructions are not fantastic, which doesn't help. Unfortunately for more our instructions bleed into Docker instructions, the less clear it gets. There are two main pages: - Install Docker (Xibo Documentation) - Install Xibo (Xibo Documentation) If you have Docker working already, getting a fully working Xibo system running on Port 80 is a case of: - Download and extract the release archive - Copy and edit config.env.template - Run `docker-compose up -d` A "custom installation", which is an installation via the traditional method of configuring your own web server and database, is very much still an option and is covered in our user manual under "Custom Installation". We've said that we might not be able to provide community support for issues with this type of installation because if there is an issue we can't recreate in a Docker install, it is most likely an environment issue. We will still do our best to help, but issues of this nature might ultimately need commercial support.