As a tool to learn Docker, I have created a Docker image to create a container that hosts and runs the River4 RSS Agreggator. The image is available in a public repository in the Docker Hub. The container has everything needed to run River4, including a sample RSS reading list. Unfortunately, the current iteration does not include a way to make changes to the reading list, nor is the application state saved when you stop the container. I have more studying to do about how persistence and data storage is done in containers.
Here are some notes for how to obtain and use the container for those who are familiar with Docker.
Obtain the image by running docker pull fmcpherson/river4
To run River4 as a background process using the default port 1337 enter docker run -p 1337:1337 -d fmcpherson/river4. Note that the -p 1337:1337 portion of this statement provides the port mapping, the left side of the colon indicates the host server port, the right side has the port the application is expecting for communication. If you want you can map River4 to port 80 by entering -p 80:1337 in the run command.
If you want to see the server output of the server running in the background, you need to first get the container ID using the docker ps command, the enter docker logs [container id]
If you want to run River4 interactively so that you see the server output enter docker run -p 1337:1337 -t -i fmcpherson/river4 /bin/bash
If you are running Docker on a physical computer, you can access the River4 app by entering http://localhost:1337 in a web browser
If you are running Docker on a virtual server, or if you want to access the River4 app from a computer on your network other than the one hosting Docker, you will need to obtain the IP address of the host and then enter http://%5BHost IP address]:1337
from Notes http://ift.tt/1IFC34X
via IFTTT
Notes From The Cave 