Test-VM¶
How to access the test-VM¶
The test/prod machines wont have a GUI. Because they will only be accessible via the dev-VM which means it is ssh only.
- Log on to space-rshiny-dev
- Open a terminal window
- From the command line
ssh space-rshiny-test
has a key set up and will log you in directly (without asking for your password) - Although ssh-key authentication is in place from dev to prod and test, we recommend changing the passwords the first time you log on, using 'passwd' from the command line.
How to transfer apps from the dev-VM to the test-VM¶
To transfer an app from one VM to another, it it sufficient to transfer the docker image of the app.
Check the app's docker image name on the dev-VM
Bash
ebreitmoser@space-rshiny-dev:~$ docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
tomtest latest cade5d53c27e 42 hours ago 1.05GB
babynames latest 9cbbe0be983b 6 days ago 1.05GB
openanalytics/r-base latest dc8921f0456d 3 months ago 588MB
hello-world latest d1165f221234 5 months ago 13.3kB
openanalytics/shinyproxy-demo latest 9a83d7d80ebf 2 years ago 925MB
Create a tarball of the docker image you want to transfer, e.g. 'babynames'.
Text Only
docker save babynames > babynames.tar
Copy the tarball to the test-VM
Text Only
scp -r babynames.tar ebreitmoser@space-rshiny-test:/home/ebreitmoser
Load the image into the local registry using command 'docker load ' and check if it is there by running 'docker images'
Text Only
docker load < babynames.tar
docker images
ebreitmoser@space-rshiny-test:~$ docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
babynames latest 9cbbe0be983b 6 days ago 1.05GB
Then the same procedures as desribed under 503328396503328396 has to be followed to add the app to the configuration file application.yml on the test-VM. You will need some information from the dev-VM/the developer:
- the diplay name the app is supposed to get (TBC by SPACe who is responsible for deciding titles etc)
- the description
- the container-cmd