Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
doc:docker [2019/08/16 12:02] – [Installing dockerized KnowRob] daniel86 | doc:docker [2019/08/19 13:10] – [Installing the docker daemon] daniel86 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Setting up your own openEASE server | + | ====== Setting up your own openEASE server ====== |
- | This page collects information on the installation and usage of KnowRob with [[http:// | + | This page collects information on the installation and usage of openEASE, a web-service based on [[http:// |
+ | You can follow the steps described here for any Ubuntu version that has docker independently of the Ubuntu version running inside of openEASE. | ||
- | ===== Installing | + | ===== Installing |
Firefox is by far the most tested browser. Packages in ubuntu repositories should work with KnowRob. | Firefox is by far the most tested browser. Packages in ubuntu repositories should work with KnowRob. | ||
Line 13: | Line 14: | ||
When the Browser is installed check that [[https:// | When the Browser is installed check that [[https:// | ||
- | ===== Installing the Docker | + | ===== Installing the docker |
Install Docker following the instructions at https:// | Install Docker following the instructions at https:// | ||
After installation, | After installation, | ||
+ | In addition, you will need to install docker-compose which is used for the orchestration of the openEASE application. | ||
+ | Install instrucitons for docker-compose can be found here: https:// | ||
- | ===== Installing dockerized KnowRob ===== | ||
- | The next step is to clone the KnowRob Docker | + | ===== Installing openEASE ===== |
+ | |||
+ | The next step is to clone the openEASE | ||
git clone https:// | git clone https:// | ||
- | ===== Setting up WebSocket | + | ===== Setting up WebSocket |
Clients can communicate with the openEASE webserver using SSL encryption. | Clients can communicate with the openEASE webserver using SSL encryption. | ||
For local testing you can generate a certificate with following commands: | For local testing you can generate a certificate with following commands: | ||
- | cd ./nginx-proxy/certs/ | + | cd ./openease/certs/ |
./ | ./ | ||
- | |||
- | This certificate must be included in the web server container (the certificate will be mounted as host volume inside of the docker container). Make sure to remove any old web server container | ||
- | that doesn' | ||
- | docker rm -f nginx | ||
**// | **// | ||
- | ===== Setting up Experiment Logs ===== | + | ===== Setting up experiment logs ===== |
+ | |||
+ | **NOTE: this is subject of change, experiment logs will be inserted differently soon (DB 08/19)** | ||
Experiment logs can be downloaded via a public FTP server that is hosted in the network of | Experiment logs can be downloaded via a public FTP server that is hosted in the network of | ||
Line 58: | Line 60: | ||
The volume container is automatically created based on the environment variable next time you start the openEASE webserver. | The volume container is automatically created based on the environment variable next time you start the openEASE webserver. | ||
- | ===== Setting up Admin User ===== | + | ===== Setting up admin user ===== |
The admin user is automatically created when the webserver starts for the first time. | The admin user is automatically created when the webserver starts for the first time. | ||
Line 70: | Line 72: | ||
**// | **// | ||
- | ===== Setting up Password Recovery ===== | ||
- | |||
- | For production servers, you might want a working password recovery mechanism. | ||
- | This requires a mail account that is used for sending the recovery mails. | ||
- | Add two more environment variables to the .bash.rc: | ||
- | export OPENEASE_MAIL_USERNAME=" | ||
- | export OPENEASE_MAIL_PASSWORD=" | ||
===== Selecting a ROS distribution ===== | ===== Selecting a ROS distribution ===== | ||
Line 84: | Line 79: | ||
export OPENEASE_ROS_DISTRIBUTION=" | export OPENEASE_ROS_DISTRIBUTION=" | ||
- | It is required, that you have a container named '' | ||
- | locally installed. | ||
===== Setting up mesh repositories ===== | ===== Setting up mesh repositories ===== | ||
+ | **NOTE: this is subject of change, meshes will be part of episodic memory soon (DB 08/19)** | ||
+ | |||
Meshes can be downloaded from custom **git** or **svn** repositories. | Meshes can be downloaded from custom **git** or **svn** repositories. | ||
This information must be included in the environment, | This information must be included in the environment, | ||
Line 107: | Line 102: | ||
export TWITTER_APP_SECRET " | export TWITTER_APP_SECRET " | ||
- | ===== Launching the Web interface | + | ===== Setting up password recovery (optional) |
- | The Web interface runs in its own container. On the one hand, this app provides the Web GUI, on the other hand it manages the container infrastructure, | + | |
- | | + | For production servers, you might want a working password recovery mechanism. |
+ | This requires a mail account that is used for sending the recovery mails. | ||
+ | Add two more environment variables to the .bash.rc: | ||
+ | export OPENEASE_MAIL_USERNAME=" | ||
+ | export OPENEASE_MAIL_PASSWORD=" | ||
+ | |||
+ | ===== Launching openEASE ===== | ||
+ | openEASE uses //docker-compose// | ||
+ | |||
+ | docker-compose up | ||
| | ||
Then you can connect to the Web interface at https:// | Then you can connect to the Web interface at https:// | ||
- | ===== Setting up Mongo Logs ===== | + | ===== Setting up mongo server |
Mongo dumps are included in the episode data downloaded from the FTP. | Mongo dumps are included in the episode data downloaded from the FTP. | ||
Line 124: | Line 127: | ||
right most column in order to import the mongo logs for one of the experiments. | right most column in order to import the mongo logs for one of the experiments. | ||
- | ===== Build own containers ===== | ||
- | If you modified something in openEASE web app, you can build the respective containers using | ||
- | |||
- | ./ | ||
- | | ||
- | If there are changes in KnowRob repo, you can rebuild the KnowRob container image using | ||
- | |||
- | ./ | ||
- | |||
- | It is suggested to run these two builds also after a fresh installation. | ||
===== Offline openEASE ===== | ===== Offline openEASE ===== | ||
+ | **NOTE: this is not supported as of 08/19, but the feature will be added again at a later time | ||
+ | ** | ||
openEASE is a webapp and thus components may require active internet connection. | openEASE is a webapp and thus components may require active internet connection. | ||
Line 190: | Line 185: | ||
sudo service mongodb stop | sudo service mongodb stop | ||
| | ||
- | ==== when i try to browse my openEASE instance, I end up in a " | ||
- | |||
- | please follow these steps: | ||
- | ./ | ||
- | docker rm docker-gen nginx | ||
- | ./ | ||
==== Other docker problems ==== | ==== Other docker problems ==== |