Re: Cedar stack and fastimage gem, push rejected
Just a guess, but could it be that some of the gems listed in your Gemfile aren't available anymore, maybe they've been removed from their repositories or something? On Thu, Jul 28, 2011 at 10:05 PM, kimptoc ch...@kimptoc.net wrote: Hi, I have a simple Rails 3 app running on the Aspen and Bamboo stacks ok, but when I try the Cedar stack the push is being rejected: $ heroku create sss --stack cedar Creating sss... done, stack is cedar http://sss.herokuapp.com/ | g...@heroku.com:sss.git Git remote heroku added $ git push heroku master Counting objects: 380, done. Delta compression using up to 2 threads. Compressing objects: 100% (360/360), done. Writing objects: 100% (380/380), 5.61 MiB | 112 KiB/s, done. Total 380 (delta 178), reused 0 (delta 0) - Heroku receiving push - Removing .DS_Store files - Ruby/Rails app detected - Installing dependencies using Bundler version 1.1.pre.5 Running: bundle install --without development:test --path vendor/bundle --deployment Fetching dependency information from the API at http://rubygems.org/ Could not find fastimage-1.2.8 in any of the sources ! ! Failed to install gems via Bundler. ! ! Heroku push rejected, failed to compile Ruby/rails app To g...@heroku.com:sss.git ! [remote rejected] master - master (pre-receive hook declined) error: failed to push some refs to 'g...@heroku.com:sss.git' Is there a problem with some gems on Cedar or do I need to bundle things differently for Cedar? Thanks, Chris -- 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: European clients hosted on Heroku?
Thanks for the information, Michel. I certainly didn't know about this or even worried it could be a problem. On Wed, Jul 6, 2011 at 12:10 PM, Michel Pigassou dag...@gmail.com wrote: Just to be clear it concerns all European countries that host personal data on Heroku (people identity, emails, etc.). -- You received this message because you are subscribed to the Google Groups Heroku group. To view this discussion on the web visit https://groups.google.com/d/msg/heroku/-/OM1Csbf7W7cJ. 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: Latency of writing in the DB
How long it takes depends on the number of records in your table but yes, this kind of search can be pretty expensive. You could try adding an index to your DB or denormalizing something but this kind of problem usually takes some engineering to solve. On Fri, Jun 24, 2011 at 12:49 PM, Michel Pigassou dag...@gmail.com wrote: Hi all. My problem is simple : when I put a new entry in my DB, I ensure that there is no entries the same day. When a request is sent twice, is it possible that to be written in the DB and readebale (accessible from a select query) the process takes more than one minute on Heroku? -- You received this message because you are subscribed to the Google Groups Heroku group. To view this discussion on the web visit https://groups.google.com/d/msg/heroku/-/1UqnOZY6VBwJ. 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: Rake aborted!
Could you have accidentally deleted your rakefile or something like that? On Sat, May 21, 2011 at 2:38 PM, Jeff Schmitz jeffrey.j.schm...@gmail.comwrote: Did your task depend on environment? Jeff On May 21, 2011, at 2:30 AM, Nikue nik...@gmail.com wrote: Hey guys, heroku rake getting aborted with this trace: $ heroku rake db:migrate --trace rake aborted! undefined method `task' for #Freelance::Application:0x7fca8218f160 /app/.bundle/gems/ruby/1.8/gems/railties-3.0.7/lib/rails/ application.rb:215:in ` initialize_tasks' /app/.bundle/gems/ruby/1.8/gems/railties-3.0.7/lib/rails/ application.rb:139:in ` load_tasks' /app/.bundle/gems/ruby/1.8/gems/railties-3.0.7/lib/rails/ application.rb:77:in `s end' /app/.bundle/gems/ruby/1.8/gems/railties-3.0.7/lib/rails/ application.rb:77:in `m ethod_missing' /app/Rakefile:7 /app/.bundle/gems/ruby/1.8/gems/rake-0.9.0/lib/rake/rake_module.rb: 25:in `load' /app/.bundle/gems/ruby/1.8/gems/rake-0.9.0/lib/rake/rake_module.rb: 25:in `load_r akefile' /app/.bundle/gems/ruby/1.8/gems/rake-0.9.0/lib/rake/application.rb: 495:in `raw_l oad_rakefile' /app/.bundle/gems/ruby/1.8/gems/rake-0.9.0/lib/rake/application.rb: 78:in `load_r akefile' /app/.bundle/gems/ruby/1.8/gems/rake-0.9.0/lib/rake/application.rb: 129:in `stand ard_exception_handling' /app/.bundle/gems/ruby/1.8/gems/rake-0.9.0/lib/rake/application.rb: 77:in `load_r akefile' /app/.bundle/gems/ruby/1.8/gems/rake-0.9.0/lib/rake/application.rb: 61:in `run' /app/.bundle/gems/ruby/1.8/gems/rake-0.9.0/lib/rake/application.rb: 129:in `stand ard_exception_handling' any ideas? -- 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: Daemonized workers on heroku and tweetstream via heroku rake jobs:work
From the error message you get, it looks like you have a Gemfile that you
should lock with bundle lock before you deploy your application.
On Sun, Apr 10, 2011 at 9:23 AM, Daryl daryl.mann...@gmail.com wrote:
I keep getting the following error when running a rake task that is
supposed to start a worker daemon on heroku.
= Located unlocked Gemfile for production
ERROR: no command given
Usage: tweetstream command options -- application options
However, I've created a rake task in lib/tasks (I'm using padrino)
which defines jobs:work (which I trigger with heroku rake jobs:work as
exec {ruby 'lib/tasks/tweetstreamer.rb' start}
The tweetstreamer.rb file adds a class to connect to the MongoHQ
database, but other than that is straight up out of the docs in terms
of daemonizing tweetstream
ie.
TweetStream::Daemon.new(ENV['TWITTER_USERNAME'],
ENV['TWITTER_PASSWORD']).track('term1', 'term2', 'term3') do |status|
status.do stuff
end
So, a bit stumped here and can't seem to fund much doc love on heroku
on the use of background processes if it's not delayed job or on
github for background worker processes using heroku. It's possible I'm
just not googling smart, but seems like it's a bit of a hole here (and
am putting my hand up for the blog post that'll help everyone who
might be working on this).
Can anyone point to a similar code example or provide some help here
to guide me?
thanks !
Daryl.
--
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: My (flawed?) attempt to add or subtract workers via Heroku API.
Kudos to you if you were really able to do what you were trying to do. It
looks like something really useful and complicated and I didn't think it
would be possible at all in production since there's only so much you can
fine tune about workers in Heroku.
Congrats!
On Wed, Jan 19, 2011 at 10:37 PM, rubynoob mysmilecent...@gmail.com wrote:
Solving my own problem...will soon report my solution for all to see,
FWIW.
On Jan 19, 7:32 am, rubynoob mysmilecent...@gmail.com wrote:
Sorry, I forgot to provide some important details. Someday I won't be
so noobish about all this stuff. :)
I'm using Ruby 1.8.6 on Windows XP, Rails 2.3.2, heroku gem 1.15.1,
and delayed_job gem 2.0.5.
I would have tried ddollar's heroku-autoscale, but it's not ready for
production apps, and from what I've read, doesn't scale workers, only
dynos. I tried lostboy's workless gem, but couldn't get it working
(sorry, it's been several days, and I can't remember why it didn't
work--I may try again).
Thanks.
Jim Costello
On Jan 18, 12:36 pm, rubynoob mysmilecent...@gmail.com wrote:
I'm trying a different approach to autoscaling workers in my heroku
app.
I'm using a custom config variable in my heroku config I've labeled
'WORKER_COUNT', which represents how many workers are running
currently. I've also added HEROKU_USERNAME, HEROKU_PASSWORD, and
HEROKU_APP to my heroku config.
I added require 'heroku' at the beginning of my application
controller, and a method to add a worker and increment 'WORKER_COUNT'
by one...:
def add_heroku_worker
heroku = Heroku::Client.new(ENV['HEROKU_USERNAME'],
ENV['HEROKU_PASSWORD'])
myapp = heroku(ENV['HEROKU_APP'])
worker_count = heroku(ENV['WORKER_COUNT'])
qty = worker_count + 1
heroku.add_config_vars(myapp, {WORKER_COUNT = qty})
heroku.set_workers(ENV['HEROKU_APP'], qty)
end
...and another method (called 'subtract_heroku_worker') to subtract a
worker and deprecate 'WORKER_COUNT' by one.
I call add_heroku_worker right after delaying a job...:
@job.delay.import(path)
add_heroku_worker
...and subtract_heroku_worker right after the job sucessfully
completes.
Problem is, nothing seems to be happening. I get no errors, but no
workers, either. I suspect either my syntax is wrong, or I'm just
going about this the wrong way.
Can anybody help shed some light on this?
--
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.comheroku%2bunsubscr...@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: Cron, delayed jobs and workers scaling
I think you got it all wrong. Cron and Delayed Job are two completely different and unrelated things; they don't have to work together. Maybe you should take a look at the examples in the wiki as they're pretty accurate both at showing you how to use and configure each and at helping you chose which one is more appropriate in your case. On Wed, Jan 5, 2011 at 5:34 PM, chris mcclellan...@gmail.com wrote: Cron and delayed_job are entirely separate things. You use cron if you want to run things daily (or hourly). Say you want to send a daily report to all your users, you would use the code your posted above. You use delayed_job if you want to run something in the background (email sending, heavy processing, etc) after something happens. Say, someone buys something from your site and you want to send them a receipt. You would do this via delayed_job, doing something like UserMailer.send_later(:notification_mail, user) Hope that helps! -- 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.comheroku%2bunsubscr...@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: HTML5 manifest caching on Heroku
I can't test the example right now, but I would like to remind you that appcache or manifest cache is still in at a experimental stage. If you think it works inconsistently with Safari, better not even try with Firefox (yet). It all depends on the version though. On Tue, Nov 30, 2010 at 6:35 PM, Rufo Sanchez r...@rufosanchez.com wrote: I have HTML5 offline-capable apps running off Heroku and have had no issues so far; we've had them used across a fairly wide range of devices, too. FWIW, I didn't have any problems with the links below in either desktop or mobile Safari; loading the page once, turning on airplane mode, closing the tab and visiting the same URL worked fine. (iPhone 4 on iOS 4.1.) Rufo On Tue, Nov 30, 2010 at 1:13 AM, railsnerd rails.n...@gmail.com wrote: Adam Wiggins kindly put up a cache manifest example: http://cachemanifest.heroku.com/clock.html I notice that this does work when I reload the page that is already open in iPhone Safari However if I load the clock url on a fresh safari page, the cache does not kick in. Is this a heroku issue? The manifests seem to be set up ok from what I can see? The reason I am wondering is that other manifest examples, outside of heroku, do work eg: http://www.thecssninja.com/demo/offline_webapp/ -- 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.comheroku%2bunsubscr...@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.comheroku%2bunsubscr...@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: Ubuntu 10.10 (amd64) + rails 3.0.1 + heroku uninitialized constant error
I think the following line: /usr/local/lib/ruby/gems/1.9.1/gems/heroku-1.13.1/lib/heroku/commands/pg.rb:8:in `class:Pg': uninitialized constant Heroku::Command::Pg::Help (NameError) gives away that the culprit could be the PostGres gem. Makes sense too since it's one of the things Heroku uses but you don't usually need it in your development environment. You should probably check to see if it's correctly listed in your Gemfile. Hope that helps. On Tue, Nov 16, 2010 at 3:07 PM, Mateus mcavanh...@gmail.com wrote: Hi guys Few months ago I start to study Ruby on Rails. At the time, I was using the version 2.x of Rails (Don't remember which exactly) and it was working fine. (running on Ubuntu 9.04) I get some troubles and personal problems and I stop with rails. Now, I update my ubuntu to 10.10 and install the Rails 3 (rails 3.0.1, ruby 1.9.2p0). But, when I just start to use and I was to deploy my app to heroku, I get the following error: /usr/local/lib/ruby/gems/1.9.1/gems/heroku-1.13.1/lib/heroku/commands/pg.rb:8:in `class:Pg': uninitialized constant Heroku::Command::Pg::Help (NameError) from /usr/local/lib/ruby/gems/1.9.1/gems/heroku-1.13.1/lib/heroku/commands/pg.rb:5:in `module:Command' from /usr/local/lib/ruby/gems/1.9.1/gems/heroku-1.13.1/lib/heroku/commands/pg.rb:4:in `top (required)' from internal:lib/rubygems/custom_require:29:in `require' from internal:lib/rubygems/custom_require:29:in `require' from /usr/local/lib/ruby/gems/1.9.1/gems/heroku-1.13.1/lib/heroku/command.rb:5:in `block in top (required)' from /usr/local/lib/ruby/gems/1.9.1/gems/heroku-1.13.1/lib/heroku/command.rb:5:in `each' from /usr/local/lib/ruby/gems/1.9.1/gems/heroku-1.13.1/lib/heroku/command.rb:5:in `top (required)' from internal:lib/rubygems/custom_require:29:in `require' from internal:lib/rubygems/custom_require:29:in `require' from /usr/local/lib/ruby/gems/1.9.1/gems/heroku-1.13.1/bin/heroku:7:in `top (required)' from /usr/local/bin/heroku:19:in `load' from /usr/local/bin/heroku:19:in `main' This happen with every single heroku command I try. I try google for it, and even check something with gem environment, which give the following: RubyGems Environment: - RUBYGEMS VERSION: 1.3.7 - RUBY VERSION: 1.9.2 (2010-08-18 patchlevel 0) [x86_64-linux] - INSTALLATION DIRECTORY: /usr/local/lib/ruby/gems/1.9.1 - RUBY EXECUTABLE: /usr/local/bin/ruby - EXECUTABLE DIRECTORY: /usr/local/bin - RUBYGEMS PLATFORMS: - ruby - x86_64-linux - GEM PATHS: - /usr/local/lib/ruby/gems/1.9.1 - /home/cavanholi/.gem/ruby/1.9.1 - GEM CONFIGURATION: - :update_sources = true - :verbose = true - :benchmark = false - :backtrace = false - :bulk_threshold = 1000 - REMOTE SOURCES: - http://rubygems.org/ As I look for some answer to my problem, this was all I could get. And, for me, it seen fine. (I'm kind of noob with linux, so sometimes I don't get the problem) When I installed the gem, its been everything fine, no errors at all. I wonder what can I do to solve this problem, since I cannot add the SSH Key. Even the command heroku help don't work. thx for the time and help, and sorry if I'm asking in the wrong place -- Mateus Cavanholi -- 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.comheroku%2bunsubscr...@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: Could not find a valid gem 'source'
I don't know it this will help, but my Gemfile looks quite different. First, the sources line is like this: source 'http://gemcutter.org' probably both notations are valid though. The problematic part is probably your Authlogic line. Mine looks like this: gem 'authlogic', :git = 'http://github.com/binarylogic/authlogic.git', '2.1.3' As you can see, I include a complete url to a concrete git file instead of just referencing the repository like you do. I hope that helps. On Thu, Oct 28, 2010 at 6:55 AM, jhubert jhub...@gmail.com wrote: For some reason I can't deploy my Rails 3 app. My Gemfile looks like this: source :rubygems gem 'rails', '3.0.1' gem 'sqlite3-ruby', :require = 'sqlite3' gem 'authlogic', :git = 'git://github.com/odorcicd/ authlogic.git', :branch = 'rails3' gem 'acts_as_commentable' gem 'activemerchant' gem 'jquery-rails' and the error message looks like this: - Heroku receiving push - Rails app detected - Installing gem source from http://rubygems.org ERROR: Could not find a valid gem 'source' ( 0) in any repository ! Heroku push rejected, failed to install gem Any ideas what might cause this? I am running on the bamboo-ree stack using Rails 3.0.1 -- 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.comheroku%2bunsubscr...@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: warning: already initialized constant OrderedHash
OrderedHash is part of ActiveSupport and it looks like it's being initialized twice. I hope that rings some bell. On Tue, Oct 26, 2010 at 2:59 PM, DAZ daz4...@gmail.com wrote: I keep getting this warning when I push a new Sinatra/DataMapper app to Heroku. /home/slugs/286257_c19666c_5401-ed999fc7-450c-4af4-a27f-d25cb1203dd9/ mnt/.gems/gems/dm-validations-1.0.2/lib/dm-validations.rb:33: warning: already initialized constant OrderedHash I don't get this warning on my local machine. Does anybody know what it means and how to fix it? cheers, DAZ -- 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.comheroku%2bunsubscr...@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: heroku_user
It looks like Heroku Users are used to authenticate users who already have an account with Heroku and are allowed to check out the application's source (that's the impression I get from skimming through the article). If you're looking for a commonly used, standard authentication method, Authlogic and Devise seem to be the most commonly used gems for the task. You can find tutorials on them both at railscasts.com On Thu, Oct 21, 2010 at 10:28 AM, jundai bates.kobashig...@gmail.comwrote: Hello, In looking for a dead-simple auth option for my heroku app, I noticed this page: http://blog.heroku.com/archives/2008/1/14/heroku_user/ I tried accessing heroku, and I wasn't able to get it working. I get a: NameError (undefined local variable or method `heroku_user' for #FilmViewingsController:0x2b17f842faa0): app/controllers/application_controller.rb:6:in `authorized?' app/controllers/film_viewings_controller.rb:39:in `edit' Is heroku_user something that's still available within heroku apps? Is there anything I have to do to enable it? Is it called something else now? I can't seem to find any indication that it's been removed as a feature, though I imagine heroku's platform has seen a lot of change since 2008. -Jdbk -- 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.comheroku%2bunsubscr...@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: Add SSH Key to Heroku (using Windows/Cygwin)
I don't think many are using Windows with Rails here. Maybe you should try dual booting with Linux. The new Ubuntu came out just this weekend and you won't regret the switch ;) On Tue, Oct 12, 2010 at 4:19 PM, Twiek sebastian.schwiec...@googlemail.comwrote: I followed their guide but it unfortunaltely didn't work for me. I have a SSH-Key and it seems to work (I used it for opening a github- Account). The problems start when I enter the following: $ heroku or $ heroku keys:add This results in the error message seen above. My guess is that it's some problem specific to cygwin/windows but I'm not sure. Twiek On Oct 11, 11:24 pm, Abel Tamayo abel.tam...@gmail.com wrote: I would recommend that you follow Heroku's guide here: http://docs.heroku.com/keys http://docs.heroku.com/keysMaybe you don't have installed ssh. Let us know how that goes and I hope that helps. Abel. On Mon, Oct 11, 2010 at 6:36 PM, Twiek sebastian.schwiec...@googlemail.comwrote: Beeing new to programming I'm trying to learn RoR using railstutorial.org and ran into a problem in chapter 1.4.1 (http:// railstutorial.org/book#sec:1.4.1). When trying to add my SSH key to Heroku the following happend: ba...@basti-pc ~ $ heroku keys:add internal:lib/rubygems/custom_require:29:in `require': no such file to load -- readline (LoadError) from internal:lib/rubygems/custom_require:29:in `require' from /usr/local/lib/ruby/gems/1.9.1/gems/heroku-1.10.14/lib/ heroku/comma nds/app.rb:1:in `top (required)' from internal:lib/rubygems/custom_require:29:in `require' from internal:lib/rubygems/custom_require:29:in `require' from /usr/local/lib/ruby/gems/1.9.1/gems/heroku-1.10.14/lib/ heroku/comma nd.rb:5:in `block in top (required)' from /usr/local/lib/ruby/gems/1.9.1/gems/heroku-1.10.14/lib/ heroku/comma nd.rb:5:in `each' from /usr/local/lib/ruby/gems/1.9.1/gems/heroku-1.10.14/lib/ heroku/comma nd.rb:5:in `top (required)' from internal:lib/rubygems/custom_require:29:in `require' from internal:lib/rubygems/custom_require:29:in `require' from /usr/local/lib/ruby/gems/1.9.1/gems/heroku-1.10.14/bin/ heroku:7:in `top (required)' from /usr/local/bin/heroku:19:in `load' from /usr/local/bin/heroku:19:in `main' I'm running Windows Vista using Cygwin. I have installed ruby-1.9.2-p0 and Rails 3.0.0. I tried to find a answer elsewhere using google but wasn't able, Nevertheles any link helping out would be appreciated as well. Thanks in advance, Twiek -- 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.comheroku%2bunsubscr...@googlegroups.com heroku%2bunsubscr...@googlegroups.comheroku%252bunsubscr...@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.comheroku%2bunsubscr...@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: Add SSH Key to Heroku (using Windows/Cygwin)
I would recommend that you follow Heroku's guide here: http://docs.heroku.com/keys http://docs.heroku.com/keysMaybe you don't have installed ssh. Let us know how that goes and I hope that helps. Abel. On Mon, Oct 11, 2010 at 6:36 PM, Twiek sebastian.schwiec...@googlemail.comwrote: Beeing new to programming I'm trying to learn RoR using railstutorial.org and ran into a problem in chapter 1.4.1 (http:// railstutorial.org/book#sec:1.4.1). When trying to add my SSH key to Heroku the following happend: ba...@basti-pc ~ $ heroku keys:add internal:lib/rubygems/custom_require:29:in `require': no such file to load -- readline (LoadError) from internal:lib/rubygems/custom_require:29:in `require' from /usr/local/lib/ruby/gems/1.9.1/gems/heroku-1.10.14/lib/ heroku/comma nds/app.rb:1:in `top (required)' from internal:lib/rubygems/custom_require:29:in `require' from internal:lib/rubygems/custom_require:29:in `require' from /usr/local/lib/ruby/gems/1.9.1/gems/heroku-1.10.14/lib/ heroku/comma nd.rb:5:in `block in top (required)' from /usr/local/lib/ruby/gems/1.9.1/gems/heroku-1.10.14/lib/ heroku/comma nd.rb:5:in `each' from /usr/local/lib/ruby/gems/1.9.1/gems/heroku-1.10.14/lib/ heroku/comma nd.rb:5:in `top (required)' from internal:lib/rubygems/custom_require:29:in `require' from internal:lib/rubygems/custom_require:29:in `require' from /usr/local/lib/ruby/gems/1.9.1/gems/heroku-1.10.14/bin/ heroku:7:in `top (required)' from /usr/local/bin/heroku:19:in `load' from /usr/local/bin/heroku:19:in `main' I'm running Windows Vista using Cygwin. I have installed ruby-1.9.2-p0 and Rails 3.0.0. I tried to find a answer elsewhere using google but wasn't able, Nevertheles any link helping out would be appreciated as well. Thanks in advance, Twiek -- 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.comheroku%2bunsubscr...@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: no such file to load -- rspec
FIrst, /usr and bundler 1.0.2 refer to the version running on the server, not your local versions which makes sense. And second, it looks like RSpec is listed as a dependency for something somewhere. Maybe you should include it in your Gem file. I hope that helps. On Thu, Oct 7, 2010 at 11:01 PM, rr r...@bubblepath.com wrote: Hi, Getting the below error error when I run heroku rake db:migrate --app my_app_name rake aborted! no such file to load -- rspec Trace: /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.0/lib/bundler/ runtime.rb:64:in `require' /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.0/lib/bundler/ runtime.rb:64:in `require' /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.0/lib/bundler/ runtime.rb:62:in `each' /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.0/lib/bundler/ runtime.rb:62:in `require' /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.0/lib/bundler/ runtime.rb:51:in `each' /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.0/lib/bundler/ runtime.rb:51:in `require' /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.0/lib/bundler.rb: 112:in `require' /disk1/home/slugs/311951_4bf369d_2ba5/mnt/config/boot.rb:116:in `load_gems' /disk1/home/slugs/311951_4bf369d_2ba5/mnt/.bundle/gems/ruby/1.8/gems/ rails-2.3.8/lib/initializer.rb:164:in `process' /disk1/home/slugs/311951_4bf369d_2ba5/mnt/.bundle/gems/ruby/1.8/gems/ rails-2.3.8/lib/initializer.rb:113:in `send' /disk1/home/slugs/311951_4bf369d_2ba5/mnt/.bundle/gems/ruby/1.8/gems/ rails-2.3.8/lib/initializer.rb:113:in `run' /disk1/home/slugs/311951_4bf369d_2ba5/mnt/config/environment.rb:9 /disk1/home/slugs/311951_4bf369d_2ba5/mnt/.bundle/gems/ruby/1.8/gems/ activesuppo rt-2.3.8/lib/active_support/dependencies.rb:156:in `require' /disk1/home/slugs/311951_4bf369d_2ba5/mnt/.bundle/gems/ruby/1.8/gems/ activesuppo rt-2.3.8/lib/active_support/dependencies.rb:156:in `require' /disk1/home/slugs/311951_4bf369d_2ba5/mnt/.bundle/gems/ruby/1.8/gems/ activesuppo rt-2.3.8/lib/active_support/dependencies.rb:521:in `new_constants_in' /disk1/home/slugs/311951_4bf369d_2ba5/mnt/.bundle/gems/ruby/1.8/gems/ activesuppo rt-2.3.8/lib/active_support/dependencies.rb:156:in `require' /disk1/home/slugs/311951_4bf369d_2ba5/mnt/.bundle/gems/ruby/1.8/gems/ rails-2.3.8/lib/tasks/misc.rake:4 /home/slugs/311951_4bf369d_2ba5/mnt/.bundle/gems/ruby/1.8/gems/ rake-0.8.7/lib/rake.rb:636:in `call' /home/slugs/311951_4bf369d_2ba5/mnt/.bundle/gems/ruby/1.8/gems/ rake-0.8.7/lib/rake.rb:636:in `execute' /home/slugs/311951_4bf369d_2ba5/mnt/.bundle/gems/ruby/1.8/gems/ rake-0.8.7/lib/rake.rb:631:in `each' /home/slugs/311951_4bf369d_2ba5/mnt/.bundle/gems/ruby/1.8/gems/ rake-0.8.7/lib/rake.rb:631:in `execute' /home/slugs/311951_4bf369d_2ba5/mnt/.bundle/gems/ruby/1.8/gems/ rake-0.8.7/lib/rake.rb:597:in `invoke_with_call_chain' /usr/ruby1.8.7/lib/ruby/1.8/monitor.rb:242:in `synchronize' /home/slugs/311951_4bf369d_2ba5/mnt/.bundle/gems/ruby/1.8/gems/ rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain' /home/slugs/311951_4bf369d_2ba5/mnt/.bundle/gems/ruby/1.8/gems/ rake-0.8.7/lib/rake.rb:607:in `invoke_prerequisites' /home/slugs/311951_4bf369d_2ba5/mnt/.bundle/gems/ruby/1.8/gems/ rake-0.8.7/lib/rake.rb:604:in `each' /home/slugs/311951_4bf369d_2ba5/mnt/.bundle/gems/ruby/1.8/gems/ rake-0.8.7/lib/rake.rb:604:in `invoke_prerequisites' /home/slugs/311951_4bf369d_2ba5/mnt/.bundle/gems/ruby/1.8/gems/ rake-0.8.7/lib/rake.rb:596:in `invoke_with_call_chain' /usr/ruby1.8.7/lib/ruby/1.8/monitor.rb:242:in `synchronize' /home/slugs/311951_4bf369d_2ba5/mnt/.bundle/gems/ruby/1.8/gems/ rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain' /home/slugs/311951_4bf369d_2ba5/mnt/.bundle/gems/ruby/1.8/gems/ rake-0.8.7/lib/rake.rb:583:in `invoke' /home/slugs/311951_4bf369d_2ba5/mnt/.bundle/gems/ruby/1.8/gems/ rake-0.8.7/lib/rake.rb:2051:in `invoke_task' /home/slugs/311951_4bf369d_2ba5/mnt/.bundle/gems/ruby/1.8/gems/ rake-0.8.7/lib/rake.rb:2029:in `top_level' /home/slugs/311951_4bf369d_2ba5/mnt/.bundle/gems/ruby/1.8/gems/ rake-0.8.7/lib/rake.rb:2029:in `each' /home/slugs/311951_4bf369d_2ba5/mnt/.bundle/gems/ruby/1.8/gems/ rake-0.8.7/lib/rake.rb:2029:in `top_level' /home/slugs/311951_4bf369d_2ba5/mnt/.bundle/gems/ruby/1.8/gems/ rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /home/slugs/311951_4bf369d_2ba5/mnt/.bundle/gems/ruby/1.8/gems/ rake-0.8.7/lib/rake.rb:2023:in `top_level' /home/slugs/311951_4bf369d_2ba5/mnt/.bundle/gems/ruby/1.8/gems/ rake-0.8.7/lib/rake.rb:2001:in `run' /home/slugs/311951_4bf369d_2ba5/mnt/.bundle/gems/ruby/1.8/gems/ rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /home/slugs/311951_4bf369d_2ba5/mnt/.bundle/gems/ruby/1.8/gems/ rake-0.8.7/lib/rake.rb:1998:in `run' /home/slugs/311951_4bf369d_2ba5/mnt/.bundle/gems/ruby/1.8/gems/ rake-0.8.7/bin/rake:31 /usr/ruby1.8.7/bin/rake:19:in `load' /usr/ruby1.8.7/bin/rake:19 (in /disk1/home/slugs/311951_4bf369d_2ba5/mnt) **
Re: heroku: command not found
Could it be that you installed the gem with Bundler instead of doing a sudo gem install heroku? Or maybe you have different ruby versions set up and you're executing it from a different one? On Mon, Oct 4, 2010 at 5:40 PM, gleble neil_...@hotmail.com wrote: Hi I am just starting with heroku and have got this far Successfully installed heroku-1.10.11 1 gem installed Installing ri documentation for heroku-1.10.11... Installing RDoc documentation for heroku-1.10.11... n...@neil-laptop:~$ heroku keys:add heroku: command not found Where am I going wrong? -- 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.comheroku%2bunsubscr...@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: Heroku Mongoid config and how it works
It seems MongoMapper is more popular around here. At least it's the solution I'm using and works flawlessly with Heroku. On Mon, Sep 27, 2010 at 2:33 PM, Bradley bradleyrobert...@gmail.com wrote: no one has a comment on this? I thought it'd be a fairly straight forward answer. On Sep 22, 7:11 pm, Bradley bradleyrobert...@gmail.com wrote: I just used a template for a new rails app that sets up everything for use with Mongoid. The mongoid.yml file looks like this: production: host: %= ENV['MONGOID_HOST'] % port: %= ENV['MONGOID_PORT'] % username: %= ENV['MONGOID_USERNAME'] % password: %= ENV['MONGOID_PASSWORD'] % database: %= ENV['MONGOID_DATABASE'] % I added the MONGOHQ_URL config var to my app (with the string given from mongohq), deployed and it worked! My question is...HOW? I don't get how adding that single URL has all of a sudden given me these 5 environment variables. I searched through the heroku docs on mongo and they pretty sparse. Nowhere does it mention that I might use these particular env vars. So how does this happen? -- 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.comheroku%2bunsubscr...@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: Heroku on serious applications and lack of support
Yeah, it can be frustrating some times. I have hope that they will improve in this particular aspect soon though, so I'll stay true to Heroku. On Thu, Sep 16, 2010 at 10:06 PM, Mike mikel...@gmail.com wrote: Are people comfortable with using Heroku on serious applications? If so, how did they come to that decision? I have been developing my application on Heroku for some time now, and I've observed that the support can be really worryingly uneven. I'm running a modest sized app, it's costing me around $150 a month, so at this amount, I know that I can't have dedicated support staff on call whenever I want. However, even when I select My app is unavailable which is presumably their highest level of support, hours can sometimes pass before anyone even gets assigned to my ticket. In my current case, I was upgrading from using Postgres search on my app to Websolr search. To do this, I planned to push as two separate pushes with a migration in between, and their push tool died in the middle of my second push, apparently due to the fact that New Relic was not responding. Now every time I push Heroku is rejecting it saying there is already a slug being compiled, leaving my app in a half-upgraded broken state. It's been like this for hours now, and the support ticket is still awaiting assignment to a help desk operator and there isn't really a single thing I can do to try and improve on the situation. There's nothing I can do to escalate my request, and everything is so abstracted there's no way I can try to fix the problem. Just last month there was another thread by someone whose app was mysteriously stuck in maintenance mode with no one assigned to their support ticket for an entire day. I love how easy Heroku makes it for me to rapidly prototype and develop my app, but it's hard to see how I can stay on it long term with such uneven support. Combine this with the fact that when error messages do come out, and they're terribly unprofessional messages directed towards administrators rather than end users, and I almost feel like they don't even want Heroku to be something that serious applications can use. I submitted a ticket about the error messages when I first saw them like half a year ago, and they said they'd fix them, and they're still like this. Maybe I'm just frustrated right now, what are others' thoughts on this? -- 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.comheroku%2bunsubscr...@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: Error when using memcached uninitialized constant Memcached (NameError)
Hi Riton, I'd suggest that you try this: #Gemfile gem 'SystemTimer' #Not necessary, but memcache recommends it for performance. gem 'memcached' #Notice it's memcached, with a D. #production.rb config.cache_store = :mem_cache_store, Memcached::Rails.new and nothing else. These three lines are what I use in all my projects and that's how I get Memcache running. Good luck. On Sat, Sep 11, 2010 at 12:38 AM, riton enjoy...@gmail.com wrote: hi Oren, Thanks for looking into my issue. Here are the modifications I made to my app , according to the heroku documentation and what you just said. Please, can you tell me what's wrong in that: environment.rb: no changes. I don't have to add the 'config gem' and 'require' lines environment/production.rb: added config.cache_store = :mem_cache_store, Memcached::Rails.new Gemfile: gem memcached-northscale, :require = memcache Is that correct ? If no, do i need gem 'memcache' in my Gemfile ? I tried with it, and with gem 'memcached' but without success. I ran bundle install in my local installation, my gemfile.lock is in GIT and this is fine with heroku's bundle (it runs whenever I add a gem in Gemfile). Here are the gem used with bundle Using rake (0.8.7) Using abstract (1.0.0) Using activesupport (3.0.0.rc2) Using builder (2.1.2) Using i18n (0.4.1) Using activemodel (3.0.0.rc2) Using erubis (2.6.6) Using rack (1.2.1) Using rack-mount (0.6.13) Using rack-test (0.5.4) Using tzinfo (0.3.23) Using actionpack (3.0.0.rc2) Using mime-types (1.16) Using polyglot (0.3.1) Using treetop (1.4.8) Using mail (2.2.5) Using actionmailer (3.0.0.rc2) Using arel (1.0.1) Using activerecord (3.0.0.rc2) Using activeresource (3.0.0.rc2) Using memcache (1.2.13) Using memcached-northscale (0.19.5.4) Using mysql (2.8.1) Using mysql2 (0.2.3) Using bundler (1.0.0) Using thor (0.14.0) Using railties (3.0.0.rc2) Using rails (3.0.0.rc2) And the error: /disk1/home/slugs/283964_74b4131_849c/mnt/config/environments/ production.rb:33: uninitialized constant Memcached (NameError) Sorry, I don't know what to do . On Sep 10, 5:54 pm, Oren Teich o...@heroku.com wrote: if you're using a gemfile, you don't want to have any config.gem directives. It's one or the other. Bundler replaces the way rails 2.3 handles gems. http://gembundler.com/rails23.html http://gembundler.com/rails23.htmlif oyu're using bundler, it's gem memcached-northscale, :require = memcache Oren On Fri, Sep 10, 2010 at 4:15 AM, riton enjoy...@gmail.com wrote: Hello, I added the memcache 5MB free addon to my application. I'm trying to make it work using the northscale gem as specified in the documentation. I can't make it to work. I can't get past this error /production.rb:33: uninitialized constant Memcached (NameError) Here is my Gemfile: gem 'memcache-client' gem 'memcached-northscale' my environment.rb: # Load memcached config.gem 'memcached-northscale', :lib = 'memcached' require 'memcached' my production.rb: config.cache_store = :mem_cache_store, Memcached::Rails.new Despite your documentation saying to remove memcache-client from the Gemfile, (I tried..) some guys seem to say we need it (ex: http://github.com/heroku-examples/r3b4-memcache-heroku/commit/f10e62d. .. ) Well, I'm not sure what I should do. Here is an EVENT_ID i'm getting (sometime) on my app when trying to reach it (error 503), maybe it's related ? Event ID: 05040001c8a60003714f Thanks for helping me out ! -- 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.comheroku%2bunsubscr...@googlegroups.com heroku%2bunsubscr...@googlegroups.comheroku%252bunsubscr...@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.comheroku%2bunsubscr...@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: Delayed Job not loading gem
The environment should be the same. Have you tried to require Hpricot manually from the job that uses it? On Thu, Aug 19, 2010 at 2:29 AM, daniel hoey danielho...@gmail.com wrote: Hi, We use the Hpricot gem on our Heroku app. It is specified in the .gems file and config.gem :hpricot is in the config/environment.rb file. Sometimes our delayed jobs throw a NoMethodError when attempting to use the 'Hpricot()' method. The exact same code with the same data works in the Heroku console. Basically it looks like the delayed jobs do not have the same environment as the console. Does anyone have any suggestions about how to fix this problem? Dan -- 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.comheroku%2bunsubscr...@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: Delayed::Job not working?
You're not alone and I don't think this has been happening since just yesterday but probably a little longer. I thought it was just me. On Wed, Aug 18, 2010 at 11:09 PM, jmay jason@gmail.com wrote: Since at least yesterday, Heroku workers are no longer picking up and executing queued jobs. Is anyone else experiencing this? -Jason -- 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.comheroku%2bunsubscr...@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: check if an index was actually created in a table
Have you tried using the console? Make sure you're on your project's directory and type in the command *heroku console*. You'll enter console mode live on your deployed application and will be able to see which fields your models have. Another good option would be using a rake task remotely like this: *heroku rake db:abort_if_pending_migrations* Good luck. On Sun, Aug 15, 2010 at 11:37 PM, Sergio Lima sergiosouzal...@gmail.comwrote: Hi people, I have a app on Heroku and I have to check if an index was actually created in a table. How can I do that ? How can I see the indexes of a table for example ? And ( in other situations) If I have to check others tables and indexes ? thanks in advance. Sergio -- Sergio Lima sergiosouzal...@gmail.com www.sergiosouzalima.com.br [image: Facebook] http://www.facebook.com/sergiosouzalima[image: Linkedin] http://br.linkedin.com/in/sergiosouzalima[image: Orkut]http://www.orkut.com.br/Main#Profile?uid=5481058371846280601[image: Twitter] http://twitter.com/sergiosouzalima --- @ WiseStamp Signaturehttp://my.wisestamp.com/link?u=xtc3rwygbx8jm5wpsite=www.wisestamp.com/email-install. Get it nowhttp://my.wisestamp.com/link?u=xtc3rwygbx8jm5wpsite=www.wisestamp.com/email-install -- 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.comheroku%2bunsubscr...@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: Open support request stuck in Awaiting assignment to a help desk operator. for 16 hours?
It sure looks like something went wrong during that migration. Have you considered just destroying that application and start again from scratch even moving to your desired stack before you push? On Fri, Aug 13, 2010 at 4:31 PM, chris mcclellan...@gmail.com wrote: Have a request open (#11626) that has just been sitting around, awaiting assignment for entirely too long now. Not sure where else to turn to get some support around here... Maybe one of y'all can help me. Getting this error when I try to push to a repo that I've recently stack:migrate'd: pumpkin:bazaar chrismcc$ git push staging master ! App git repo is being migrated. Please try again later. fatal: The remote end hung up unexpectedly ... -- 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.comheroku%2bunsubscr...@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: workers crashing....
Segmentation faults are the most mysterious of faults... could it be some incompatibility between Ruby 1.8.6 and the PostgreSQL adapter? On Thu, Aug 12, 2010 at 5:38 PM, Chris Kalaboukis thinkfut...@gmail.comwrote: I think I found the culprit: == dj-1943630-crashlog.log == (in /disk1/home/slugs/152245_4b6a640_e6b3/mnt) RPM Monitoring DJ worker host:railgun64.29102 pid:9157 ** [NewRelic] Connected to NewRelic Service at collector5.newrelic.com:80 ** [NewRelic] New Relic RPM Agent 2.12.3 Initialized: pid = 9157 ** [NewRelic] Agent Log found in /disk1/home/slugs/152245_4b6a640_e6b3/mnt/log/newrelic_agent.log *** Starting job worker host:railgun64.29102 pid:9157 /usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/active_record/connection_adapters/postgresql_adapter.rb:1102: [BUG] Segmentation fault ruby 1.8.6 (2008-08-11) [x86_64-linux] Any ideas on how to fix? On Thu, 2010-08-12 at 01:28 -0700, Chris Kalaboukis wrote: Hi all: I've got workers crashing for no apparent reason. Have the exception code in there but it just stops running and ps reports crashed. Neither heroku logs or New Relic have anything to add. Where can I find out why a workers crashed like that? Thanks...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.comheroku%2bunsubscr...@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: workers crashing....
Heroku is supposed to restart a worker everytime it crashes. Whatever is in your jobs:work task will be executed as soon as it fails. However, I run a very dependent on background jobs webapp in Heroku and this is not enough for me. What I did was create a rake task that finds the last record to be updated and issue a background job to update the next after that one and automate the task to find the rest of the records that need to be updated. The only thing you'll be able to do to interact with your app once it's deployed are Rake tasks. On Thu, Aug 12, 2010 at 5:54 PM, Chris Kalaboukis thinkfut...@gmail.comwrote: Possibly. Problem is I can't seem to catch it...do you know how I can, other than running some monitor to restart. BTW, how do I restart a crashed job? Is there a way to do it from the heroku command line? Thanks...Chris On Thu, 2010-08-12 at 17:47 +0200, Abel Tamayo wrote: Segmentation faults are the most mysterious of faults... could it be some incompatibility between Ruby 1.8.6 and the PostgreSQL adapter? On Thu, Aug 12, 2010 at 5:38 PM, Chris Kalaboukis thinkfut...@gmail.com wrote: I think I found the culprit: == dj-1943630-crashlog.log == (in /disk1/home/slugs/152245_4b6a640_e6b3/mnt) RPM Monitoring DJ worker host:railgun64.29102 pid:9157 ** [NewRelic] Connected to NewRelic Service at collector5.newrelic.com:80 ** [NewRelic] New Relic RPM Agent 2.12.3 Initialized: pid = 9157 ** [NewRelic] Agent Log found in /disk1/home/slugs/152245_4b6a640_e6b3/mnt/log/newrelic_agent.log *** Starting job worker host:railgun64.29102 pid:9157 /usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/active_record/connection_adapters/postgresql_adapter.rb:1102: [BUG] Segmentation fault ruby 1.8.6 (2008-08-11) [x86_64-linux] Any ideas on how to fix? On Thu, 2010-08-12 at 01:28 -0700, Chris Kalaboukis wrote: Hi all: I've got workers crashing for no apparent reason. Have the exception code in there but it just stops running and ps reports crashed. Neither heroku logs or New Relic have anything to add. Where can I find out why a workers crashed like that? Thanks...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. -- 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.comheroku%2bunsubscr...@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: workers crashing....
It's done automatically. You don't have to select or configure anything. On Thu, Aug 12, 2010 at 6:33 PM, Chris Kalaboukis thinkfut...@gmail.comwrote: Hi Abel: For some reason, its not restarting the job. Is there a way to change that setting - its not re-starting the job its just hanging there. i need it to restart when it fails, can you tell me what I need to edit in order to make it do that? Thanks...Chris On Thu, 2010-08-12 at 18:15 +0200, Abel Tamayo wrote: Heroku is supposed to restart a worker everytime it crashes. Whatever is in your jobs:work task will be executed as soon as it fails. However, I run a very dependent on background jobs webapp in Heroku and this is not enough for me. What I did was create a rake task that finds the last record to be updated and issue a background job to update the next after that one and automate the task to find the rest of the records that need to be updated. The only thing you'll be able to do to interact with your app once it's deployed are Rake tasks. On Thu, Aug 12, 2010 at 5:54 PM, Chris Kalaboukis thinkfut...@gmail.com wrote: Possibly. Problem is I can't seem to catch it...do you know how I can, other than running some monitor to restart. BTW, how do I restart a crashed job? Is there a way to do it from the heroku command line? Thanks...Chris On Thu, 2010-08-12 at 17:47 +0200, Abel Tamayo wrote: Segmentation faults are the most mysterious of faults... could it be some incompatibility between Ruby 1.8.6 and the PostgreSQL adapter? On Thu, Aug 12, 2010 at 5:38 PM, Chris Kalaboukis thinkfut...@gmail.com wrote: I think I found the culprit: == dj-1943630-crashlog.log == (in /disk1/home/slugs/152245_4b6a640_e6b3/mnt) RPM Monitoring DJ worker host:railgun64.29102 pid:9157 ** [NewRelic] Connected to NewRelic Service at collector5.newrelic.com:80 ** [NewRelic] New Relic RPM Agent 2.12.3 Initialized: pid = 9157 ** [NewRelic] Agent Log found in /disk1/home/slugs/152245_4b6a640_e6b3/mnt/log/newrelic_agent.log *** Starting job worker host:railgun64.29102 pid:9157 /usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/active_record/connection_adapters/postgresql_adapter.rb:1102: [BUG] Segmentation fault ruby 1.8.6 (2008-08-11) [x86_64-linux] Any ideas on how to fix? On Thu, 2010-08-12 at 01:28 -0700, Chris Kalaboukis wrote: Hi all: I've got workers crashing for no apparent reason. Have the exception code in there but it just stops running and ps reports crashed. Neither heroku logs or New Relic have anything to add. Where can I find out why a workers crashed like that? Thanks...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. -- 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. -- 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
Re: Running Memcached
Why are you installing memcached-northscale instead of just memcached? On Wed, Aug 11, 2010 at 12:34 AM, Chris Kalaboukis thinkfut...@gmail.comwrote: Hi guys: I've just installed Memcached and my development environment is hosed - responds with ch...@chris-laptop:~/strong-fog-31$ ruby script/server = Booting WEBrick = Rails 2.3.8 application starting on http://0.0.0.0:3000 Missing these required gems: memcached-northscale You're running: ruby 1.8.7.249 at /usr/bin/ruby1.8 rubygems 1.3.5 at /home/chris/.gem/ruby/1.8, /var/lib/gems/1.8 Run `rake gems:install` to install the missing gems. ch...@chris-laptop:~/strong-fog-31$ rake gems:install (in /home/chris/strong-fog-31) DEPRECATION WARNING: Rake tasks in vendor/plugins/delayed_job/tasks and vendor/plugins/jrails/tasks are deprecated. Use lib/tasks instead. (called from /home/chris/.gem/ruby/1.8/gems/rails-2.3.8/lib/tasks/ rails.rb:10) rake aborted! no such file to load -- memcached (See full trace by running task with --trace) ch...@chris-laptop:~/strong-fog-31$ ruby script/generate migration archivecapture Missing these required gems: memcached-northscale You're running: ruby 1.8.7.249 at /usr/bin/ruby1.8 rubygems 1.3.5 at /home/chris/.gem/ruby/1.8, /var/lib/gems/1.8 Run `rake gems:install` to install the missing gems. So when i try to run rake, it craps out. Does anyone know how I can edit my config so I can get this working again? Thanks...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.comheroku%2bunsubscr...@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: Rails 3 doesn't officially support Ruby 1.9.1
The best you can do is either find a deployment stack with the specifications you're using or adapt your environment to what is offered by Heroku. I'm checking the documents and it seems that Bamboo MRI supports Ruby 1.9.1. On Tue, Aug 10, 2010 at 10:53 AM, Stefan Wintermeyer stefan.winterme...@amooma.de wrote: Hi, just wanted to do a heroku rake db:migrate and look what happened. The current situation with Ruby 1.9.1 on Heroku is a bit disappointing. I really would like to use Heroku but haven't been able to fire up a single Rails 3 server yet. ---cut--- s...@swmbp 0 1.9.2-preview3 gemeinschaft.heroku.com(master)$ heroku rake db:migrate Rails 3 doesn't officially support Ruby 1.9.1 since recent stable releases have segfaulted the test suite. Please upgrade to Ruby 1.9.2 before Rails 3 is released! You're running ruby 1.9.1p129 (2009-05-12 revision 23412) [x86_64-linux] rake aborted! /disk1/home/slugs/209589_ac244c3_4557/mnt/.bundle/gems/ruby/1.9.1/gems/workflow-0.6.0/lib/workflow.rb:182: Invalid return (See full trace by running task with --trace) (in /disk1/home/slugs/209589_ac244c3_4557/mnt) s...@swmbp 0 1.9.2-preview3 gemeinschaft.heroku.com(master)$ ---cut--- 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.comheroku%2bunsubscr...@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: Rails3 RC from master failed to start
Guys, what's the command to install RC4? I'm trying something like: gem install bundler --version '1.0.0.rc.4' --pre but I'm getting an error that that version can't be found in any of the sources (rubygems). I can only install RC5. On Tue, Aug 10, 2010 at 3:33 AM, Pasha pavel.chip...@gmail.com wrote: This bug is now fixed http://github.com/carlhuda/bundler/blob/master/CHANGELOG.md Please update bundler to 1.0.0.rc4 On Aug 6, 3:49 am, Terence Lee hon...@gmail.com wrote: We have a workaround here:http://docs.heroku.com/bundler100rc2-git Please file a support ticket if you're still having issues Thanks, Terence On Thu, 2010-08-05 at 16:07 -0700, garyf wrote: I am pleased that our production platform for Rails 2.3.8 is receiving such aggressive beta testing of the RC. In a few weeks, or months, I have no doubt that Heroku will be rock solid with Rails 3.0. Gary http://realized-app.com On Aug 5, 6:06 pm, Chris Conley chris.m.con...@gmail.com wrote: Yeah I agree. I should've mentioned that it was a temporary solution. Thanks! On Thu, Aug 5, 2010 at 5:59 PM, Nick Quaranto n...@quaran.to wrote: How about git://github.com/rails/rails.git ? Also, I've been trying to discourage gem forking unless if it's really, really necessary...you can point bundler to a git repo, why is pushing the gem necessary then? On Thu, Aug 5, 2010 at 5:56 PM, Chris Conley chris.m.con...@gmail.com wrote: I just got around this by forking the git gem and pushing to rubygems.org. Here's drnic's guide to doing just that: http://drnicwilliams.com/2009/11/04/hacking-someones-gem-with-github-... On Thu, Aug 5, 2010 at 5:33 PM, Chris Conley chris.m.con...@gmail.com wrote: Yeah, I'm getting the same error as well. On Thu, Aug 5, 2010 at 5:11 PM, lstoll l...@lds.li wrote: I'm having a similar problem - seems that any gem that is installed from a git source will fail like this. On Aug 5, 10:47 pm, morgoth w.wnetr...@gmail.com wrote: After pushing application to heroku I get error:http://gist.github.com/510350 Anybody having similar problem? -- 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.comheroku%2bunsubscr...@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.comheroku%2bunsubscr...@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.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. signature.asc 1KViewDownload -- 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.comheroku%2bunsubscr...@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.
