dailab/across-fileserver repository overview

OWL-S File Server to be used in the AcRoSS project. The code is the same as in the generic OWL-S file server, but this comes with an AcRoSS-specific node configuration and some pre-installed resources.

This file server can be started as a Docker image. First, you have to have a JIAC gateway, otherwise the file server can not communicate outside of the Docker to other JIAC nodes. You can start a gateway with Docker, too:

docker run -p 45678:45678 dailab/jiac-gateway

Then, you can start the file server connecting to the same gateway using the gateway parameter. If the parameter is not given, then the node will use JMX multicast communication only. You will also have to sync the file server's repository (where files are stored) with some local directory, otherwise all new files will be lost when the image is restarted. Note: If you sync the repo directory itself, it will be considered already existing and no files will be created; instead, sync the parent directory. You also have to provide the IP to the MQTT broker mqttIP and, if necessary, the login mqttLgn and password mqttPwd. For example:

mkdir ~/REPO
docker run -p 8080:8080 \
           -e gateway=172.17.0.1 \
           -e mqttIP=172.17.0.1 \
           -v ~/REPO:/root/.across/
           dailab/across-fileserver

When everything worked well, then the file server will provide a (read-only) web interface at http://localhost:8080/.