Re: You have modified your Gemfile in development but did not check the resulting snapshot (Gemfile.lock) into version control
thank you so much :) i had no idea you could do this and it works perfectly! On Oct 12, 5:44 am, Chris Hanks christopher.m.ha...@gmail.com wrote: First, to prevent Heroku from installing certain gems, use the BUNDLE_WITHOUT config var to specify groups you want to skip. For example, I do: heroku config:add BUNDLE_WITHOUT=development test Then, in my Gemfile: source :rubygems gem 'rails', '3.0.0' group :development, :test do gem 'rspec-rails', '2.0.0' # etc... end Now Heroku won't install any of the rspec gems. Second, try running bundle update after updating a gem in the Gemfile, and it will recalculate all your dependencies and update your Gemfile.lock for you. What's even better, though, is to only update gems you specify - for example, run bundle update rails if you change the rails version in your Gemfile. That way, Bundler will only update the things it really needs to, which is safer. On Oct 11, 9:09 pm, stephen murdoch stephenjamesmurd...@gmail.com wrote: I get this error message every now and then: You have modified your Gemfile in development but did not check the resulting snapshot (Gemfile.lock) into version control Most people suggest removing the .bundle directory and running bundle install again making sure to add Gemfile.lock to the git repo before committing and pushing to heroku but that doesn't always resolve the problem. The easiest way to fix this is by removing Gemfile.lock and pushing to heroku without it. Heroku then bundles your gems for you, but informs you that you will soon be required to include a Gemfile.lock. I am trying to get my head round this problem. Can anyone tell my why this happens? I have on occasions tried wrapping certain gems in my Gemfile within and 'if statement' to prevent heroku from installing them as I only want them on my dev box. The error only seems to happen in apps that I've used this technique. Perhaps this is the source of these problems? When will Heroku start requiring you to add a Gemfile.lock and what are the best ways of preventing this 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.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Compiled Slug size not changing after removing large gems from Gemfile
yes Keenan, it's definitely my slug size that's creeping up (same problem others are having) I did some digging and this is what I found: According to the command-line output, my bundle is getting installed to `.bundle/gems`. I decided to try and vendor my gems to see if this would make a difference. Firstly, I downloaded the source for the compass gem and stuck in my vendor/gems directory. Then in Gemfile I pointed to the vendored version like so: gem 'compass', :path = File.join(File.dirname(__FILE__), '/vendor/ gems/compass') I ran bundler again and pushed to heroku and watched the gem install and the slug increase in size. Then I removed the gem from my vendor directory, bundled and pushed to heroku again, and this time, the slug size decreased! So a possible fix for this problem might be to just vendor all gems until it's sorted out. Can't say that i've tested this out thoroughly but will give it a shot tonight when I have time just to be certain. On Oct 12, 7:52 am, Keenan Brock kee...@thebrocks.net wrote: Hi Stephen, If you checked in a gem into git Then you deleted the gem from git. Git still has the gem. It is not showing up for today, but git log will show when you added it and removed it. Guess I do not know if you are checking in your bundle dir and gems into git. 1. So are you saying your repo is 17mb, or your slug is 17mb? I'd imagine that the slug would be smaller on your change to the Gemfile. But you stating that your slug is big suggests that maybe the .git directory is included in the slug? The slug size does affect the speed in which a dyno is started / compiles / restarts. But I agree with Chris, I can't imagine it would slow it down too much. --Keenan On Oct 12, 2010, at 12:48 AM, Chris Hanks wrote: Yeah, this has happened to me before, too. I'm pretty sure the problem is on Heroku's end. I don't worry that much about it, though, since the max slug size is 100 MB. On Oct 11, 8:57 pm, stephen murdoch stephenjamesmurd...@gmail.com wrote: I have encountered a few strange problems with Heroku this evening. My repo size somehow managed to bloat to 17mb so I removed some gems from my Gemfile (ran bundle install, git add Gemfile.lock etc etc) and found that my repo was still 17mb. I removed all my gems (apart from rails and pg) and the repo didn't get any smaller. My app is no bigger than 2mb. So I deleted my app (along with my .git and .bundle directories) and created everything from scratch. This seemed to fix the problem, until just now, when I tried to remove 4 large gems from my Gemfile and didn't see any change in the size of my compiled slug on Heroku. Is this something that other people are experiencing? FWIW, I've tried everything I can think of, including removing Gemfile.lock, .bundle etc etc -- 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.
Compiled Slug size not changing after removing large gems from Gemfile
I have encountered a few strange problems with Heroku this evening. My repo size somehow managed to bloat to 17mb so I removed some gems from my Gemfile (ran bundle install, git add Gemfile.lock etc etc) and found that my repo was still 17mb. I removed all my gems (apart from rails and pg) and the repo didn't get any smaller. My app is no bigger than 2mb. So I deleted my app (along with my .git and .bundle directories) and created everything from scratch. This seemed to fix the problem, until just now, when I tried to remove 4 large gems from my Gemfile and didn't see any change in the size of my compiled slug on Heroku. Is this something that other people are experiencing? FWIW, I've tried everything I can think of, including removing Gemfile.lock, .bundle etc etc -- 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 have modified your Gemfile in development but did not check the resulting snapshot (Gemfile.lock) into version control
I get this error message every now and then: You have modified your Gemfile in development but did not check the resulting snapshot (Gemfile.lock) into version control Most people suggest removing the .bundle directory and running bundle install again making sure to add Gemfile.lock to the git repo before committing and pushing to heroku but that doesn't always resolve the problem. The easiest way to fix this is by removing Gemfile.lock and pushing to heroku without it. Heroku then bundles your gems for you, but informs you that you will soon be required to include a Gemfile.lock. I am trying to get my head round this problem. Can anyone tell my why this happens? I have on occasions tried wrapping certain gems in my Gemfile within and 'if statement' to prevent heroku from installing them as I only want them on my dev box. The error only seems to happen in apps that I've used this technique. Perhaps this is the source of these problems? When will Heroku start requiring you to add a Gemfile.lock and what are the best ways of preventing this 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.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Compiled Slug size not changing after removing large gems from Gemfile
PS - I'm using heroku gem 1.10.14 Also, when this problem occurs, the gems that I remove from my Gemfile do not get installed on heroku, but the slug size indicates that they are still lurking around somewhere in the background - is there anyway to list all the gems that my slug has installed? Is there any way to force heroku to purge the deleted gems? On Oct 12, 4:57 am, stephen murdoch stephenjamesmurd...@gmail.com wrote: I have encountered a few strange problems with Heroku this evening. My repo size somehow managed to bloat to 17mb so I removed some gems from my Gemfile (ran bundle install, git add Gemfile.lock etc etc) and found that my repo was still 17mb. I removed all my gems (apart from rails and pg) and the repo didn't get any smaller. My app is no bigger than 2mb. So I deleted my app (along with my .git and .bundle directories) and created everything from scratch. This seemed to fix the problem, until just now, when I tried to remove 4 large gems from my Gemfile and didn't see any change in the size of my compiled slug on Heroku. Is this something that other people are experiencing? FWIW, I've tried everything I can think of, including removing Gemfile.lock, .bundle etc etc -- 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: quick question about heroku versus herokugarden
Hi Thanks a lot for the quick reply and the advice. Real helpful, cheers Steve On Feb 22, 3:06 am, Keenan Brock kee...@thebrocks.net wrote: Hi Stephen, To turn off the banner: Create config/heroku.yml toolbar_public: false toolbar_collaborators: false I'm pretty sure you don't need to put a link to heroku. Rember it mentioned, but I put some not on the about page. (People tend to do that with non-free sites too for some reason) I think the reason you were auto moved is because the old heroku became herokugarden, and heroku is now their v2 product. I don't think it will auto move you to herokugarden. I don't know when it will cost money. --Keenan On Feb 21, 2009, at 9:15 PM, stephen murdoch wrote: Hi I had a few test apps running on heroku a while back and had forgotten about them until I got an email informing me that they had been moved to herokugarden - fine with me I don't mind Then today, I set up a new app on heroku (not herokugarden) and was wondering if this app will get moved by some daemon to herokugarden at any point It's not going to be a problem, I was just wondering Also, I notice that if you create a custom domain name for an app on Herokugarden, the page will have a pervasive heroku banner link at the bottom whilst custom domain names hosted on Heroku do not. Whilst I understand why you do that (you are giving free hosting and nothing's really free right?) what can we do in the event that it clashes with the site colour scheme? Lets say I had a bright pink background or flourescent green etc... As a suggestion I recommend the following: 1) allow users to alter the colours of the Heroku banner bar at the bottom of the page (perhaps have a set of banners from which they can choose, even allow people to develop their own within strict guidelines using some custom banner generator tool) - this solves the problem of my page background clashing with your banner 2) or, make a requirement that every page of every site must contain a visisble link to herokugarden along with some buttkissing statement about how much they love heroku, instead of having to have the banner. a bot or perhaps a rails test could verify that the visible link is displayed and could be set up to lock the site down if the user removed it just thinking so my questions are: 1) will my app on heroku be moved to herokugarden suddenly one day? 2) in the event that my app on heroku is not going to be moved to herokugarden, how long do I have before it ceases to be hosted for free? finally, I have a podcast that I want to host, I was thinking about using dreamhost as I've got other apps running there but now that I've spent the last 12 hours immersing myself in the ways heroku, dreamhost seems like a total PITA. the best solution is probably going to be the heroku commercial option you guys have planned, can you give me any info about what to expect for pricing? also do you have any idea what will happen in the event that my users should exceed my download limit? will I get fined or will my app just stop running until the next month? --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
quick question about heroku versus herokugarden
Hi I had a few test apps running on heroku a while back and had forgotten about them until I got an email informing me that they had been moved to herokugarden - fine with me I don't mind Then today, I set up a new app on heroku (not herokugarden) and was wondering if this app will get moved by some daemon to herokugarden at any point It's not going to be a problem, I was just wondering Also, I notice that if you create a custom domain name for an app on Herokugarden, the page will have a pervasive heroku banner link at the bottom whilst custom domain names hosted on Heroku do not. Whilst I understand why you do that (you are giving free hosting and nothing's really free right?) what can we do in the event that it clashes with the site colour scheme? Lets say I had a bright pink background or flourescent green etc... As a suggestion I recommend the following: 1) allow users to alter the colours of the Heroku banner bar at the bottom of the page (perhaps have a set of banners from which they can choose, even allow people to develop their own within strict guidelines using some custom banner generator tool) - this solves the problem of my page background clashing with your banner 2) or, make a requirement that every page of every site must contain a visisble link to herokugarden along with some buttkissing statement about how much they love heroku, instead of having to have the banner. a bot or perhaps a rails test could verify that the visible link is displayed and could be set up to lock the site down if the user removed it just thinking so my questions are: 1) will my app on heroku be moved to herokugarden suddenly one day? 2) in the event that my app on heroku is not going to be moved to herokugarden, how long do I have before it ceases to be hosted for free? finally, I have a podcast that I want to host, I was thinking about using dreamhost as I've got other apps running there but now that I've spent the last 12 hours immersing myself in the ways heroku, dreamhost seems like a total PITA. the best solution is probably going to be the heroku commercial option you guys have planned, can you give me any info about what to expect for pricing? also do you have any idea what will happen in the event that my users should exceed my download limit? will I get fined or will my app just stop running until the next month? ok, thanks for the lovely app, heroku really is excellent --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
