Re: Killing Cron Process?
heroku restart should restart all of your process, including cron. you can also remove and add the add-on Oren On Wed, Dec 29, 2010 at 10:50 AM, Zach Bailey wrote: > I have a long-running cron process as a result of an out of control task > that I need to kill. Is it possible to do this via the heroku gem or console > somehow? > > -Zach > > -- > 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: heroku db:push doesnt work
what are you entering for a command? On Mon, Dec 27, 2010 at 2:31 AM, Sasha wrote: > tried reinstall heroku and taps and nothing helped :( > > here what im getting: > > Sending schema > c:/Ruby192/lib/ruby/gems/1.9.1/gems/sequel-3.17.0/lib/sequel/adapters/ > sqlite.rb:5:in `rescue in ': SQLite3::Database#type_ > translation is not defined. If you are using the sqlite3 gem, please > install the sqlite3-ruby gem. (Sequel::Error) >from c:/Ruby192/lib/ruby/gems/1.9.1/gems/sequel-3.17.0/lib/ > sequel/adapters/sqlite.rb:2:in `' >from :29:in `require' >from :29:in `require' >from c:/Ruby192/lib/ruby/gems/1.9.1/gems/sequel-3.17.0/lib/ > sequel/core.rb:249:in `block in tsk_require' >from c:/Ruby192/lib/ruby/gems/1.9.1/gems/sequel-3.17.0/lib/ > sequel/core.rb:72:in `block in check_requiring_thread' >from :10:in `synchronize' >from c:/Ruby192/lib/ruby/gems/1.9.1/gems/sequel-3.17.0/lib/ > sequel/core.rb:69:in `check_requiring_thread' >from c:/Ruby192/lib/ruby/gems/1.9.1/gems/sequel-3.17.0/lib/ > sequel/core.rb:249:in `tsk_require' >from c:/Ruby192/lib/ruby/gems/1.9.1/gems/sequel-3.17.0/lib/ > sequel/database/connecting.rb:25:in `adapter_class' >from c:/Ruby192/lib/ruby/gems/1.9.1/gems/sequel-3.17.0/lib/ > sequel/database/connecting.rb:54:in `connect' >from c:/Ruby192/lib/ruby/gems/1.9.1/gems/sequel-3.17.0/lib/ > sequel/core.rb:119:in `connect' >from c:/Ruby192/lib/ruby/gems/1.9.1/gems/taps-0.3.14/lib/taps/ > schema.rb:18:in `dump_table' >from c:/Ruby192/lib/ruby/gems/1.9.1/gems/taps-0.3.14/bin/ > schema:32:in `' > > > p.s im using rails 3.0.3 (ruby 1.9.1) on windows (yes-yes windows with > small 'w' ) > > -- > 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.
s3 performance question
I'm seeing AWS::S3::S3Object.find take about 100 ms. Is this about right? I was hoping for better speeds. -- 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: 1.9.2 Stack
Just to know, what did you push in order for heroku to migrate your
stack?
On Dec 13, 11:20 pm, Scott LaBounty wrote:
> Thanks! That cleared up one problem anyway. It looks like I may have other
> issues, but I'll try to work them out.
>
> Scott
>
>
>
>
>
>
>
>
>
> On Mon, Dec 13, 2010 at 2:00 PM, Robert Eanes wrote:
> > You want the pg gem, not the ruby-pg gem, which looks like it hasn't been
> > updated since 2008. I've used it locally and on heroku with 1.9.2
> > successfully.
>
> > On Dec 13, 2010, at 3:49 PM, Scott LaBounty wrote:
>
> > > OK, continuing on here. I just use sqlite locally for development and
> > don't have postgres installed. I get the same error when I try to install it
> > on my machine. Is the ruby-pg gem incompatible with ruby 1.9.2? If so, then
> > how on earth does the 1.9.2 stack work for anything on Heroku?
>
> > > Scott
>
> > > On Mon, Dec 13, 2010 at 12:38 PM, Scott LaBounty
> > wrote:
> > > One more thought ... would it help to delete the app and then regenerate
> > it with ruby 1.9.2 to start with? For the record, I'm using Ramaze and
> > Sequel here, not Rails.
>
> > > Scott
>
> > > On Mon, Dec 13, 2010 at 10:49 AM, Scott LaBounty
> > wrote:
> > > OK, when I changed something and did a new push, I get ...
>
> > > <<
> > > -> Installing gem ruby-pg fromhttp://rubygems.org
> > > Building native extensions. This could take a while...
> > > ERROR: Error installing ruby-pg:
> > > ERROR: Failed to build gem native extension.
>
> > > /usr/ruby1.9.2/bin/ruby extconf.rb
> > > *** extconf.rb failed ***
> > > Could not create Makefile due to some reason, probably lack of
> > > necessary libraries and/or headers. Check the mkmf.log file for
> > more
> > > details. You may need configuration options.
>
> > > Provided configuration options:
> > > --with-opt-dir
> > > --without-opt-dir
> > > --with-opt-include
> > > --without-opt-include=${opt-dir}/include
> > > --with-opt-lib
> > > --without-opt-lib=${opt-dir}/lib
> > > --with-make-prog
> > > --without-make-prog
> > > --srcdir=.
> > > --curdir
> > > --ruby=/usr/ruby1.9.2/bin/ruby
> > > extconf.rb:4:in `': uninitialized constant Object::PLATFORM
> > (NameError)
>
> > > Gem files will remain installed in
> > /code/repos/377655/gems_build/gems/ruby-pg-0.7.9.2008.01.28 for inspection.
> > > Results logged to
> > /code/repos/377655/gems_build/gems/ruby-pg-0.7.9.2008.01.28/ext/gem_make.ou
> > t
> > > ! Heroku push rejected, failed to install gem
>
> > > It looks like the ruby-pg gem won't build with 1.9.2?
>
> > > Scott
>
> > > On Mon, Dec 13, 2010 at 9:59 AM, Scott LaBounty
> > wrote:
> > > All,
>
> > > I was getting the following error:
>
> > > <<
>
> > /disk1/home/slugs/377655_fdff8e6_b844-847cc755-b706-4bc4-bc3b-9927cb45f112/
> > mnt/model/init.rb:10:
> > undefined method `require_relative' for main:Object (NoMethodError)
> > > from
> > /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> > `gem_original_require'
> > > from
> > /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> > `require'
> > > from
> > /disk1/home/slugs/377655_fdff8e6_b844-847cc755-b706-4bc4-bc3b-9927cb45f112/
> > mnt/app.rb:13
> > > from
> > /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> > `gem_original_require'
> > > from
> > /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> > `require'
> > > from config.ru:18
> > > from /home/heroku_rack/heroku.ru:23
> > > from
> > /home/slugs/377655_fdff8e6_b844-847cc755-b706-4bc4-bc3b-9927cb45f112/mnt/.g
> > ems/gems/rack-1.2.1/lib/rack/builder.rb:46:in
> > `instance_eval'
> > > from
> > /home/slugs/377655_fdff8e6_b844-847cc755-b706-4bc4-bc3b-9927cb45f112/mnt/.g
> > ems/gems/rack-1.2.1/lib/rack/builder.rb:46:in
> > `initialize'
> > > from
> > /home/slugs/377655_fdff8e6_b844-847cc755-b706-4bc4-bc3b-9927cb45f112/mnt/.g
> > ems/gems/rack-1.2.1/lib/rack/builder.rb:63:in
> > `new'
> > > from
> > /home/slugs/377655_fdff8e6_b844-847cc755-b706-4bc4-bc3b-9927cb45f112/mnt/.g
> > ems/gems/rack-1.2.1/lib/rack/builder.rb:63:in
> > `map'
> > > from /home/heroku_rack/heroku.ru:18
> > > from
> > /home/slugs/377655_fdff8e6_b844-847cc755-b706-4bc4-bc3b-9927cb45f112/mnt/.g
> > ems/gems/rack-1.2.1/lib/rack/builder.rb:46:in
> > `instance_eval'
> > > from
> > /home/slugs/377655_fdff8e6_b844-847cc755-b706-4bc4-bc3b-9927cb45f112/mnt/.g
> > ems/gems/rack-1.2.1/lib/rack/builder.rb:46:in
> > `initialize'
> > > from /home/heroku_rack/heroku.ru:11:in `new'
> > > from /home/heroku_rack/heroku.ru:11
> > > from
> > /home/slugs/377655_fdff8e6_b844-847cc755-b706-4bc4-bc3b-9927cb45f112/mnt/.g
> > ems/gems/rack-1.2.1/lib/rack/builder.rb:46:in
> > `instance_eval'
> > > from
Re: 1.9.2 Stack
And it worked, of course. I think it's definitely the best way to do it! On Thu, Dec 30, 2010 at 7:41 PM, Vincent Coste wrote: > Okay thank's a lot for your time Scott, I'll do that! > > > On Thu, Dec 30, 2010 at 7:34 PM, Scott LaBounty wrote: > >> Vince, >> >> After looking a 2nd time at my history, it seems like I might have given >> up on the migration to 1.9.2 and just gone with a recreation: >> >> heroku create --stack bamboo-mri-1.9.2 >> >> Scott >> >> >> On Thu, Dec 30, 2010 at 9:57 AM, Vincent Coste >> wrote: >> >>> Okay, I don't have a .gems but un Gemfile. And i have pg defined into it. >>> >>> >>> Her is the content of my Gemfile; >>> >>> source 'http://rubygems.org' > gem 'rails', '3.0.1' > gem 'nokogiri' gem 'jquery-rails' gem 'haml' gem 'devise' gem 'omniauth' gem "friendly_id", "~> 3.1" > gem 'sqlite3-ruby', :require => 'sqlite3' > group :production do gem "pg" end > group :development, :test do gem 'machinist', '>= 2.0.0.beta1' gem 'fakeweb' gem 'mocha' gem 'compass' end >>> >>> The weird thing is that when I git push, the logs tell me that the stack >>> changes from 1.8.7 to 1.9.2, but actually not. >>> >>> Weird! >>> >>> >>> >>> On Thu, Dec 30, 2010 at 6:15 PM, Scott LaBounty wrote: >>> Vince, OK, now I'm with you. I think what finally did it was to put "pg" in my .gems file rather than "pg-ruby". If that doesn't work, let me know and I'll look a bit more. Scott On Thu, Dec 30, 2010 at 7:18 AM, Vincent Coste >>> > wrote: > Hi Scott, thanks for the faste answer. > > Actually, my question was more about what kind of code push did you do > in order to migrate your stack? I have almost the same problem you had: > > git push heroku master > > Counting objects: 87, done. > > Delta compression using up to 2 threads. > > Compressing objects: 100% (48/48), done. > > Writing objects: 100% (50/50), 7.23 KiB, done. > > Total 50 (delta 31), reused 0 (delta 0) > > >> -> Heroku receiving push > > -> Migrating from bamboo-ree-1.8.7 to bamboo-mri-1.9.2 > > > [..] > > > Your bundle is complete! It was installed into ./.bundle/gems > > -> Installing Exceptional plugin from git:// > github.com/contrast/exceptional.git... done. > >Compiled slug size is 6.7MB > > -> Launching... done > >deployed to Heroku > > > -> Migration complete, your app is now running on bamboo-mri-1.9.2 > > > > > > > And on an heroku stack: > > heroku stack > > aspen-mri-1.8.6 > > * bamboo-ree-1.8.7 > > bamboo-mri-1.9.1 (beta) > > bamboo-mri-1.9.2 (beta) (prepared, will migrate on next git push) > > > > > If i can't do it soon, i think i'm gonna recreate an app directly with > the right stack. > > Regards, > > > > On Wed, Dec 29, 2010 at 8:06 PM, Scott LaBounty > wrote: > >> Vince, >> >> Here's a post I did on Heroku and Sequel ... >> >> http://steamcode.blogspot.com/2010/09/sequel-and-heroku.html >> >> To push your database do: >> >> heroku db:push sqlite://mydatabase.sqlite >> heroku restart >> >> Is this what you're looking for? If not, let me know and I'll see what >> else I've got. Locally, I just use sqlite and then pretty much everything >> works on Heroku with Postgres. >> >> Scott >> >> On Wed, Dec 29, 2010 at 5:26 AM, Vincent Coste < >> coste.vinc...@gmail.com> wrote: >> >>> Just to know, what did you push in order for heroku to migrate your >>> stack? >>> >>> On Dec 13, 11:20 pm, Scott LaBounty wrote: >>> > Thanks! That cleared up one problem anyway. It looks like I may >>> have other >>> > issues, but I'll try to work them out. >>> > >>> > Scott >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > On Mon, Dec 13, 2010 at 2:00 PM, Robert Eanes >>> wrote: >>> > > You want the pg gem, not the ruby-pg gem, which looks like it >>> hasn't been >>> > > updated since 2008. I've used it locally and on heroku with 1.9.2 >>> > > successfully. >>> > >>> > > On Dec 13, 2010, at 3:49 PM, Scott LaBounty wrote: >>> > >>> > > > OK, continuing on here. I just use sqlite locally for >>> development and >>> > > don't have postgres installed. I get the same error when I try to >>> install it >>> > > on my machine. Is the ruby-pg gem incompatible with ruby 1.9.2? >>> If so, then >>> > > how on earth does the 1.9.2 stack work for a
Re: DATABASE_URL vs. SHARED_DATABASE_URL
Hello Wes, Answer to your questions below: On Tue, 2010-12-28 at 17:14 -0600, Wes Gamble wrote: > From http://docs.heroku.com/database: > > > "Each database installed on a Heroku app has a unique database URL > which can be used by your app to connect to that database. The URLs > are viewable and accessible through config vars. The config var name > for the default shared database is SHARED_DATABASE_URL. > > In addition, each app has a config var named DATABASE_URL, which is > the database that Rails will use by default. You can change which > database is set to DATABASE_URL with the ‘heroku pg:promote’ command." > > > I'm confused. > > > 1) Do both of these configuration variables always exist for a given > app.? Yes. > > > 2) When would SHARED_DATABASE_URL be used as opposed to DATABASE_URL? The SHARED_DATABASE_URL just keeps track of the shared database url. The DATABASE_URL is what actually gets written out to config/database.yml for your app. When you first create your heroku app these two config vars should be the same. When you have more than one database the value of having two config vars becomes apparent. For instance, you might choose to use Amazon RDS where you would change your DATABASE_URL. The SHARED_DATABASE_URL is still around in case you decide to switch back. If you decided to purchase a dedicated database, you'd get a HEROKU_POSTGRESQL_RONIN_URL for instance which you would promote to your DATABASE_URL. When you decide to downgrade you could promote your SHARED_DATABASE_URL back. Hope that helps, Terence > > Thanks, > Wes > > > -- > 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: After redeploy, my app still displays old index page
I am having the same problem after my last push. http://emberlene.heroku.com/ The default Rails page is showing and it runs correctly locally. If I go directly to a page it works fine: http://emberlene.heroku.com/about http://emberlene.heroku.com/contact http://emberlene.heroku.com/help http://emberlene.heroku.com/signup They all work if you try: http://emberlene.heroku.com/ or http://emberlene.heroku.com/home or click on any of the links on the pages that work you get the default Rails page. I will post back if I figure it out. On Nov 9, 11:14 pm, Mouli wrote: > Hi, > > I deployed a site in Heroku few months back (url:http://pyaronweb.heroku.com) > where I just created static html pages in public folder of rails. > > Yesterday, I redeployed a new version - updates include removal of > static html pages (including my index.html) and routing through > controllers. In my routes.rb, I used 'root :to => "home#index"' (home > is my controller name with index method present in it.) > > After my redeploying, my app still displays the old index page. Just > checked if app was not deployed at all but I can see that it has been > deployed by manually visitinghttp://pyaronweb.heroku.com/home. > > I could see the routing works properly in my dev environment by > visiting localhost:3000. I run Rails 3. > > Let me know if further info required. Your help is greatly > appreciated. > > - Mouli -- 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.
heroku rake db:migrate error
I want upload some changes to my heroku up, but if I type heroku rake db:migrate I got this error: rake aborted! Permission denied - /home/slugs/379875_18c20e2_b265-4dc295df-e7e6-4e95- b692-87812981aaa5/mnt/tmp/schema.rb (See full trace by running task with --trace) (in /disk1/home/slugs/379875_18c20e2_b265-4dc295df-e7e6-4e95- b692-87812981aaa5/mnt) Default gems, and config. What's wrong? full trace by running task with --trace rake aborted! Permission denied - /home/slugs/ 379875_18c20e2_b265-196b9596-81a6-480f-8772-c91e7936c322/mnt/tmp/ schema.rb /home/slugs/379875_18c20e2_b265-196b9596-81a6-480f-8772- c91e7936c322/mnt/.gems/gems/rails-2.3.8/lib/tasks/databases.rake: 255:in initialize' /home/slugs/ 379875_18c20e2_b265-196b9596-81a6-480f-8772-c91e7936c322/mnt/.gems/ gems/rails-2.3.8/lib/tasks/databases.rake:255:inopen' /home/slugs/ 379875_18c20e2_b265-196b9596-81a6-480f-8772-c91e7936c322/mnt/.gems/ gems/rails-2.3.8/lib/tasks/databases.rake:255 /usr/ruby1.8.7/lib/ruby/ gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in call' /usr/ruby1.8.7/lib/ ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:inexecute' /usr/ ruby1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in each' / usr/ruby1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb: 631:inexecute' /usr/ruby1.8.7/lib/ruby/gems/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:insynchronize' /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/ rake-0.8.7/lib/rake.rb:590:in invoke_with_call_chain' /usr/ruby1.8.7/ lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:583:ininvoke' /home/ slugs/379875_18c20e2_b265-196b9596-81a6-480f-8772-c91e7936c322/ mnt/.gems/gems/rails-2.3.8/lib/tasks/databases.rake:113 /usr/ruby1.8.7/ lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in call' /usr/ ruby1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb: 636:inexecute' /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/ rake.rb:631:in each' /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/ lib/rake.rb:631:inexecute' /usr/ruby1.8.7/lib/ruby/gems/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:insynchronize' /usr/ruby1.8.7/lib/ruby/ gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:in invoke_with_call_chain' / usr/ruby1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb: 583:ininvoke' /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/ rake.rb:2051:in invoke_task' /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/ rake-0.8.7/lib/rake.rb:2029:intop_level' /usr/ruby1.8.7/lib/ruby/gems/ 1.8/gems/rake-0.8.7/lib/rake.rb:2029:in each' /usr/ruby1.8.7/lib/ruby/ gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:intop_level' /usr/ruby1.8.7/ lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in standard_exception_handling' /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/ rake-0.8.7/lib/rake.rb:2023:intop_level' /usr/ruby1.8.7/lib/ruby/gems/ 1.8/gems/rake-0.8.7/lib/rake.rb:2001:in run' /usr/ruby1.8.7/lib/ruby/ gems/1.8/gems/rake-0.8.7/lib/rake.rb: 2068:instandard_exception_handling' /usr/ruby1.8.7/lib/ruby/gems/1.8/ gems/rake-0.8.7/lib/rake.rb:1998:in run' /usr/ruby1.8.7/lib/ruby/gems/ 1.8/gems/rake-0.8.7/bin/rake:31 /usr/ruby1.8.7/bin/rake:19:inload' / usr/ruby1.8.7/bin/rake:19 (in /disk1/home/slugs/ 379875_18c20e2_b265-196b9596-81a6-480f-8772-c91e7936c322/mnt) ** Invoke db:migrate (first_time) ** Invoke environment (first_time) ** Execute environment ** Execute db:migrate ** Invoke db:schema:dump (first_time) ** Invoke environment ** Execute db:schema:dump -- 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: 1.9.2 Stack
Hi Scott, thanks for the faste answer.
Actually, my question was more about what kind of code push did you do in
order to migrate your stack? I have almost the same problem you had:
git push heroku master
Counting objects: 87, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (48/48), done.
Writing objects: 100% (50/50), 7.23 KiB, done.
Total 50 (delta 31), reused 0 (delta 0)
> -> Heroku receiving push
-> Migrating from bamboo-ree-1.8.7 to bamboo-mri-1.9.2
[..]
Your bundle is complete! It was installed into ./.bundle/gems
-> Installing Exceptional plugin from git://
github.com/contrast/exceptional.git... done.
Compiled slug size is 6.7MB
-> Launching... done
deployed to Heroku
-> Migration complete, your app is now running on bamboo-mri-1.9.2
And on an heroku stack:
heroku stack
aspen-mri-1.8.6
* bamboo-ree-1.8.7
bamboo-mri-1.9.1 (beta)
bamboo-mri-1.9.2 (beta) (prepared, will migrate on next git push)
If i can't do it soon, i think i'm gonna recreate an app directly with the
right stack.
Regards,
On Wed, Dec 29, 2010 at 8:06 PM, Scott LaBounty wrote:
> Vince,
>
> Here's a post I did on Heroku and Sequel ...
>
> http://steamcode.blogspot.com/2010/09/sequel-and-heroku.html
>
> To push your database do:
>
> heroku db:push sqlite://mydatabase.sqlite
> heroku restart
>
> Is this what you're looking for? If not, let me know and I'll see what else
> I've got. Locally, I just use sqlite and then pretty much everything works
> on Heroku with Postgres.
>
> Scott
>
> On Wed, Dec 29, 2010 at 5:26 AM, Vincent Coste wrote:
>
>> Just to know, what did you push in order for heroku to migrate your
>> stack?
>>
>> On Dec 13, 11:20 pm, Scott LaBounty wrote:
>> > Thanks! That cleared up one problem anyway. It looks like I may have
>> other
>> > issues, but I'll try to work them out.
>> >
>> > Scott
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > On Mon, Dec 13, 2010 at 2:00 PM, Robert Eanes wrote:
>> > > You want the pg gem, not the ruby-pg gem, which looks like it hasn't
>> been
>> > > updated since 2008. I've used it locally and on heroku with 1.9.2
>> > > successfully.
>> >
>> > > On Dec 13, 2010, at 3:49 PM, Scott LaBounty wrote:
>> >
>> > > > OK, continuing on here. I just use sqlite locally for development
>> and
>> > > don't have postgres installed. I get the same error when I try to
>> install it
>> > > on my machine. Is the ruby-pg gem incompatible with ruby 1.9.2? If so,
>> then
>> > > how on earth does the 1.9.2 stack work for anything on Heroku?
>> >
>> > > > Scott
>> >
>> > > > On Mon, Dec 13, 2010 at 12:38 PM, Scott LaBounty <
>> slabou...@gmail.com>
>> > > wrote:
>> > > > One more thought ... would it help to delete the app and then
>> regenerate
>> > > it with ruby 1.9.2 to start with? For the record, I'm using Ramaze and
>> > > Sequel here, not Rails.
>> >
>> > > > Scott
>> >
>> > > > On Mon, Dec 13, 2010 at 10:49 AM, Scott LaBounty <
>> slabou...@gmail.com>
>> > > wrote:
>> > > > OK, when I changed something and did a new push, I get ...
>> >
>> > > > <<
>> > > > -> Installing gem ruby-pg fromhttp://rubygems.org
>> > > >Building native extensions. This could take a while...
>> > > >ERROR: Error installing ruby-pg:
>> > > >ERROR: Failed to build gem native extension.
>> >
>> > > >/usr/ruby1.9.2/bin/ruby extconf.rb
>> > > >*** extconf.rb failed ***
>> > > >Could not create Makefile due to some reason, probably lack
>> of
>> > > >necessary libraries and/or headers. Check the mkmf.log file
>> for
>> > > more
>> > > >details. You may need configuration options.
>> >
>> > > >Provided configuration options:
>> > > >--with-opt-dir
>> > > >--without-opt-dir
>> > > >--with-opt-include
>> > > >--without-opt-include=${opt-dir}/include
>> > > >--with-opt-lib
>> > > >--without-opt-lib=${opt-dir}/lib
>> > > >--with-make-prog
>> > > >--without-make-prog
>> > > >--srcdir=.
>> > > >--curdir
>> > > >--ruby=/usr/ruby1.9.2/bin/ruby
>> > > >extconf.rb:4:in `': uninitialized constant
>> Object::PLATFORM
>> > > (NameError)
>> >
>> > > >Gem files will remain installed in
>> > > /code/repos/377655/gems_build/gems/ruby-pg-0.7.9.2008.01.28 for
>> inspection.
>> > > >Results logged to
>> > >
>> /code/repos/377655/gems_build/gems/ruby-pg-0.7.9.2008.01.28/ext/gem_make.ou
>> t
>> > > > ! Heroku push rejected, failed to install gem
>> >
>> > > > It looks like the ruby-pg gem won't build with 1.9.2?
>> >
>> > > > Scott
>> >
>> > > > On Mon, Dec 13, 2010 at 9:59 AM, Scott LaBounty <
>> slabou...@gmail.com>
>> > > wrote:
>> > > > All,
>> >
>> > > > I was getting the following error:
>> >
>> > > > <<
>> >
>> > >
>> /disk1/home/slugs/377655_fdff8e6_b844-847cc755-b706-4bc4-bc3b-9927cb45f112/
Ronin database connection down, but not reflected in status -- what gives?
Hi folks, My app is currently down, not serving any traffic at all, and when I run this command I see: MacBook-Pro:Husband-Redis eric$ heroku pg:psql --app myappname ! The database is not available I am running on the Ronin database. A check of http://status.heroku.com shows that all systems are running normally. I looked at the Heroku support page, and it looks like they only monitor the support email alias during business hours? Is there anything I can do, or must I wait until 6am PST tomorrow? And is a disconnect between the Heroku status page and actual app uptime a common thing? Thanks, Eric -- 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.
Heroku and VPN
Hi, I'm planning a rails application which needs to access some services through a corporate VPN. A VPN is the only way we can access these services, they don't offer any other alternative. Is this setup possible in Heroku? Kind regards, Christian -- 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.
rack-openid and heroku love story (multiple issues)
After getting my app working locally for quite a while, I pushed it to Heroku only to find that OpenID authentication was working "selectively" -- it didn't work for the largest OpenID providers (Google and Yahoo). This was intolerable, of course, and I started figuring the differences between here and there. One such difference was the storage used, so despite being sceptic about it, I decided to equalise and to introduce memcache (which is really the preferred option for what OpenID needs). Heroku provides two memcache client gems: memcached-northscale and dalli. First, I have to say that memcached-northwest really su... of a low quality, I think it's rather incompatible with openid (as an OpenID::Store::Memcache cache client). It throws a pre-built(! no stack trace !) exception (which Rack::ShowExceptions#pretty shamelessly fails on itself -- because of the absent stacktrace) during a get instead of returning nil value as the OpenID::Store::Memcache expects. Then, dalli is also currently incompatible with OpenID::Store::Memcache! See https://github.com/openid/ruby-openid/pull/9 -- figure the monkey patch in order (see right below). I created https://github.com/costa/rack-openid-test solely for debugging ( http://rack-openid-test.heroku.com/), but it didn't help me to finally detect the problem. I'm still not sure what the problem was, but I've found the root cause, it is some sort of SSL problem using the CA certificate file I provided: #https://www.google.com/accounts/o8/id : Error connecting to SSL URL https://www.google.com/accounts/o8/id: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed> Now that exception was hidden away in rack-openid ( https://github.com/josh/rack-openid/blob/master/lib/rack/openid.rb#L128) which reported a missing provider error. What makes this really weird is the very same file being used in the rack-openid-test above which is working flawlessly for some reason (see https://github.com/costa/rack-openid-test/blob/master/sinatra_example.rb#L15 ). After removing 'OpenID.fetcher.ca_file = ...' line from rails initializers I've started to get warnings just like I did locally before setting that cert file up: WARNING: making https request to https://www.google.com/accounts/o8/idwithout v erifying server certificate; no CA path was specified. But the authentication works... for now. I really hope a clue on this weird issue will come up and/or Heroku will update its docs on Rack::OpenID. -- 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: 1.9.2 Stack
Okay, I don't have a .gems but un Gemfile. And i have pg defined into it. Her is the content of my Gemfile; source 'http://rubygems.org' > > >> gem 'rails', '3.0.1' > > >> gem 'nokogiri' > > gem 'jquery-rails' > > gem 'haml' > > gem 'devise' > > gem 'omniauth' > > gem "friendly_id", "~> 3.1" > > >> gem 'sqlite3-ruby', :require => 'sqlite3' > > >> group :production do > > gem "pg" > > end > > >> group :development, :test do > > gem 'machinist', '>= 2.0.0.beta1' > > gem 'fakeweb' > > gem 'mocha' > > gem 'compass' > > end > > > The weird thing is that when I git push, the logs tell me that the stack changes from 1.8.7 to 1.9.2, but actually not. Weird! On Thu, Dec 30, 2010 at 6:15 PM, Scott LaBounty wrote: > Vince, > > OK, now I'm with you. I think what finally did it was to put "pg" in my > .gems file rather than "pg-ruby". If that doesn't work, let me know and I'll > look a bit more. > > Scott > > > On Thu, Dec 30, 2010 at 7:18 AM, Vincent Coste wrote: > >> Hi Scott, thanks for the faste answer. >> >> Actually, my question was more about what kind of code push did you do in >> order to migrate your stack? I have almost the same problem you had: >> >> git push heroku master >> >> Counting objects: 87, done. >> >> Delta compression using up to 2 threads. >> >> Compressing objects: 100% (48/48), done. >> >> Writing objects: 100% (50/50), 7.23 KiB, done. >> >> Total 50 (delta 31), reused 0 (delta 0) >> >> >>> -> Heroku receiving push >> >> -> Migrating from bamboo-ree-1.8.7 to bamboo-mri-1.9.2 >> >> >> [..] >> >> >> Your bundle is complete! It was installed into ./.bundle/gems >> >> -> Installing Exceptional plugin from git:// >> github.com/contrast/exceptional.git... done. >> >>Compiled slug size is 6.7MB >> >> -> Launching... done >> >>deployed to Heroku >> >> >> -> Migration complete, your app is now running on bamboo-mri-1.9.2 >> >> >> >> >> >> >> And on an heroku stack: >> >> heroku stack >> >> aspen-mri-1.8.6 >> >> * bamboo-ree-1.8.7 >> >> bamboo-mri-1.9.1 (beta) >> >> bamboo-mri-1.9.2 (beta) (prepared, will migrate on next git push) >> >> >> >> >> If i can't do it soon, i think i'm gonna recreate an app directly with the >> right stack. >> >> Regards, >> >> >> >> On Wed, Dec 29, 2010 at 8:06 PM, Scott LaBounty wrote: >> >>> Vince, >>> >>> Here's a post I did on Heroku and Sequel ... >>> >>> http://steamcode.blogspot.com/2010/09/sequel-and-heroku.html >>> >>> To push your database do: >>> >>> heroku db:push sqlite://mydatabase.sqlite >>> heroku restart >>> >>> Is this what you're looking for? If not, let me know and I'll see what >>> else I've got. Locally, I just use sqlite and then pretty much everything >>> works on Heroku with Postgres. >>> >>> Scott >>> >>> On Wed, Dec 29, 2010 at 5:26 AM, Vincent Coste >>> wrote: >>> Just to know, what did you push in order for heroku to migrate your stack? On Dec 13, 11:20 pm, Scott LaBounty wrote: > Thanks! That cleared up one problem anyway. It looks like I may have other > issues, but I'll try to work them out. > > Scott > > > > > > > > > > On Mon, Dec 13, 2010 at 2:00 PM, Robert Eanes wrote: > > You want the pg gem, not the ruby-pg gem, which looks like it hasn't been > > updated since 2008. I've used it locally and on heroku with 1.9.2 > > successfully. > > > On Dec 13, 2010, at 3:49 PM, Scott LaBounty wrote: > > > > OK, continuing on here. I just use sqlite locally for development and > > don't have postgres installed. I get the same error when I try to install it > > on my machine. Is the ruby-pg gem incompatible with ruby 1.9.2? If so, then > > how on earth does the 1.9.2 stack work for anything on Heroku? > > > > Scott > > > > On Mon, Dec 13, 2010 at 12:38 PM, Scott LaBounty < slabou...@gmail.com> > > wrote: > > > One more thought ... would it help to delete the app and then regenerate > > it with ruby 1.9.2 to start with? For the record, I'm using Ramaze and > > Sequel here, not Rails. > > > > Scott > > > > On Mon, Dec 13, 2010 at 10:49 AM, Scott LaBounty < slabou...@gmail.com> > > wrote: > > > OK, when I changed something and did a new push, I get ... > > > > << > > > -> Installing gem ruby-pg fromhttp://rubygems.org > > >Building native extensions. This could take a while... > > >ERROR: Error installing ruby-pg: > > >ERROR: Failed to build gem native extension. > > > >/usr/ruby1.9.2/bin/ruby extconf.rb > > >*** extconf.rb failed *** > > >Could not create Makefile due to some reason, probably lack of > > >necessary libraries and/or headers. Check the mkmf.log file for > > more > > >d
heroku db:push doesnt work
tried reinstall heroku and taps and nothing helped :( here what im getting: Sending schema c:/Ruby192/lib/ruby/gems/1.9.1/gems/sequel-3.17.0/lib/sequel/adapters/ sqlite.rb:5:in `rescue in ': SQLite3::Database#type_ translation is not defined. If you are using the sqlite3 gem, please install the sqlite3-ruby gem. (Sequel::Error) from c:/Ruby192/lib/ruby/gems/1.9.1/gems/sequel-3.17.0/lib/ sequel/adapters/sqlite.rb:2:in `' from :29:in `require' from :29:in `require' from c:/Ruby192/lib/ruby/gems/1.9.1/gems/sequel-3.17.0/lib/ sequel/core.rb:249:in `block in tsk_require' from c:/Ruby192/lib/ruby/gems/1.9.1/gems/sequel-3.17.0/lib/ sequel/core.rb:72:in `block in check_requiring_thread' from :10:in `synchronize' from c:/Ruby192/lib/ruby/gems/1.9.1/gems/sequel-3.17.0/lib/ sequel/core.rb:69:in `check_requiring_thread' from c:/Ruby192/lib/ruby/gems/1.9.1/gems/sequel-3.17.0/lib/ sequel/core.rb:249:in `tsk_require' from c:/Ruby192/lib/ruby/gems/1.9.1/gems/sequel-3.17.0/lib/ sequel/database/connecting.rb:25:in `adapter_class' from c:/Ruby192/lib/ruby/gems/1.9.1/gems/sequel-3.17.0/lib/ sequel/database/connecting.rb:54:in `connect' from c:/Ruby192/lib/ruby/gems/1.9.1/gems/sequel-3.17.0/lib/ sequel/core.rb:119:in `connect' from c:/Ruby192/lib/ruby/gems/1.9.1/gems/taps-0.3.14/lib/taps/ schema.rb:18:in `dump_table' from c:/Ruby192/lib/ruby/gems/1.9.1/gems/taps-0.3.14/bin/ schema:32:in `' p.s im using rails 3.0.3 (ruby 1.9.1) on windows (yes-yes windows with small 'w' ) -- 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: 1.9.2 Stack
Okay thank's a lot for your time Scott, I'll do that! On Thu, Dec 30, 2010 at 7:34 PM, Scott LaBounty wrote: > Vince, > > After looking a 2nd time at my history, it seems like I might have given up > on the migration to 1.9.2 and just gone with a recreation: > > heroku create --stack bamboo-mri-1.9.2 > > Scott > > > On Thu, Dec 30, 2010 at 9:57 AM, Vincent Coste wrote: > >> Okay, I don't have a .gems but un Gemfile. And i have pg defined into it. >> >> >> Her is the content of my Gemfile; >> >> source 'http://rubygems.org' >>> >>> gem 'rails', '3.0.1' >>> >>> gem 'nokogiri' >>> >>> gem 'jquery-rails' >>> >>> gem 'haml' >>> >>> gem 'devise' >>> >>> gem 'omniauth' >>> >>> gem "friendly_id", "~> 3.1" >>> >>> gem 'sqlite3-ruby', :require => 'sqlite3' >>> >>> group :production do >>> >>> gem "pg" >>> >>> end >>> >>> group :development, :test do >>> >>> gem 'machinist', '>= 2.0.0.beta1' >>> >>> gem 'fakeweb' >>> >>> gem 'mocha' >>> >>> gem 'compass' >>> >>> end >>> >>> >>> >> >> The weird thing is that when I git push, the logs tell me that the stack >> changes from 1.8.7 to 1.9.2, but actually not. >> >> Weird! >> >> >> >> On Thu, Dec 30, 2010 at 6:15 PM, Scott LaBounty wrote: >> >>> Vince, >>> >>> OK, now I'm with you. I think what finally did it was to put "pg" in my >>> .gems file rather than "pg-ruby". If that doesn't work, let me know and I'll >>> look a bit more. >>> >>> Scott >>> >>> >>> On Thu, Dec 30, 2010 at 7:18 AM, Vincent Coste >>> wrote: >>> Hi Scott, thanks for the faste answer. Actually, my question was more about what kind of code push did you do in order to migrate your stack? I have almost the same problem you had: git push heroku master Counting objects: 87, done. Delta compression using up to 2 threads. Compressing objects: 100% (48/48), done. Writing objects: 100% (50/50), 7.23 KiB, done. Total 50 (delta 31), reused 0 (delta 0) > -> Heroku receiving push -> Migrating from bamboo-ree-1.8.7 to bamboo-mri-1.9.2 [..] Your bundle is complete! It was installed into ./.bundle/gems -> Installing Exceptional plugin from git:// github.com/contrast/exceptional.git... done. Compiled slug size is 6.7MB -> Launching... done deployed to Heroku -> Migration complete, your app is now running on bamboo-mri-1.9.2 And on an heroku stack: heroku stack aspen-mri-1.8.6 * bamboo-ree-1.8.7 bamboo-mri-1.9.1 (beta) bamboo-mri-1.9.2 (beta) (prepared, will migrate on next git push) If i can't do it soon, i think i'm gonna recreate an app directly with the right stack. Regards, On Wed, Dec 29, 2010 at 8:06 PM, Scott LaBounty wrote: > Vince, > > Here's a post I did on Heroku and Sequel ... > > http://steamcode.blogspot.com/2010/09/sequel-and-heroku.html > > To push your database do: > > heroku db:push sqlite://mydatabase.sqlite > heroku restart > > Is this what you're looking for? If not, let me know and I'll see what > else I've got. Locally, I just use sqlite and then pretty much everything > works on Heroku with Postgres. > > Scott > > On Wed, Dec 29, 2010 at 5:26 AM, Vincent Coste < > coste.vinc...@gmail.com> wrote: > >> Just to know, what did you push in order for heroku to migrate your >> stack? >> >> On Dec 13, 11:20 pm, Scott LaBounty wrote: >> > Thanks! That cleared up one problem anyway. It looks like I may have >> other >> > issues, but I'll try to work them out. >> > >> > Scott >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > On Mon, Dec 13, 2010 at 2:00 PM, Robert Eanes >> wrote: >> > > You want the pg gem, not the ruby-pg gem, which looks like it >> hasn't been >> > > updated since 2008. I've used it locally and on heroku with 1.9.2 >> > > successfully. >> > >> > > On Dec 13, 2010, at 3:49 PM, Scott LaBounty wrote: >> > >> > > > OK, continuing on here. I just use sqlite locally for >> development and >> > > don't have postgres installed. I get the same error when I try to >> install it >> > > on my machine. Is the ruby-pg gem incompatible with ruby 1.9.2? If >> so, then >> > > how on earth does the 1.9.2 stack work for anything on Heroku? >> > >> > > > Scott >> > >> > > > On Mon, Dec 13, 2010 at 12:38 PM, Scott LaBounty < >> slabou...@gmail.com> >> > > wrote: >> > > > One more thought ... would it help to delete the app and then >> regenerate >> > > it with ruby 1.9.2 to start with? For the record, I'm using Ramaze >> and >> > >
Re: Some Heroku questions
For us, staging is basically the wild west - anything can go on it at any time -- HEAD, crazy experimental branches, etc. For production releases I branch and tag, and only the "production" branch goes to a live server. -k- On Thu, Dec 30, 2010 at 8:57 AM, Wes Gamble wrote: > To piggyback on this question - how do people handle staging vs. live? > Do you point at the same repo. but use different branches to deploy, or > something else? > > Wes > > On 12/30/10 7:35 AM, femto Zheng wrote: > > Yes, that's it, thanks for the info. > > > On Thu, Dec 30, 2010 at 8:17 PM, Steve Smith wrote: > >> I'm not sure I quite understand your question but if you are saying for >> example you have two heroku sites setup but they share the same repository >> (like staging and live) then you can specify --app as part of the heroku >> command line tool. >> >> Such as: >> >> $ heroku info --app cloudmailin >> >> >> On 30 Dec 2010, at 11:45, femto Zheng wrote: >> >> > Hello, I'm running into a situation, >> > while my live site is up and running in heroku, >> > some part I need to ask others to modify. >> > >> > so say, >> > I have myapp point to g...@heroku.com:myapp.git, >> > then I want to add a new app/repo to use as a collabor repo, >> > then say, >> > in my local myapp project, I git remote add >> g...@heroku.com:myapp-pre.git(which I created), >> > then I git push myapp-pre master, then use it as a collabor repository. >> > >> > The question is, then the several heroku commands, >> > like heroku console, heroku rake etc, how do they know to find >> > which repo/app to work with? That's an interesting question, >> > and I don't want to two environment mess up together. >> > >> > >> > -- >> > 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. >> >> > > > -- > http://hi.baidu.com/femto > http://bbs.aisiming.com/ > > -- > 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.
