$ heroku logs --tail ! Realtime tail and filter are not available with basic logging, please upgrade to expanded logging :(
Heroku Gets Sweet Logging
21–25 of 25 posts
Re: Heroku Gets Sweet Logging
#22Prolly not the place to ask this...but I will go ahead anyway...I recently heard that if you have a Rails app that will be accepting files from users (e.g. say images/videos being uploaded) Heroku is not the best host to use. Anyone have any thoughts/experiences with that? Is that complete rubbish or is there truth to it and why?
AFAIK, if you have a Rails app that will be accepting files from users, Rails is probably not the best thing to use. Ruby likewise, short of using something evented (and I say this as someone thoroughly enjoying working with both Ruby and Rails.) Seeing as you'll be tying up processes rather quickly that way, no? That aside for the moment, and based on your S3-related comments nested below, I thought I might pop by t…
It's not so much the S3 storage I am concerned about. It's more the allowing me to backup everything properly, concern I have.
Re: Heroku Gets Sweet Logging
#23Re: Heroku Gets Sweet Logging
#24Earlier quoted context omitted.
AFAIK, if you have a Rails app that will be accepting files from users, Rails is probably not the best thing to use. Ruby likewise, short of using something evented (and I say this as someone thoroughly enjoying working with both Ruby and Rails.) Seeing as you'll be tying up processes rather quickly that way, no? That aside for the moment, and based on your S3-related comments nested below, I thought I might pop by t…
What I am handling is basically what Basecamp is handling. If Ruby and Rails can manage Basecamp, then it sure can manage what I am doing. It's not so much the S3 storage I am concerned about. It's more the allowing me to backup everything properly, concern I have.
Re: Heroku Gets Sweet Logging
#25Earlier quoted context omitted.
AFAIK, if you have a Rails app that will be accepting files from users, Rails is probably not the best thing to use. Ruby likewise, short of using something evented (and I say this as someone thoroughly enjoying working with both Ruby and Rails.) Seeing as you'll be tying up processes rather quickly that way, no? That aside for the moment, and based on your S3-related comments nested below, I thought I might pop by t…
If you're using something like Passenger, I believe it does the upload in nginx/apache to a tempfile and then hands it off to Rails.