News and updates about the River2 aggregator.
Storing your rivers in Amazon S3
The reason to store your rivers in Amazon S3 is that you get the infinite scaling of S3, compared to the very finite scaling of EC2 (esp if you’re using a micro-instance).
1. If you haven’t already done so, configure the OPML Editor for S3.
2. Using the AWS dashboard, create a new S3 bucket. You can name it whatever you like, but it must be unique across all of S3. If your initials are BM, something like bmRiverBucket probably will be unique. Remember what you named the bucket.
3. Using your remote desktop app, access your server. On the server machine, bring the OPML app to the front.
4. Bring config.root to the front.
5. Navigate to config.river2.prefs.static.
6. In s3Path, enter a forward-slash (/) followed by the name of your bucket followed by a forward-slash. Something like /bmRiverBucket/.
7. Set flSynchToS3 to true.
8. You can leave s3Url empty, River2 will fill it in for you.
After your next scan, look in the bucket. If it worked, you should see your static files, a full set for each user, and one for your main river.