Re: PDF Generation on Heroku
Has your gmail id been hijacked? I'm relying to this note attached note On 26 February 2011 00:51, kumari s kumari...@gmail.com wrote: http://groups.google.com/group/super-star20011 a href=http://www.PaisaLive.com/register.asp?2024379-5217218;bfont color=#FF size=4Earn upto Rs. 9,000 pm checking Emails. Join now!/font/b/aa href= http://www.PaisaLive.com/register.asp?2024379-5217218;bfont color=#FF size=4Earn upto Rs. 9,000 pm checking Emails. Join now!/font/b/a http://www.PaisaLive.com/register.asp?2024379-5217218 http://www.PaisaLive.com/register.asp?2024379-5217218 http://www.PaisaLive.com/register.asp?2024379-5217218 http://www.PaisaLive.com/register.asp?2024379-5217218 http://www.PaisaLive.com/register.asp?2024379-5217218 On Sat, Feb 26, 2011 at 6:06 AM, Josh Coffman joshcoff...@gmail.comwrote: I've used Prawn/Prawnto to generate pdf's on heroku, which were then either downloaded or attached to an email. Worked well for me. On Fri, Feb 25, 2011 at 10:13 AM, kumari s kumari...@gmail.com wrote: http://www.PaisaLive.com/register.asp?2024379-5217218http://www.paisalive.com/register.asp?2024379-5217218 On 2/25/11, John Beynon j...@beynon.org.uk wrote: We're faced with having to generate PDFs on Heroku - we've been looking at wickedPDF and taken a look at the new heroku addon DocRaptor. I'm curious with DocRaptor - with their Ruby example at http://docraptor.com/examples (Rails tab) - where does Heroku's involvement end - is a dyno 'busy' throughout? For example a pdf link is clicked which is then passed over to DocRaptor via a post (consuming a Dyno) and then waits for the response to be generated and then streamed back to the same dyno which then sends the data to the client browser - so a dyno is essentially busy throughout this process from when the link is clicked, waiting for the response and then returning the data to the client browser? What we're looking at is being able to generate PDFs without consuming precious dynos - I've seen mentions of using DJ for background processing but we want the user to able to click a button which kicks of the PDF generation and shows them 'Generating' and then when the doc is ready send it to the client but I'm thinking that may need writing to tmp to then serve back? Any one done anything similar? Any ideas? John. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Download rate 260 KB/s
I believe the charges for an additional dyno(s) are usage based so it would be a relatively cheap experiment to add a dyno and do a test. I could be wrong in that there may be some flat charge in going from a free plan to a paid but I don't remember that being the case - it would be documented somewhere on the Heroku site. So add a dyno check the dl rates and then remove the dyno or better yet keep it in place for a month and enjoy the immediate response vs the delayed response of a first page hit (after an idle period of some minutes) while the single dyno spins up. A paid plan keeps the dynos spinning and available. On Jan 25, 11:46 am, obruening ollibruen...@googlemail.com wrote: I have a rails app installed on Heroku. It uses the 1 dyno free plan. I have measured the download rate with the download of a static file (200KB) from the rails public folder. The result is 260 KB/s. Are there better higher download rates in the paid plans? Best regards Oliver -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Internal Server Error After a db:push
On Jan 8, 10:01 pm, Scott LaBounty slabou...@gmail.com wrote: When I do a heroku db:push, I get the following ... Loaded Taps v0.3.14 Warning: Data in the app 'freezing-sunset-75' will be overwritten and will not be recoverable. ! Internal server error This has worked in the past, but didn't work even after I rolled back the database to the previous version. Any ideas? -- Scotthttp://steamcode.blogspot.com/ Since db:push worked four you in the past - have you updated your heroku gem recently? Latest version is 1.16.2 -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: rails 3.0.3 bundle - tread carefully!
I also had to revert back from 3.0.3 to 3.0.1 - the Paperclip gem gave a temp_file method not found error msg while attempting to upload an image. On Nov 24, 4:20 pm, mattsly matt...@gmail.com wrote: I just had an exciting afternoon-before-thanksgiving...I read all the goodness at:http://weblog.rubyonrails.org/2010/11/15/rails-3-0-3-faster-active-re... ...about better perf and low-risk changes with Rails3.0.3, so I did a local upgrade from 3.0.1, ran some tests, everything seemed fine, pushed to staging, ditto, pushed to prod, ditto...went out to do some errands. And then got a crash alert: 2010-11-24T12:35:55-08:00 app[worker.1]: Could not find columnize-0.3.1 in any of the sources boom! Rushed home, rolled back to 3.0.1... I'm still not sure exactly what happened - trying to diagnose now. But clearly some funkiness w/ dependency management btwn versions, as Rails3.0.3doesn't seem to install columnize (or linecache-0.43, possibly more) whereas they do get installed when Rails = 3.0.1. If anyone else has thoughts, please jump in. But, at the very least, consider this a public service announcement that the 3.0.1 -3.0.3 upgrade doesn't appear to be vanilla. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Can heroku db:pull db:push specify tables?
On Nov 3, 7:42 am, femto femto...@gmail.com wrote: Hello all, I need to sync some tables between server and local, Can heroku db:pull db:push specify tables? Not that I'm aware of with heroku db:push. However, using Rails, you could use seed data as a (much more involved) way of accomplishing the same thing. Here's Ryan Bates video segment on the topic: http://railscasts.com/episodes/179-seed-data If the table itself has been changed (change of attributes for instance) then naturally you'll need to do a heroku rake to do a migration drop and then migration up of the table itself. If you go this route - a suggestion which I'm sure you would do - but just in case - be sure to do a full trial run of the whole sequence on your dev machine - table down using current migration file, table up using a new modified migration file (for the case where you are modifying the table structure) and finally creating a csv seed file (sqlite web site has tool for this) http://www.sqlite.org/download.html and then the creation of the seed.rb file (again see Ryan Bates segment). Only reason I mention this is it took me a good number of tries on my dev machine to get everything to work and get the result I wanted - there were some subtle issues with the way sqlite was creating the csv data - at least to me they were. It'd be great to have heroku do one table pushes - maybe an enhancement if it's not yet possible - please ... -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: wonderful platform for app staging...
I believe Rails 3 works with Ruby 1.8.7: http://edgeguides.rubyonrails.org/getting_started.html I think it is only a couple of p releases of 1.8.7 that cause problems (see above link) ... later versions of 1.8.7 are available - for windows at least and I think archived versions of 1.8.7 would be available for other OS's On Sep 19, 1:26 pm, kadoudal kadou...@gmail.com wrote: I subscribed recently to Heroku and found how easy it is (together with GitHub) to deploy apps and test them 'live' HOWEVER all new Rails applications are to be designed with the pair Rails3-Ruby1.9.2 as they have been released unfortunately Heroku does support Rails3 only with Ruby 1.8.7 at the present time... and I have to go back to my old staging deployment environment... I hope they will support 1.9.2 asap , any idea of when this could happen ?? matter of weeks.. months.. quarters.. hungry now ... -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: free vs. paid heroku app performance
I think I have to agree with Stefan - *particularly* when it comes to staging. Why not take the cheapest entry level package for staging for a month - any outfit that advertises rock solid ruby platform should give good to excellent service for even the cheapest paid-for package. I totally agree with your previous post and its sentiments - the need to be aware of, and working on, the problem when the client calls at 2:00 a.m. is critical - it has to be one of the worst feelings ever to have your client inform you the site is down and not be aware of it. However the discussion started on the topic the free account's (staging) performance ... doesn't surprise me it's poor to fair ... On Aug 28, 1:43 pm, David datab...@gmail.com wrote: It's in the best interest of any web site operator to know when their web site is down external from your hosting company regardless of platform, language, or baseline hosting provider's functionality. When I get a phone call at 2am that the web site is down, I should already be on it. It just happens that it has the same benefits for spun down processes. I understand where you're coming from in regards to all the free sites but most likely the operators of those sites are leveraging Varnish and site monitoring is simply going to hit the same cached route. We can only work with what we have, if they want it done differently - give us the option. Besides, I pay plenty a month for it to work in my situation. /david. On Aug 27, 10:52 am, Stefan Wintermeyer stefan.winterme...@amooma.de wrote: Am 27.08.2010 um 15:27 schrieb David: That's what we do, setting up site monitoring is part of my normal routine so I have something checking the site every 5 mins including staging. I think that might not be in the best interest of the Heroku guys. If they wanted it that way they'd have built it in. Stefan -- AMOOMA GmbH - Bachstr. 126 - 56566 Neuwied -- http://www.amooma.de Geschäftsführer: Stefan Wintermeyer, Handelsregister Montabaur B14998 Asterisk 1.6:http://das-asterisk-buch.de Ruby on Rails 3:http://ruby-auf-schienen.de Videos and slides of AMOOCON:http://amoocon.de -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Generating access_key_id and secret_access_key for S3.yml
A very newbie question about the the access_key_id and secret_access_key for the S3.yml config file - are these keys something I make up on my own or are they keys that I should use some auto-generator of some kind to create them. Sorry if I missed the specifics about generating these keys in the Heroku docs - I didn't see anything when I went through them. Thanks. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
