New screencast for River4 Amazon S3 Heroku setup

52 views
Skip to first unread message

Andy Sylvester

unread,
Jul 27, 2015, 12:43:47 AM7/27/15
to river4
I have created a new screencast showing how to set up a River4 site using Amazon S3 and Heroku:


Also, I have added a screencast on using the River4 console app for local River4 installs:


Let me know what you think!

Andy Sylvester

Frank McPherson

unread,
Jul 27, 2015, 7:24:15 PM7/27/15
to river4

The Heroku screencast is private so it won't play for me.  


--
GitHub repository: https://github.com/scripting/river4
How to ask for help: http://scripting.com/2014/03/19/howToAskForHelpWithSoftware.html
---
You received this message because you are subscribed to the Google Groups "river4" group.
To unsubscribe from this group and stop receiving emails from it, send an email to river4+un...@googlegroups.com.
To post to this group, send email to riv...@googlegroups.com.
Visit this group at http://groups.google.com/group/river4.
To view this discussion on the web visit https://groups.google.com/d/msgid/river4/aa9ea1b7-ed9c-428b-a8e5-a6135cd05d87%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Andy Sylvester

unread,
Jul 28, 2015, 12:49:03 AM7/28/15
to river4, frank.m...@gmail.com
Ooops! Thanks for letting me know, I have fixed the problem, you should be be able to view the video now.

Andy Sylvester

Anton Zuiker

unread,
Sep 4, 2015, 9:54:23 PM9/4/15
to river4
Andy, 

Many thanks for your tutorial video. I followed it to get my Duke River running at river4.dukeriver.co.

One point of confusion for me, though.

In the tutorial, in the DNS Setup for Domain Name section, you show how you pointed 'rivertest' to an Amazon S3 endpoint. When I pointed my domain, river4.dukeriver.co, to my Amazon s3 endpoint, there was nothing there to serve up (Amazon said no permissions, in effect). So, instead, I pointed river4.dukeriver.co to dukeriver.herokuapp.com and that served up my river (because river4.js on heroku was pulling info from S3, right).

Perhaps I misunderstood your tutorial? If not, could it be corrected to make the DNS/CNAME step clearer?

Also, since I successfully stood up the Duke River, river4.js has been updated (v0.120), but my heroku app is synched to the older version (v0.117a). Any plans to produce another video in your series to show how to update github/heroku?

fwiw, I have outlined the Duke River project, and am doing my best to narrate my work, at bit.ly/dukeriverinfo

Anton

Andy Sylvester

unread,
Sep 5, 2015, 1:20:36 AM9/5/15
to riv...@googlegroups.com
Anton,

Great work on setting up your river - looks good! Here is some info regarding your questions.

When you could not see anything from your Amazon S3 endpoint, it could be that River4 had not run long enough to create any rivers and write the files to Amazon S3. It seems like you have found another way to be able to view your content. Assuming that you did all the steps in the video, all of the files should be visible in your Amazon S3 account. The River4 Heroku app does read and write information from Amazon S3, but Heroku does not provide any file storage, that is the reason for having a service like Amazon S3 as part of the entire package. I may do some experiments with the rivertest river to check out your setup.

I am definitely interested in improving the videos. After my experiments, I might do an update on this one. I agree that it would be a good idea to have a video on how to update a Heroku app that has a newer version. I used the method in the video so that users would not have to have Git installed to be able to set up River4, but I see now that there is a need to be able to deploy app updates. I am working on setting up another River4 website, but I think Heroku app updates would be the next logical video.

If you have some more questions, feel free to post them to the list. If you would like to talk, email me at sylvest...@gmail.com and we can set up a time (I am in the Pacific time zone).

Andy Sylvester



--
GitHub repository: https://github.com/scripting/river4
How to ask for help: http://scripting.com/2014/03/19/howToAskForHelpWithSoftware.html
---
You received this message because you are subscribed to the Google Groups "river4" group.
To unsubscribe from this group and stop receiving emails from it, send an email to river4+un...@googlegroups.com.
To post to this group, send email to riv...@googlegroups.com.
Visit this group at http://groups.google.com/group/river4.

Adam Monago

unread,
Nov 23, 2015, 5:03:50 PM11/23/15
to river4
Hi Andy,

I was able to successfully set up River4 on my Mac without any problem.

I decided to follow your tutorial for setting up on Heroku with S3 storage.  I've completed the tutorial but found that my bucket never populates with the index and json files.  After some investigation I can see that index.html does not exist. It also appears that river4 never actually runs on Heroku, even though the deployment was successful.

Any thoughts on what could potentially be missing?  I've gone through the steps a couple of times and have not been able to deduce what's wrong.  

Here's a screenshot of what you see when I try to hit the domain - Note that my redirect is working and I get the same message with a direct hit to the AWS address:


Many thanks,
Adam

Andy Sylvester

unread,
Nov 23, 2015, 10:30:15 PM11/23/15
to riv...@googlegroups.com
Adam,

Here are several ideas to try to get some quick info:

1. Use an addon app in Heroku to be able to view the console log messages from your app on Heroku (I have added the Papertrail app, there is a free version available). There may be some obvious errors that you could post to the list and assist with the debugging.
2. Check your config variables in Heroku. I once had a problem where I thought the app was not working, the reason was that I had a typo in one of the config variables.
3. Upload a file to your S3 storage to make sure that files can be written to S3.

Looking forward to helping you with your setup and seeing your river online!


Andy Sylvester


Adam Monago

unread,
Nov 24, 2015, 10:07:11 PM11/24/15
to riv...@googlegroups.com
You're a good man, Andy Sylvester. As suspected, I double checked my environment variables and realized I was putting the whole endpoint address into the s3path variable, instead of the bucket name. :) 

We seem to be rolling now.  Thanks for the Papertrail rec, I've installed that and like it so far.

Will let you know how we go.

-Adam

You received this message because you are subscribed to a topic in the Google Groups "river4" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/river4/6SJPtqCkyRY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to river4+un...@googlegroups.com.

To post to this group, send email to riv...@googlegroups.com.
Visit this group at http://groups.google.com/group/river4.

For more options, visit https://groups.google.com/d/optout.

Adam Monago

unread,
Nov 25, 2015, 1:17:29 AM11/25/15
to river4
Sorting out the s3path got things running on Heroku. I now have all of the feed and river data making its way to S3.

Strangely though, the index.html file never gets generated and therefore I'm still not getting the call to the custom domain to resolve.

I can upload files into the bucket by hand, but not sure why it's not getting generated automatically.

Any tips welcome.

-Adam
Reply all
Reply to author
Forward
0 new messages