wideskycloud/edge repository overview

⁠Widesky Edge

See our documentation⁠ for detailed information.

⁠How to run

To start the Widesky-edge in its simplest form, binding to an external port 7788.

docker run -it -p 7788:80 --name myEdge wideskycloud/edge:latest

Then go to your browser and type in the url http://localhost:7788/ to access the web application. Use admin/admin to login.

⁠Persisting data

By default, data within a docker container are lost when they are re-created. To avoid losing your work, we recommend that you preserve the data by using the --volume option of docker. You can do so by mounting a host's directory to the running container's /var/lib/widesky-edge directory.

Example:

docker run -it -p 7788:80 -v `pwd`/myData:/var/lib/widesky-edge  --name dataExample wideskycloud/edge:latest

The example above assumes you have a directory named myData in the current working directory.

⁠Environment variables

⁠HTTP_PORT

By default, the Widesky edge application is configured to serve from port 80. To reconfigure this, the environment variable HTTP_PORT can be used to alter this behaviour.

Example:

docker run -it -e HTTP_PORT=5566 -p 7788:5566 --name myEdge wideskycloud/edge:latest

⁠ADMIN_USER and ADMIN_PASSWORD

This set of credentials can be changed if the environment variables for ADMIN_USER and ADMIN_PASSWORD are defined.

Example:

docker run -it -e ADMIN_USER=myAccount -e ADMIN_PASSWORD=myPassword --name myEdge wideskycloud/edge:latest

For this instance, the administrator account will be seeded as myAccount/myPassword.

⁠SERVE_FROM_SUB_PATH

The Widesky edge application may be served from a subpath such as http://example/wideskyedge.

In this case the sub path is wideskyedge.

To do so, the environment variable SERVE_FROM_SUB_PATH can be set to wideskyedge.

Example:

docker run -it -e SERVE_FROM_SUB_PATH=wideskyedge --name myEdge wideskycloud/edge:latest