Infrastructural changes

[jenzopr]

Here, I will collect commits that change the infrastructure of the repository a bit 😉

[jenzopr]

Details

• I updated the README file to contain less information and more structure. Especially, I put the focus on How to get the app running and How to get my data into it (see 9219fb3)
• I cleaned up the Dockerfile and made it much simpler. Now, it is based on the rocker/shiny image and we do not need to install shiny ourselves any more. A feature of the new image is that it is configurable using env variables during docker run. For example, using docker run -e WILSON_LANDING_PAGE='feature_selection' will directly show the Feature Selection page of Wilson (see 89a0211 and 6f4c744).
• I moved the location of the Dockerfiles into the wilson-basic folder. This removes the necessity to clone and download the Wilson-Apps repository during docker build. The workflow to build the container is now git clone; cd wilson-basic; docker build . (see 89a0211).
• Custom data is easily included in the container by moving it into the data subdirectory. Mounting a external_data directory is still possible (see 89a0211).
• Although I removed old Docker files, they are still available in the Backup Release.
• I implemented jinja2 templating for the Shiny server configuration and the app configuration, which enables container customarization during docker run. This can easily be extended to more variables (see 6f4c744 and 89a0211).

[ckuenne]

seems ok to me. but including jinja for one and a half parameter seems a bit overdeveloped to me. :)

[jenzopr]

I agree - however, it allows to integrate much more parameters (e.g. logging) to be controlled from outside the container..