can't activate activesupport Error message after including gem in .gem file
After including the gem in my .gem file, the application is unable to run. It runs perfectly on my localhost - so i wonder why the conflict is happening? There appears to be some problems with the rails runtime - would love to get some help here! /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems.rb:230:in `activate': can't activate activesupport (= 2.3.8, runtime) for [feedzirra-0.0.24], already activated activesupport-2.3.5 for [rails-2.3.5] (Gem::LoadError -- 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: How to deploy app with sensitive config information?
Dmytri, Check out the heroku documentation on config vars, I think that's what you're looking for. http://docs.heroku.com/config-vars http://docs.heroku.com/config-vars- Ed On Wed, Sep 1, 2010 at 10:38 AM, dnagir dna...@gmail.com wrote: Hi, Deployment to Heroku is done as a Git push. For git I configure my app not to include any sensitive information so it will not appear anywhere. This includes email, payment gateway credentials, encryption key, etc. So how would I deploy that information together with the application without storing it in git? Cheers, Dmytrii. -- 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. -- Ed Schmalzle @nerdEd http://www.EdSchmalzle.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.
Re: Calling all forks
If you don't mind using Resque instead of Delayed:Job for your workers, take a look at this blog post. http://blog.darkhax.com/2010/07/30/auto-scale-your-resque-workers-on-heroku That should be just about all you need to spin up your workers up and down as needed. On Aug 31, 10:50 pm, Gabriel ummo...@gmail.com wrote: This seems to be a somewhat common use case for Heroku: I have a process that takes far too long to tie up a web request but doesn't happen often enough to warrant paying for a Worker. Right now I'm considering calling fork to handle this situation and I have two questions: 1. Will this work on Heroku? That is: are there any specifics about the Heroku architecture that would prevent forks? 2. Is there a better way that doesn't involve having a Worker running all the time? I've seen people mention that Workers can be spun up and deleted programmatically but I've yet to see what the API for doing so looks like. Thanks, Gabriel -- 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.
Connecting to 2nd database... `establish_connection': xxx database is not configured (ActiveRecord::AdapterNotSpecified)
Trying to get our app up and running on Heroku and am having some issues with the models that connect to a 2nd remote database. I get the error: :in `establish_connection': wawd database is not configured (ActiveRecord::AdapterNotSpecified) The database is configured in database.yml and currently works outside of heroku in a production setting xxx: adapter: mysql database: username: password: host: x And the models include: establish_connection :xxx Is this not a valid way of connecting to a database on Heroku? Should it be configured differently? Thanks... -timw -- 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: Calling all forks
Try out this fork of Delayed Job: http://github.com/pedro/delayed_job I've been using it for a week or two now, and it works beautifully. On Sep 2, 2010, at 12:40 PM, chris wrote: 2. Is there a better way that doesn't involve having a Worker running all the time? I've seen people mention that Workers can be spun up and deleted programmatically but I've yet to see what the API for doing so looks like. -- 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.
What is the equivalent of cap deploy:migrations in Heroku?
I've been a heavy user of Capistrano before switching to Heroku and my typical workflow with database migrations is that I try to keep them backwards compatible and then do my deploy with cap deploy:migrations. That command will do a rake db:migrate before the deploy and abort the deploy if there are errors. Heroku doesn't seem to have anyting like deploy:migrations and the problem with running heroku rake db:migrate after the deploy is that that leaves a time window where I am receiving requests with the new code which is not compatible with the old schema. The only workaround here I can think of is to push the migrations first, then db:migrate, then push the code. That seems very awkward and far from the Heroku philosophy and I'm not even sure how to set that up with Git. Any suggestions? Thanks for an awesome service! Peter -- 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.
HTML server side includes
Do you guys know if theres any way to enable HTML server side includes? Thanks! -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: What is the equivalent of cap deploy:migrations in Heroku?
This isn't the best option, but you can put your app in maintenance mode during the deploy/migrations and then put it back in service. It makes continuous deployment a bit of a problem, but if you can deploy during low traffic periods it would probably be ok. Mike On Tue, Sep 7, 2010 at 12:21 AM, Peter Marklund peter_markl...@fastmail.fm wrote: I've been a heavy user of Capistrano before switching to Heroku and my typical workflow with database migrations is that I try to keep them backwards compatible and then do my deploy with cap deploy:migrations. That command will do a rake db:migrate before the deploy and abort the deploy if there are errors. Heroku doesn't seem to have anyting like deploy:migrations and the problem with running heroku rake db:migrate after the deploy is that that leaves a time window where I am receiving requests with the new code which is not compatible with the old schema. The only workaround here I can think of is to push the migrations first, then db:migrate, then push the code. That seems very awkward and far from the Heroku philosophy and I'm not even sure how to set that up with Git. Any suggestions? Thanks for an awesome service! Peter -- 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: What is the equivalent of cap deploy:migrations in Heroku?
That's the best solution I know of generally if you have migrations that break the previous install; however, many migrations (such as creating tables/columns) are backward-compatible and thus can be run while the app is still running under the older version of the code. This allows you to avoid any downtime at all, which is of course far preferable to downtime. Peter, your proposed solution is (unfortunately) the best I can think of given Heroku's current capabilities; it might be possible to at least automate it, though, by doing a little git-fu: - Check out a temporary local branch based on the head of the Heroku remote - Do a diff between your new temporary branch and your deployment branch, only on the db/migrate directory. - Apply that diff as a patch to your temporary branch. - Push your temporary branch to Heroku. This will keep your application running in its current codebase, but with new migrations. - Run heroku rake db:migrate - Merge your temporary branch back into your deployment branch. This merge won't have any actual effect on your deployment branch's working copy, but you need to do this to keep the revision history consistent. - Push your deployment branch to heroku. I've never tried this and YMMV but that's how I'd tackle it. I think a simple way for Heroku to support a less painful way of doing this would be to give you control over whether the app automatically restarts after a push -- maybe based on a config var. Then it'd just be -- turn off auto-restart, push, rake db:migrate, restart, turn on auto-restart. Not sure how easy that'd be to deliver with Heroku's cloud internals though. Mat On Tue, Sep 7, 2010 at 14:13, Mike Abner mike.ab...@gmail.com wrote: This isn't the best option, but you can put your app in maintenance mode during the deploy/migrations and then put it back in service. It makes continuous deployment a bit of a problem, but if you can deploy during low traffic periods it would probably be ok. Mike On Tue, Sep 7, 2010 at 12:21 AM, Peter Marklund peter_markl...@fastmail.fm wrote: I've been a heavy user of Capistrano before switching to Heroku and my typical workflow with database migrations is that I try to keep them backwards compatible and then do my deploy with cap deploy:migrations. That command will do a rake db:migrate before the deploy and abort the deploy if there are errors. Heroku doesn't seem to have anyting like deploy:migrations and the problem with running heroku rake db:migrate after the deploy is that that leaves a time window where I am receiving requests with the new code which is not compatible with the old schema. The only workaround here I can think of is to push the migrations first, then db:migrate, then push the code. That seems very awkward and far from the Heroku philosophy and I'm not even sure how to set that up with Git. Any suggestions? Thanks for an awesome service! Peter -- 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.
When I deploy to heroku, I get a complaint about Rubygems 1.3.7 not being available
I just tried to do a deploy, and got the following message: Installing gem liquid = 0 from http://rubygems.org ERROR: Error installing liquid: liquid requires RubyGems version = 1.3.7. Try 'gem update -- system' to update RubyGems itself. I am on the bamboo-ree-1.8.7 Is RubyGems 1.3.7 really not available? Or is something else wrong? Many thanks, Wes Gamble -- 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.
Issues sending email from a Heroku app?
Hi- I'm developing a Rails app that operates from a VPS and have run into problems with my emails to users getting sent to the junk folder, or worse, not getting seen at all. I've spent many fruitless hours pouring over the email acceptance procedures for Yahoo and Hotmail, for example, in an attempt to craft the most compliant emails possible. No luck. Would I get any relief from these problems if I switched to Heroku? I've learned a tremendous amount administering my own slice, but it's hard to be an expert in everything. I'm guessing that since the Heroku servers must be a 'known quantity', it would be smoother sailing for my app-generated emails. But then again, what do I know? I'd be grateful for any insight on this. Thanks. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: can't activate activesupport Error message after including gem in .gem file
Hi Ming Yeow - Think it's because feedzirra has a dependency on activesupport 2.3.8 whereas Rails 2.3.5 is tied to activesupport 2.3.5 . Can you see if you adding --ignore-dependencies to the feedzirra line in your .gems file solves the problem? Here's some docs for a similar problem: http://docs.heroku.com/rails236 Cheers, Arun On Sun, Sep 5, 2010 at 6:36 AM, Ming Yeow Ng mingy...@gmail.com wrote: After including the gem in my .gem file, the application is unable to run. It runs perfectly on my localhost - so i wonder why the conflict is happening? There appears to be some problems with the rails runtime - would love to get some help here! /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems.rb:230:in `activate': can't activate activesupport (= 2.3.8, runtime) for [feedzirra-0.0.24], already activated activesupport-2.3.5 for [rails-2.3.5] (Gem::LoadError -- 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. -- It's better to be a pirate than join the Navy - Steve Jobs http://mclov.in | @iamclovin -- 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: Issues sending email from a Heroku app?
heroku don't actually do email now. but, you can try out the sendgrid plugin. i have really good experience with it now. correct me if i am wrong. : ) On Tue, Sep 7, 2010 at 3:41 PM, nimzo bushbr...@gmail.com wrote: Hi- I'm developing a Rails app that operates from a VPS and have run into problems with my emails to users getting sent to the junk folder, or worse, not getting seen at all. I've spent many fruitless hours pouring over the email acceptance procedures for Yahoo and Hotmail, for example, in an attempt to craft the most compliant emails possible. No luck. Would I get any relief from these problems if I switched to Heroku? I've learned a tremendous amount administering my own slice, but it's hard to be an expert in everything. I'm guessing that since the Heroku servers must be a 'known quantity', it would be smoother sailing for my app-generated emails. But then again, what do I know? I'd be grateful for any insight on this. Thanks. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.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.
