my favorite: 2010-10-21T10:11:16-07:00 app[web.2]: Company acquired /_party (0.1ms)
Only a partial party?
I guess they would be re-using it multiple times, hopefully...
Heroku Gets Sweet Logging
11–20 of 25 posts
Re: Heroku Gets Sweet Logging
#12$ heroku logs --tail
! Realtime tail and filter are not available with basic logging, please upgrade to expanded logging
:(
Re: Heroku Gets Sweet Logging
#13Prolly 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?
Re: Heroku Gets Sweet Logging
#14Prolly 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?
I use the paperclip gem and store files on S3 with my Heroku apps and it works great. I believe this approach is very common.
Re: Heroku Gets Sweet Logging
#15Prolly 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?
I'm guessing they said that because Heroku doesn't let you save files to their system. You have to use something like s3. Other than that, I see no reason why someone would say that.
You can save things to the tmp directory for a little while. The files should last long enough to do some work on them. For example, I've had an app parse an uploaded XML file that gets saved in tmp. This might not be a good practice, but I don't feel like setting up anything special for that app.
Re: Heroku Gets Sweet Logging
#16Prolly 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?
I use the paperclip gem and store files on S3 with my Heroku apps and it works great. I believe this approach is very common.
I too am implementing paperclip...but I am wondering about backing up the uploads. How do you backup those uploads? I was thinking that I would store the first copy on the host - then push them to s3 for backup (and maybe 1 other CDN, just to be ultra paranoid).
But, it seems to me, that if you are just passing through Heroku altogether - that removes one point of fault tolerance and redundancy - right?
Re: Heroku Gets Sweet Logging
#17Re: Heroku Gets Sweet Logging
#18Until the Advanced functionality is rolled out publicly, does anyone have suggestions for logging all requests to something like S3? I was going to write my own this afternoon since I couldn't find anything. I see the market currently providing two options, neither of which encompass my use case. 1) Exception Logging via existing Heroku addons like Exceptional 2) Tracking via javascript, e.g. Google Analytics The pro…
S3 is not the best AWS for the functionality you seek: http://aws.amazon.com/simpledb/usecases_logging/
Re: Heroku Gets Sweet Logging
#19Prolly 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 to mention that I (using Rails on Heroku) have been handling uploads by using direct pre-authorized posting to S3 and it has been very nice to work with.
Re: Heroku Gets Sweet Logging
#20Prolly 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…
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.