I wrote
a post several years ago on this topic, but decided to refresh it since some of the links don’t work any more…and also because I am setting up a new river for
Ron Chester….
In the same vein as “own your data” or “supporting the open web”, it’s important for users to be able to set up their own tools for collecting/reading information on the Web, and not be dependent on other people’s tools. Having said that, I have been happy to provide a river resource for the 1999er community (http://1999bloggers.andysylvester.com/). This post will help you to do the same for any blogs/feeds that you are interested in following.
There are two pieces to the river resource given above:
1. A installation of the River5 RSS aggregator running on a server
2. An HTML page that displays a river or rivers created by River5
At the River5 Github site (https://github.com/scripting/river5), there are several tutorials in the site wiki on installing River5:
Another option is to buy my book on setting up an Ubuntu server on Amazon Web Services (the last chapter shows how to set up River5)….
Once you have River5 set up on a public server and creating river files (Javascript files that can be read/displayed by other applications (for example, 1999bloggers.js)), you have some options for being able to display those files. When River5 is running, you can direct people to the public display of the rivers being created. An example can be seen at http://fedwiki.andysylvester.com:1337, which is my main River5 installation. This install is creating multiple rivers, which are displayed in multiple tabs. If you only had one river, you would see only one tab.
Another option for making your river public without pointing to the River5 app display is to use a separate HTML page that accesses the river files. Dave Winer has created a toolkit for display of River5 river files (https://github.com/scripting/riverBrowser). To test the app, copy two files from the repo (frozenriver.js and riverbrowserdemo.html) to a directory on a web server. You should then see the contents of the frozen river file as shown in Dave Winer’s demo app.
To set up your own public display of a River5 river, make a copy of the riverbrowserdemo.html file. Next, edit the file and find the line with the phrase “httpGetRiver”. It should look like this:
httpGetRiver(“frozenriver.js”, “idRiverDisplay”, function (){
Next, you will be replacing the text “frozenriver.js” with a URL to a list in your River5 installation. For example, I have a file called readinglist.txt, which contains a list of over 40 RSS feeds that I follow. When your River5 installation is running, you can feed a URL corresponding to a River5 list of feeds that you have created. The following is the line of Javascript from above with the URL for readinglist.txt from my server:
httpGetRiver (“http://fedwiki.andysylvester.com:1337/getoneriver?fname=readinglist.txt”, “idRiverDisplay”, function (){
For your setup, replace the URL part (http://fedwiki.andysylvester.com:1337) with the URL for your River5 server, and replace the text following “fname=” (readinglist.txt) with the name of your file in the lists folder within your River5 installation. Finally, upload the HTML file to a server. As long as the River5 server is running, your HTML page will display the latest version of the river. An example is available at http://andysylvester.com/files/riverbrowserdemo.html.
OK – now get started making rivers!
