exclusion of bundler gems (via group, :platforms, what else?)
I have to start things with `bundle exec` and put all the gems I use in the Gemfile. However some gems are incompatible with Heroku (those specifically for mac-osx) and make it impossible to deploy the app. It would be great if there is a way to exclude certain :development :test groups when pushing to Heroku. Those gems aren't used in production anyway. It would make the slugs leaner too. The platforms tag isn't helping either. There is no :platforms = :osx. The only workaround I see so far is to develop with :ruby_18 and deploy to :ruby_19. The 1.8 is still useful for capybara-envjs but 1.9 is obviously preferable... Orlin -- 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: exclusion of bundler gems (via group, :platforms, what else?)
Thanks Ben. Should have looked at the docs again. First time seeing this, I guess the exclusion feature is relatively new. -- 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.
thin error
I'm getting an error with http://astropi-staging.heroku.com/ - just reinstalled the rvm / gems, which means newer bundler (a couple of changes to .bundle). Otherwise everything is is just as before. It runs fine locally. Switched to the bamboo 1.8.7 stack. Did get the same error with argent aspen. Thin web server (v1.0.1 codename ?) Maximum connections set to 1024 Listening on 0.0.0.0:57444, CTRL+C to stop /usr/local/lib/ruby/gems/1.8/gems/thin-1.0.1/lib/thin/backends/ tcp_server.rb:16:in `connect': no such file to load -- thin/connection (MissingSourceFile) from /usr/local/lib/ruby/gems/1.8/gems/thin-1.0.1/lib/thin/backends/ base.rb:49:in `start' from /usr/local/lib/ruby/gems/1.8/gems/eventmachine-0.12.6/lib/ eventmachine.rb:240:in `call' from /usr/local/lib/ruby/gems/1.8/gems/eventmachine-0.12.6/lib/ eventmachine.rb:240:in `run_machine' from /usr/local/lib/ruby/gems/1.8/gems/eventmachine-0.12.6/lib/ eventmachine.rb:240:in `run' from /usr/local/lib/ruby/gems/1.8/gems/thin-1.0.1/lib/thin/backends/ base.rb:57:in `start' from /usr/local/lib/ruby/gems/1.8/gems/thin-1.0.1/lib/thin/server.rb: 150:in `start' from /usr/local/lib/ruby/gems/1.8/gems/thin-1.0.1/lib/thin/ controllers/controller.rb:80:in `start' from /usr/local/lib/ruby/gems/1.8/gems/thin-1.0.1/lib/thin/runner.rb: 173:in `send' from /usr/local/lib/ruby/gems/1.8/gems/thin-1.0.1/lib/thin/runner.rb: 173:in `run_command' from /usr/local/lib/ruby/gems/1.8/gems/thin-1.0.1/lib/thin/runner.rb: 139:in `run!' from /usr/local/lib/ruby/gems/1.8/gems/thin-1.0.1/bin/thin:6 from /usr/local/bin/thin:20:in `load' from /usr/local/bin/thin:20 -- 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: undo heroku deploy
Thanks guys. I guess it was an old topic, with these two links recycled from earlier posts: http://jqr.github.com/2009/04/25/deploying-multiple-environments-on-heroku.html http://suitmymind.com/blog/2009/06/02/deploying-multiple-environments-on-heroku-while-still-hosting-code-on-github/ I would have identical environments down to the RACK_ENV=production for both. Rake is the way to go. Thanks for the gist. I would still deploy from a branch instead of a tag. Here is an example: $ git push staging deploy:master $ git push production deploy:master Tagging only after production has tested ok too. Also, I like http://semver.org/ better than tagging with dates. Versions incremented, possibly with http://github.com/dazuma/versionomy -- 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: require 'bundled-gem' -- no such file to load
It did work. Noticing significant speed increase compared to the previous .gem installs. Congratulations thanks. On Feb 19, 8:09 pm, Pedro Belo pe...@heroku.com wrote: We fixed an issue with bundler earlier this week. Push a change o your Gemfile and it should work. On Fri, Feb 19, 2010 at 2:22 AM, orlin orlin.mo...@gmail.com wrote: Something I noticed is when I run $ bundle show and when no gems other than bundler are installed (clean rvm) - nokogiri is the first to be found missing Could not find gem 'nokogiri (= 1.4.1, runtime)' in any of the sources.. It's not the first (very far down in the Gemfile), and otherwise, both bundle install and bundle show install / list the gems in alphabetical order. So it could be that the dyno can't find its installed gems (or that the gems aren't actually installed)... On Feb 17, 7:08 pm, Matthew A. Brown mat.a.br...@gmail.com wrote: I'm having the same problem with Nokogiri. On Wed, Feb 17, 2010 at 12:07, orlin orlin.mo...@gmail.com wrote: Toadhopper doesn't find Nokogiri, after upgrading to the latest Bundler. The gem is bundled, and locked, and Heroku says: Installing nokogiri (1.4.1) from rubygems repository athttp://gemcutter.orgwith native extensions upon push. I deployed herehttp://freezing-sunset-88.heroku.com/-a temp app to illustrate the issue. Orlin -- 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 athttp://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 athttp://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: require 'bundled-gem' -- no such file to load
Something I noticed is when I run $ bundle show and when no gems other than bundler are installed (clean rvm) - nokogiri is the first to be found missing Could not find gem 'nokogiri (= 1.4.1, runtime)' in any of the sources.. It's not the first (very far down in the Gemfile), and otherwise, both bundle install and bundle show install / list the gems in alphabetical order. So it could be that the dyno can't find its installed gems (or that the gems aren't actually installed)... On Feb 17, 7:08 pm, Matthew A. Brown mat.a.br...@gmail.com wrote: I'm having the same problem with Nokogiri. On Wed, Feb 17, 2010 at 12:07, orlin orlin.mo...@gmail.com wrote: Toadhopper doesn't find Nokogiri, after upgrading to the latest Bundler. The gem is bundled, and locked, and Heroku says: Installing nokogiri (1.4.1) from rubygems repository athttp://gemcutter.orgwith native extensions upon push. I deployed herehttp://freezing-sunset-88.heroku.com/- a temp app to illustrate the issue. Orlin -- 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 athttp://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.
undo heroku deploy
What is the recommended way to undo a bad heroku deploy? I push something that causes App failed to start error. Afaik, the fastest way to fix that would be: git push heroku mybranch:master --force Is there a way for git to push a commit instead of a branch? Otherwise It seems better to deploy from call it a deploy branch and then merge changes into master if they deploy cleanly. Also, there seems to be a bug with the .gems to bundler transition. The .gems manifest gems were uninstalled after switching to Bundler. But Bundler introduced an error (in my case, require fails for one of the gems)... Having to rollback to a running app (maintenance mode doesn't fix such errors), I force-push older code. But, since the .gems manifest is the same, all the gems turn out missing. Now I have to push a fake commit that modifies the .gems file (so that it gets detected thus the gems get reinstalled). Perhaps an explicit heroku gems reinstall command I haven't spotted? On a separate note, why would heroku deploy an app - if every single page produces an App failed to start error? Luckily, my site is basically unknown at this point, but I would eventually need a solid deployment process... Any *best practice* pages out there? Regards, Orlin -- 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.
require 'bundled-gem' -- no such file to load
Toadhopper doesn't find Nokogiri, after upgrading to the latest Bundler. The gem is bundled, and locked, and Heroku says: Installing nokogiri (1.4.1) from rubygems repository at http://gemcutter.org with native extensions upon push. I deployed here http://freezing-sunset-88.heroku.com/ - a temp app to illustrate the issue. Orlin -- 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.
multiple custom domains + wildcards for each?
If one app has a couple of custom domain names set, and has wildcards enabled, can I have wildcards turned on just for one of those? Also, can I have different sets of wildcard sub-domain names for each custom domain? Orlin --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
several rack / sinatra apps - making a single heroku app
How would you go about combining several Sinatra apps to run as a single Heroku app? I want to run a whole bunch of apps like: Hancock, CloudKit, WebGlue, Watercoolr, etc. Upgrading each one individually (beyond development) would be too much for my budget. I think there was some recent Rack project that can do such combining at runtime. Not sure if applicable to your environment... Perhaps it's a source- level git trick that does it? What would you recommend? Orlin --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
vendored rack on herokugarden
Heroku is great, but garden is useful for collaborating with people who don't have rails installed. For example I want to ask a designer to tweak some css styles and then pull the changes from herokugarden. I have to use rails 2.3 which I vendored. It seems to need newer rack, so I vendored 1.0.0 too. Now I'm up against: /usr/local/lib/site_ruby/1.8/rubygems.rb:149:in `activate': can't activate rack (~ 1.0.0, runtime), already activated rack-0.4.0 (Gem::Exception) Is there a way to get around this? It seems like you have disabled the custom gem install, or am I forgetting where that was? I will run my apps on Heroku. It's just that for certain types of collaboration - Heroku Garden is still better. Just because of its online interface, of-course. Thanks, Orlin --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
