All components in the Fabscape system run in Docker Containers, making it a prerequisite necessary to run Fabscape. For more on Docker containers visit the Docker CE Installation page. Please note that in production mode (on-premise or standalone) Fabscape currently only supports CentOS 7.5 due to the requirement of OpenShift 3.9.0.
In development mode you may run Fabscape simply in Docker without OpenShift. You should be able to run Fabscape in virtually any environment that is supported by Docker but we have not tested every environment. The environments we have tested to work are as follows:
- CentOS 7.x
- Ubuntu 16.x
- MacOS 10.13.x
Note that although it may seem convenient to simply run Fabscape this way even for production environments, this is not recommended since you would not be able to take advantage of many of the security and reliability features which require OpenShift.
When developing a plugin or driver, running Fabscape in Docker works well for testing its functionality. However, it is important to test your final plugin/driver in a production environment since OpenShift can cause some communication issues with your plugin/driver due to some security features which wouldn’t be present in a Docker environment.
To install your Fabscape developer environment you must first download the Fabscape Platform & Console Developer Build. Once you have downloaded the package file unpack it and proceed with the following steps.
- Run “docker login” with an account with fabscapeorg access
- Change the .env file contents to run the docker version tag on the fabscapeorg docker repo for example: 9.0.0
- For that example you would change the line in the .env file to “FABSCAPE_VERSION=9.0.0”
- If you’re unable to find a .env file, make sure you show hidden files.
- Run “docker-compose up”
Note that you must have permissions to access the Fabscape private repositories on Docker Hub so if you don’t already have it please contact your Gigaphoton representative.