Automatic Task Execution on Deploy
My CakePHP app has a cache that I would like to have compiled and ready to be served to users every time I push to Heroku. The cache will always be fresh until the next deployment. Is there any way I could have a command be run to prepare this cache every time a web dyno is spun up? Namely: cd ~/www/app/ && ./Console/cake AssetCompress.AssetCompress build_ini Alternatively, are there any other suggestions as to how I could otherwise automate this task to be completed on deploy? -- 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: request.remote_ip
Looking into this now. I'll follow up with an email as well. On Mar 30, 11:23 am, kowsik wrote: > This is a bummer. We are about to switch to hostname-based SSL > onhttp://blitz.ioand it's important that we see the original IP. Can > someone from Heroku confirm/deny this and/or suggest a work around? We > are using sinatra and so far (without the SSL add-on) we can see the > request.ip. > > Thanks, > > K. > ---http://blitz.iohttp://twitter.com/pcapr > > > > > > > > On Wed, Mar 30, 2011 at 7:39 AM, chris wrote: > > Again, if you're using Hostname Based SSL, even on non-https requests, you > > will not get the users IP, no matter which headers you try. So, yeah, you'll > > have go to through a 3rd party, or try not to care about the IPs at all! > > > -- > > 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: heroku rake db:migrate fails with "no such file to load --heroku"???
OK solved. I needed to add heroku to my .gems file. I haven't needed to do this before to make this work. Did I miss the memo? On Feb 2, 11:30 am, Brad wrote: > No, gem list reveals heroku (1.16.2). Other heroku commands work fine > (eg heroku logs, heroku console) so I don't think the problem is at my > end. > > On Feb 2, 10:53 am, Neil Middleton wrote: > > > It looks like you don't have the heroku gem installed locally. Are you > > working in a new gemset or something? > > > Neil > > On Feb 1, 2011 11:37 PM, "Brad" wrote: > > > > I have had my app in development working fine for months now and have > > > never encountered this. I just uploaded a few changes including a new > > > migration (added an index to a table). > > > > When I run heroku rake db:migrate I get the following error; > > > > rake aborted! > > > no such file to load -- heroku > > > /app/a06db1b8-25c0-4fba-a198-9f83669c4791/home/Rakefile:10:in > > > `require' > > > (See full trace by running task with --trace) > > > (in /app/a06db1b8-25c0-4fba-a198-9f83669c4791/home) > > > > What? That's stuff that's waaay out of my control isn't it? > > > > I did a migration this way a few days ago and it worked fine. I can't > > > think of anything I've changed since then. I'm on bamboo-mri-1.9.2. Is > > > this something that's gone wrong with heroku or at my end? > > > > The full trace is as follows; > > > > heroku rake db:migrate --trace > > > rake aborted! > > > no such file to load -- heroku > > > /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/ > > > activesupport-2.3.10/lib/active_support/dependencies.rb:182:in > > > `require' > > > /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/ > > > activesupport-2.3.10/lib/active_support/dependencies.rb:182:in `block > > > in require' > > > /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/ > > > activesupport-2.3.10/lib/active_support/dependencies.rb:547:in > > > `new_constants_in' > > > /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/ > > > activesupport-2.3.10/lib/active_support/dependencies.rb:182:in > > > `require' > > > /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/lib/tasks/cron.rake: > > > 1:in `' > > > /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/ > > > activesupport-2.3.10/lib/active_support/dependencies.rb:171:in `load' > > > /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/ > > > activesupport-2.3.10/lib/active_support/dependencies.rb:171:in `block > > > in load_with_new_constant_marking' > > > /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/ > > > activesupport-2.3.10/lib/active_support/dependencies.rb:547:in > > > `new_constants_in' > > > /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/ > > > activesupport-2.3.10/lib/active_support/dependencies.rb:171:in > > > `load_with_new_constant_marking' > > > /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/rails-2.3.10/ > > > lib/tasks/rails.rb:14:in `block in ' > > > /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/rails-2.3.10/ > > > lib/tasks/rails.rb:14:in `each' > > > /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/rails-2.3.10/ > > > lib/tasks/rails.rb:14:in `' > > > /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/Rakefile:10:in > > > `require' > > > /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/Rakefile:10:in ` > > (required)>' > > > /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2383:in > > > `load' > > > /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2383:in > > > `raw_load_rakefile' > > > /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2017:in > > > `block in load_rakefile' > > > /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2068:in > > > `standard_exception_handling' > > > /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2016:in > > > `load_rakefile' > > > /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2000:in > > > `block in run' > > > /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2068:in > > > `standard_exception_handling' > > > /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7
Re: heroku rake db:migrate fails with "no such file to load --heroku"???
Additional - While exploring this issue I have noticed that I was on bamboo- mri-1.9.1. I have now migrated my app to bamboo-mri-1.9.2 hoping this might resolve the issue but it hasn't. The error I am receiving now is as follows; rake aborted! no such file to load -- heroku :29:in `require' :29:in `require' /app/8c0e4e48-ceff-49bf-b087-34b3d5ab65b5/home/.gems/gems/ activesupport-2.3.10/lib/active_support/dependencies.rb:182:in `block in require' /app/8c0e4e48-ceff-49bf-b087-34b3d5ab65b5/home/.gems/gems/ activesupport-2.3.10/lib/active_support/dependencies.rb:547:in `new_constants_in' /app/8c0e4e48-ceff-49bf-b087-34b3d5ab65b5/home/.gems/gems/ activesupport-2.3.10/lib/active_support/dependencies.rb:182:in `require' /app/8c0e4e48-ceff-49bf-b087-34b3d5ab65b5/home/lib/tasks/cron.rake: 1:in `' /app/8c0e4e48-ceff-49bf-b087-34b3d5ab65b5/home/.gems/gems/ activesupport-2.3.10/lib/active_support/dependencies.rb:171:in `load' /app/8c0e4e48-ceff-49bf-b087-34b3d5ab65b5/home/.gems/gems/ activesupport-2.3.10/lib/active_support/dependencies.rb:171:in `block in load_with_new_constant_marking' /app/8c0e4e48-ceff-49bf-b087-34b3d5ab65b5/home/.gems/gems/ activesupport-2.3.10/lib/active_support/dependencies.rb:547:in `new_constants_in' /app/8c0e4e48-ceff-49bf-b087-34b3d5ab65b5/home/.gems/gems/ activesupport-2.3.10/lib/active_support/dependencies.rb:171:in `load_with_new_constant_marking' /app/8c0e4e48-ceff-49bf-b087-34b3d5ab65b5/home/.gems/gems/rails-2.3.10/ lib/tasks/rails.rb:14:in `block in ' /app/8c0e4e48-ceff-49bf-b087-34b3d5ab65b5/home/.gems/gems/rails-2.3.10/ lib/tasks/rails.rb:14:in `each' /app/8c0e4e48-ceff-49bf-b087-34b3d5ab65b5/home/.gems/gems/rails-2.3.10/ lib/tasks/rails.rb:14:in `' :29:in `require' :29:in `require' /app/8c0e4e48-ceff-49bf-b087-34b3d5ab65b5/home/Rakefile:10:in `' /usr/ruby1.9.2/lib/ruby/1.9.1/rake.rb:2373:in `load' /usr/ruby1.9.2/lib/ruby/1.9.1/rake.rb:2373:in `raw_load_rakefile' /usr/ruby1.9.2/lib/ruby/1.9.1/rake.rb:2007:in `block in load_rakefile' /usr/ruby1.9.2/lib/ruby/1.9.1/rake.rb:2058:in `standard_exception_handling' /usr/ruby1.9.2/lib/ruby/1.9.1/rake.rb:2006:in `load_rakefile' /usr/ruby1.9.2/lib/ruby/1.9.1/rake.rb:1991:in `run' /usr/ruby1.9.2/bin/rake:31:in `' (in /app/8c0e4e48-ceff-49bf-b087-34b3d5ab65b5/home) On Feb 2, 11:30 am, Brad wrote: > No, gem list reveals heroku (1.16.2). Other heroku commands work fine > (eg heroku logs, heroku console) so I don't think the problem is at my > end. > > On Feb 2, 10:53 am, Neil Middleton wrote: > > > It looks like you don't have the heroku gem installed locally. Are you > > working in a new gemset or something? > > > Neil > > On Feb 1, 2011 11:37 PM, "Brad" wrote: > > > > I have had my app in development working fine for months now and have > > > never encountered this. I just uploaded a few changes including a new > > > migration (added an index to a table). > > > > When I run heroku rake db:migrate I get the following error; > > > > rake aborted! > > > no such file to load -- heroku > > > /app/a06db1b8-25c0-4fba-a198-9f83669c4791/home/Rakefile:10:in > > > `require' > > > (See full trace by running task with --trace) > > > (in /app/a06db1b8-25c0-4fba-a198-9f83669c4791/home) > > > > What? That's stuff that's waaay out of my control isn't it? > > > > I did a migration this way a few days ago and it worked fine. I can't > > > think of anything I've changed since then. I'm on bamboo-mri-1.9.2. Is > > > this something that's gone wrong with heroku or at my end? > > > > The full trace is as follows; > > > > heroku rake db:migrate --trace > > > rake aborted! > > > no such file to load -- heroku > > > /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/ > > > activesupport-2.3.10/lib/active_support/dependencies.rb:182:in > > > `require' > > > /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/ > > > activesupport-2.3.10/lib/active_support/dependencies.rb:182:in `block > > > in require' > > > /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/ > > > activesupport-2.3.10/lib/active_support/dependencies.rb:547:in > > > `new_constants_in' > > > /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/ > > > activesupport-2.3.10/lib/active_support/dependencies.rb:182:in > > > `require' > > > /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/lib/tasks/cron.rake: > > > 1:in `' > > > /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/ > > > activesupport-2.3
Re: heroku rake db:migrate fails with "no such file to load --heroku"???
No, gem list reveals heroku (1.16.2). Other heroku commands work fine (eg heroku logs, heroku console) so I don't think the problem is at my end. On Feb 2, 10:53 am, Neil Middleton wrote: > It looks like you don't have the heroku gem installed locally. Are you > working in a new gemset or something? > > Neil > On Feb 1, 2011 11:37 PM, "Brad" wrote: > > > I have had my app in development working fine for months now and have > > never encountered this. I just uploaded a few changes including a new > > migration (added an index to a table). > > > When I run heroku rake db:migrate I get the following error; > > > rake aborted! > > no such file to load -- heroku > > /app/a06db1b8-25c0-4fba-a198-9f83669c4791/home/Rakefile:10:in > > `require' > > (See full trace by running task with --trace) > > (in /app/a06db1b8-25c0-4fba-a198-9f83669c4791/home) > > > What? That's stuff that's waaay out of my control isn't it? > > > I did a migration this way a few days ago and it worked fine. I can't > > think of anything I've changed since then. I'm on bamboo-mri-1.9.2. Is > > this something that's gone wrong with heroku or at my end? > > > The full trace is as follows; > > > heroku rake db:migrate --trace > > rake aborted! > > no such file to load -- heroku > > /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/ > > activesupport-2.3.10/lib/active_support/dependencies.rb:182:in > > `require' > > /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/ > > activesupport-2.3.10/lib/active_support/dependencies.rb:182:in `block > > in require' > > /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/ > > activesupport-2.3.10/lib/active_support/dependencies.rb:547:in > > `new_constants_in' > > /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/ > > activesupport-2.3.10/lib/active_support/dependencies.rb:182:in > > `require' > > /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/lib/tasks/cron.rake: > > 1:in `' > > /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/ > > activesupport-2.3.10/lib/active_support/dependencies.rb:171:in `load' > > /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/ > > activesupport-2.3.10/lib/active_support/dependencies.rb:171:in `block > > in load_with_new_constant_marking' > > /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/ > > activesupport-2.3.10/lib/active_support/dependencies.rb:547:in > > `new_constants_in' > > /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/ > > activesupport-2.3.10/lib/active_support/dependencies.rb:171:in > > `load_with_new_constant_marking' > > /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/rails-2.3.10/ > > lib/tasks/rails.rb:14:in `block in ' > > /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/rails-2.3.10/ > > lib/tasks/rails.rb:14:in `each' > > /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/rails-2.3.10/ > > lib/tasks/rails.rb:14:in `' > > /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/Rakefile:10:in > > `require' > > /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/Rakefile:10:in ` > (required)>' > > /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2383:in > > `load' > > /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2383:in > > `raw_load_rakefile' > > /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2017:in > > `block in load_rakefile' > > /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2068:in > > `standard_exception_handling' > > /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2016:in > > `load_rakefile' > > /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2000:in > > `block in run' > > /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2068:in > > `standard_exception_handling' > > /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:1998:in > > `run' > > /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/bin/rake:31:in > > `' > > /usr/ruby1.9.1/bin/rake:19:in `load' > > /usr/ruby1.9.1/bin/rake:19:in `' > > (in /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home) > > > -- > > 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.
heroku rake db:migrate fails with "no such file to load --heroku"???
I have had my app in development working fine for months now and have never encountered this. I just uploaded a few changes including a new migration (added an index to a table). When I run heroku rake db:migrate I get the following error; rake aborted! no such file to load -- heroku /app/a06db1b8-25c0-4fba-a198-9f83669c4791/home/Rakefile:10:in `require' (See full trace by running task with --trace) (in /app/a06db1b8-25c0-4fba-a198-9f83669c4791/home) What? That's stuff that's waaay out of my control isn't it? I did a migration this way a few days ago and it worked fine. I can't think of anything I've changed since then. I'm on bamboo-mri-1.9.2. Is this something that's gone wrong with heroku or at my end? The full trace is as follows; heroku rake db:migrate --trace rake aborted! no such file to load -- heroku /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/ activesupport-2.3.10/lib/active_support/dependencies.rb:182:in `require' /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/ activesupport-2.3.10/lib/active_support/dependencies.rb:182:in `block in require' /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/ activesupport-2.3.10/lib/active_support/dependencies.rb:547:in `new_constants_in' /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/ activesupport-2.3.10/lib/active_support/dependencies.rb:182:in `require' /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/lib/tasks/cron.rake: 1:in `' /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/ activesupport-2.3.10/lib/active_support/dependencies.rb:171:in `load' /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/ activesupport-2.3.10/lib/active_support/dependencies.rb:171:in `block in load_with_new_constant_marking' /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/ activesupport-2.3.10/lib/active_support/dependencies.rb:547:in `new_constants_in' /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/ activesupport-2.3.10/lib/active_support/dependencies.rb:171:in `load_with_new_constant_marking' /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/rails-2.3.10/ lib/tasks/rails.rb:14:in `block in ' /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/rails-2.3.10/ lib/tasks/rails.rb:14:in `each' /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/.gems/gems/rails-2.3.10/ lib/tasks/rails.rb:14:in `' /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/Rakefile:10:in `require' /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home/Rakefile:10:in `' /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2383:in `load' /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2383:in `raw_load_rakefile' /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2017:in `block in load_rakefile' /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2016:in `load_rakefile' /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2000:in `block in run' /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:1998:in `run' /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/bin/rake:31:in `' /usr/ruby1.9.1/bin/rake:19:in `load' /usr/ruby1.9.1/bin/rake:19:in `' (in /app/f47a1fc7-411c-43ab-819d-04123dfa1b96/home) -- 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: db:pull throws exception from taps
I'm not entirely sure but is your problem related to this issue - http://github.com/ricardochimal/taps/issues#issue/25 Using ruby 1.8.7 with taps produced better results for me that 1.9.1. Perhaps try that. On Jun 26, 2:40 am, lsiden wrote: > I am having the same problem discussed in this > thread:http://groups.google.com/group/heroku/browse_thread/thread/20e036163a..., > but the solution of uninstalling and re-installing sqlite3-ruby did > not help. Taps throws an exception here: > > Error encountered loading data, wrote the data chunk to dump. > 20810.dat | ETA: --:--:-- > /home/lsiden/.rvm/gems/ruby-1.9.1-p378/gems/taps-0.3.9/lib/taps/ > data_stream.rb:187:in `load': class DateTime needs to have method > `_load' (TypeError) > from /home/lsiden/.rvm/gems/ruby-1.9.1-p378/gems/taps-0.3.9/lib/taps/ > data_stream.rb:187:in `parse_encoded_data' > from /home/lsiden/.rvm/gems/ruby-1.9.1-p378/gems/taps-0.3.9/lib/taps/ > data_stream.rb:130:in `fetch_remote' > from /home/lsiden/.rvm/gems/ruby-1.9.1-p378/gems/taps-0.3.9/lib/taps/ > operation.rb:286:in `block in pull_data_from_table' > from /home/lsiden/.rvm/gems/ruby-1.9.1-p378/gems/taps-0.3.9/lib/taps/ > operation.rb:279:in `loop' > from /home/lsiden/.rvm/gems/ruby-1.9.1-p378/gems/taps-0.3.9/lib/taps/ > operation.rb:279:in `pull_data_from_table' > > Is this something I should post to the taps forum or #irc? -- 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.
How do deal with dd/mm/yyyy date formats in forms in heroku
My app has a form with several dates and datetimes in it in the format dd/mm/ or dd/mm/ HH:MM. These worked fine in my local development environment (using postgresql) but it causes 500 errors once posted to heroku. I've come across a few suggestions for how to deal with this on the web such as using a before filter in the controller to reformat the date before passing it to the database but all of the solutions I've read seem clumsy. Is there a recommended way of dealing with this issue? Also, why does this work on my local system but not on heroku? -- 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.
Location of Amazon servers used by Heroku
Just wondering if heroku uses a particular set of amazon servers, e.g East Coast, West Coast, Europe etc. Are there any plans to make this user selectable? This may matter to me as latency may be an issue for my app (still need to do more deployment/testing to see how much of an issue). I'd particularly be interested in the Singapore/Asia servers at this point in time. -- 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: Database importing very slow
Thanks for replying. Yes, taps is the latest version. Initially it wouldn't work because of a known issue with Ruby 1.9.1 but it works fine when I used 1.8.7. The taps version number is 0.3.9. The database has 11 tables all of which were generated according to Rails defaults and as such all have an integer primary key. I also confirmed this through directly querying the database in postgres. My database eventually uploaded overnight taking 8 hours (~0.5 kbps!). After uploading my app didn't work so I suspect it didn't upload properly (although I can't prove this). Perhaps I'll try Heroku support directly. On Jun 25, 4:34 am, Oren Teich wrote: > Are you running the latest version of taps (sudo gem update taps)? Is the > primary key on your table an integer? > > http://blog.heroku.com/archives/2010/4/21/supporting_big_data_part_1/ > > > > On Thu, Jun 24, 2010 at 4:25 AM, Brad wrote: > > Oops, I didn't say how slow. So far it's been 2 hours. It looks like > > it'll be at least another hour. > > > On Jun 24, 9:23 pm, Brad wrote: > > > I'm trying to upload my development database to my heroku app (via > > > heroku db:push) but finding it very slow. My database is not huge - 11 > > > tables, about 57000 records, 13MB diskspace but is taking hours to > > > upload. I don't even know where to start with investigating this. The > > > connection at my end is fine for any other activities. Surely heroku > > > can't be this slow. > > > -- > > 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. -- 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: Database importing very slow
Oops, I didn't say how slow. So far it's been 2 hours. It looks like it'll be at least another hour. On Jun 24, 9:23 pm, Brad wrote: > I'm trying to upload my development database to my heroku app (via > heroku db:push) but finding it very slow. My database is not huge - 11 > tables, about 57000 records, 13MB diskspace but is taking hours to > upload. I don't even know where to start with investigating this. The > connection at my end is fine for any other activities. Surely heroku > can't be this slow. -- 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.
Database importing very slow
I'm trying to upload my development database to my heroku app (via heroku db:push) but finding it very slow. My database is not huge - 11 tables, about 57000 records, 13MB diskspace but is taking hours to upload. I don't even know where to start with investigating this. The connection at my end is fine for any other activities. Surely heroku can't be this slow. -- 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: Deploying an app with prawn included as a submodule
OK, I solved the issue. There was a syntax error in a file that wasn't causing problems on my setup but causing a crash on heroku. After fixing that it works fine now. On Jun 15, 6:21 pm, Brad wrote: > Thanks Chris, > > I guess I'll have to look at things a little closer and work out where > things are going wrong. > > On Jun 14, 11:13 pm, Chris Schumann wrote: > > > > > On Jun 14, 2:41 am, Brad wrote: > > > > I have installedprawnas a submodule rather than as a gem in > > > accordance with the developers' suggestions at > > >http://wiki.github.com/sandal/prawn/using-prawn-in-rails. This was > > > before I knew about the inability of heroku to use submodules (http:// > > > docs.heroku.com/constraints#git-submodules). > > > I used the commands in that document to un-submodulizePrawnin my > > app. It worked perfectly for me. > > > Chris -- 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: Deploying an app with prawn included as a submodule
Thanks Chris, I guess I'll have to look at things a little closer and work out where things are going wrong. On Jun 14, 11:13 pm, Chris Schumann wrote: > On Jun 14, 2:41 am, Brad wrote: > > > I have installed prawn as a submodule rather than as a gem in > > accordance with the developers' suggestions at > >http://wiki.github.com/sandal/prawn/using-prawn-in-rails. This was > > before I knew about the inability of heroku to use submodules (http:// > > docs.heroku.com/constraints#git-submodules). > > I used the commands in that document to un-submodulize Prawn in my > app. It worked perfectly for me. > > Chris -- 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.
Deploying an app with prawn included as a submodule
Hi, I'm very new to Heroku and am trying to deploy an app I have in early development. This app uses prawn to generate pdf output and this works fine on my local setup. I have installed prawn as a submodule rather than as a gem in accordance with the developers' suggestions at http://wiki.github.com/sandal/prawn/using-prawn-in-rails. This was before I knew about the inability of heroku to use submodules (http:// docs.heroku.com/constraints#git-submodules). Anyway, I followed the instructions to track the submodule in the main project, but when I try uploading the app I get an error (on display at http://fierce-waterfall-51.heroku.com/) which suggests to me that prawn is not being found (the .to_pdf method being called in my controller is defined in a class that is a subclass of Prawn::Document in the same manner as described on the prawn/rails page above). Does anyone have a solution to this problem or should I give up on this approach? As the prawn gem is not being kept up to date until the 1.0 release (next month?) I'm reluctant to switch to a gem based approach until then but may do so if I have no other choice. -- 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: Git - Internal server error - fatal: The remote end hung up unexpectedly
I'm having the same problem now too! Brad On Sep 19, 12:41 am, James PocketSmith <[EMAIL PROTECTED]> wrote: > Hi Adam, > > Looks like it has happened again; same app (pocketsmithdev). > > Difference now is that it is hanging for a good 3-4 minutes on a pull > before it gives it the: > > "Internalservererrorfatal: Theremoteendhungupunexpectedly" > > Thanks for any help you can provide. > > James > > On Aug 28, 5:22 am, "Adam Wiggins" <[EMAIL PROTECTED]> wrote: > > > pocketdevsmith should begit-capable again. > > > Adam --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
