Re: Newrelic Bronze and Heroku
Many hosting providers have figured out it is cheaper for them to run efficient websites than inefficient ones. Engine yard gives away rpm as well. Or at least they did. I'm pretty sure bronze is 100% free --Keenan On Jun 11, 2010, at 3:52 PM, Amiruddin Nagri wrote: Heroku is offering Newrelic bronze integration for free, whereas the Newrelic site have a subscription fee for bronze version. How is this possible ? Is there a hidden cost that I am missing out ? Will I be charged under any circumstances either from Heroku or Newrelic for using this free bronze integration. Regards, Amiruddin Nagri, Bangalore, 560008, KA India Y! IM : amir_na...@yahoo.com GTalk : amir.na...@gmail.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.
Re: Rails 3 now 187 or 192 only
I'm sorry Oren, did you just imply Rails 3 beta's on MRI 191 make stable platforms for commercial deployments? :) Just giving you a hard time, but seriously now: an understandable position and I'd have been damn surprised if there were plans to make a 192 stack for early testing, never hurts to ask though. FWIW: someday, assuming it were even feasible, it'd be nice to have Heroku images (AMI, VMWare, whatever,) we could use and tweak locally for development when we get ahead of where it makes sense for Heroku to spend time/money. Given your IP in there, I'd also be pretty surprised if this were feasible, just a thought. And now to figure out how to deal with this debacle (rails I mean, not Heroku) hopefully only for the next several months while we see just how behind schedule 192 can finally be. On 11 Jun., 16:05, Oren Teich wrote: > We won't be supporting 1.9.2head before 1.9.2 is officially released. We > work hard to provide a stable platform for commercial deployment, and 1.9.2 > isn't there yet. > > We are investigating updating 1.8.7 to the latest REE patch level to address > the crashing 1.8.7 issue. > > Oren > > > > On Fri, Jun 11, 2010 at 2:27 PM, Yuri wrote: > > After beta4, i.e., master for now, starting up with MRI 191 gets you > > this stick in the eye: > > > Rails 3 requires Ruby 1.8.7 or 1.9.2. > > > You're running 1.9.1 (2010-01-10); please upgrade to continue. > > > And beta4 itself is pretty much a non-starter for 191 due to a 191- > > incompatible fix for multibyte chars, which ironically looks to be > > fixed in a compatible way for 191 in master now. But still, there it > > is. > > > Any thoughts from Heroku on their beta Rails 3 / 191 option, i.e., > > possibility of 192 previews (realizing that's gotta be a pain to > > handle on your end, but then the whole 1.9 cycle seems to be about > > maximizing pain for all concerned.) > > > -- > > 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: Rails 3 now 187 or 192 only
We won't be supporting 1.9.2head before 1.9.2 is officially released.We work hard to provide a stable platform for commercial deployment, and 1.9.2 isn't there yet. We are investigating updating 1.8.7 to the latest REE patch level to address the crashing 1.8.7 issue. Oren On Fri, Jun 11, 2010 at 2:27 PM, Yuri wrote: > After beta4, i.e., master for now, starting up with MRI 191 gets you > this stick in the eye: > >Rails 3 requires Ruby 1.8.7 or 1.9.2. > >You're running 1.9.1 (2010-01-10); please upgrade to continue. > > And beta4 itself is pretty much a non-starter for 191 due to a 191- > incompatible fix for multibyte chars, which ironically looks to be > fixed in a compatible way for 191 in master now. But still, there it > is. > > Any thoughts from Heroku on their beta Rails 3 / 191 option, i.e., > possibility of 192 previews (realizing that's gotta be a pain to > handle on your end, but then the whole 1.9 cycle seems to be about > maximizing pain for all concerned.) > > -- > 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: Rails 3 now 187 or 192 only
A big +1 on the 1.9.2 front, again acknowledging the obnoxiousness of relying on a non-stable Ruby. On Fri, Jun 11, 2010 at 5:27 PM, Yuri wrote: > After beta4, i.e., master for now, starting up with MRI 191 gets you > this stick in the eye: > >Rails 3 requires Ruby 1.8.7 or 1.9.2. > >You're running 1.9.1 (2010-01-10); please upgrade to continue. > > And beta4 itself is pretty much a non-starter for 191 due to a 191- > incompatible fix for multibyte chars, which ironically looks to be > fixed in a compatible way for 191 in master now. But still, there it > is. > > Any thoughts from Heroku on their beta Rails 3 / 191 option, i.e., > possibility of 192 previews (realizing that's gotta be a pain to > handle on your end, but then the whole 1.9 cycle seems to be about > maximizing pain for all concerned.) > > -- > 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.
Rails 3 now 187 or 192 only
After beta4, i.e., master for now, starting up with MRI 191 gets you this stick in the eye: Rails 3 requires Ruby 1.8.7 or 1.9.2. You're running 1.9.1 (2010-01-10); please upgrade to continue. And beta4 itself is pretty much a non-starter for 191 due to a 191- incompatible fix for multibyte chars, which ironically looks to be fixed in a compatible way for 191 in master now. But still, there it is. Any thoughts from Heroku on their beta Rails 3 / 191 option, i.e., possibility of 192 previews (realizing that's gotta be a pain to handle on your end, but then the whole 1.9 cycle seems to be about maximizing pain for all concerned.) -- 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.
Newrelic Bronze and Heroku
Heroku is offering Newrelic bronze integration for free, whereas the Newrelic site have a subscription fee for bronze version. How is this possible ? Is there a hidden cost that I am missing out ? Will I be charged under any circumstances either from Heroku or Newrelic for using this free bronze integration. Regards, Amiruddin Nagri, Bangalore, 560008, KA India Y! IM : amir_na...@yahoo.com GTalk : amir.na...@gmail.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: libraptor binary
I believe that 1.4.17 was the standard package for our Debian version, so we'd prefer to stick with that version. If it doesn't work or requires a lot of hoops we can look into alternatives. On Fri, Jun 11, 2010 at 8:48 AM, Arto Bendiken wrote: > Hi Matt, > > On Jun 11, 2:28 am, Matthew Soldo wrote: > > Hi RDF fans, > > > > We now have libraptor on our bamboo stack! > > > > Bamboo is not the default Heroku stack. If you aren't familiar with > Heroku > > stacks you should read up on them here. > > > > To create a new app with Bamboo, use the following command: > > > > heroku create --stack bamboo-ree-1.8.7 > > > > To switch an existing app to bamboo: > > > > heroku stack:migrate bamboo-ree-1.8.7 > > > > Let me know how it goes. > > > > - Matt > > Just testing this out now... for anyone who wants to play with this, > make sure that you have both the `rdf-raptor` and `ffi` gems specified > in your Heroku application's .gems file or Gemfile, and then > explicitly switch RDF::Raptor over to using FFI mode by setting an > environment variable as follows: > >$ heroku config:add RDF_RAPTOR_ENGINE=ffi --app myapp > > (CLI mode is still the default in the current RDF::Raptor release. > This will be changed to auto-detection of FFI vis-a-vis CLI mode in > the next release.) > > Unfortunately, at the moment I'm running into this problem: > >/home/slugs/.../.gems/gems/ffi-0.6.3/lib/ffi/library.rb:113:in > `attach_function': Function 'raptor_new_world' not found in > [libraptor.so] (FFI::NotFoundError) > > It looks like RDF::Raptor's FFI mode is currently relying on a > `raptor_new_world` function which was only introduced as of libraptor > 1.4.19: > >http://librdf.org/raptor/RELEASE.html#rel1_4_19 > > Matt, I'm assuming you had to deploy the older libraptor version > 1.4.17 because of platform constraints (an "enterprise" Linux distro > or the like), making an upgrade infeasible, so we'll try and work > around this on our end in the next RDF::Raptor release. Shouldn't be > too difficult to fix, I think. > > I'll keep you posted. > > -- > Arto Bendiken | http://datagraph.org/ > > -- > 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. > > -- Matthew Soldo Heroku, Inc (415) 323-0003 http://www.linkedin.com/in/mattsoldo @mattsoldo -- 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: libraptor binary
Hi Matt, On Jun 11, 2:28 am, Matthew Soldo wrote: > Hi RDF fans, > > We now have libraptor on our bamboo stack! > > Bamboo is not the default Heroku stack. If you aren't familiar with Heroku > stacks you should read up on them here. > > To create a new app with Bamboo, use the following command: > > heroku create --stack bamboo-ree-1.8.7 > > To switch an existing app to bamboo: > > heroku stack:migrate bamboo-ree-1.8.7 > > Let me know how it goes. > > - Matt Just testing this out now... for anyone who wants to play with this, make sure that you have both the `rdf-raptor` and `ffi` gems specified in your Heroku application's .gems file or Gemfile, and then explicitly switch RDF::Raptor over to using FFI mode by setting an environment variable as follows: $ heroku config:add RDF_RAPTOR_ENGINE=ffi --app myapp (CLI mode is still the default in the current RDF::Raptor release. This will be changed to auto-detection of FFI vis-a-vis CLI mode in the next release.) Unfortunately, at the moment I'm running into this problem: /home/slugs/.../.gems/gems/ffi-0.6.3/lib/ffi/library.rb:113:in `attach_function': Function 'raptor_new_world' not found in [libraptor.so] (FFI::NotFoundError) It looks like RDF::Raptor's FFI mode is currently relying on a `raptor_new_world` function which was only introduced as of libraptor 1.4.19: http://librdf.org/raptor/RELEASE.html#rel1_4_19 Matt, I'm assuming you had to deploy the older libraptor version 1.4.17 because of platform constraints (an "enterprise" Linux distro or the like), making an upgrade infeasible, so we'll try and work around this on our end in the next RDF::Raptor release. Shouldn't be too difficult to fix, I think. I'll keep you posted. -- Arto Bendiken | http://datagraph.org/ -- 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.
Scaling limits and biggest app examples?
I remember seeing discussions in the past where it was said that Heroku can scale to handle any site, and that there haven't been any sites yet that have left due to inability to scale. Is this to say that it is plausible that Heroku's platform could handle running the biggest applications on the Internet, such as a massive search engine (say, Google) or a massive social network (say, Facebook)? I can see why with the dyno system the scaling is effectively unlimited, but I'm a little concerned because with only one database server, it seems like it would be extremely difficult to handle database-heavy use cases. Are there any examples out there of really large and popular sites (especially those that are heavy on the database load) that are run on the Heroku platform? -- 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: SSL issues
Thanks for the feedback. As it turns out, our issue was that we were trying to use two individual SSL certificates on a single IP address. Which is not supported by the protocol. Once we switched over to a multi-domain certificate, everything worked fine. Mike On Jun 11, 2010, at 2:24 AM, Maximilian Mack wrote: > Hi Mike, > did you check that every, i repeat, every single link, image, js or > stylesheet file beginns with either https or has a relative path? > > That's one of the main reasons why browsers don't accept certificates. > > Greetings Max > > > Am 09.06.2010 um 17:06 schrieb Mike Doel: > >> Our app supports two sites: >> >> www.vacationtrade.com >> www.rrbo.com >> >> I have uploaded SSL certificates for both, and heroku ssl:add gave me >> positive assurances that it understood both by telling me what domains they >> were for. >> >> However, we're having problems with the www.rrbo.com one in some >> browsers/platforms. If I go to >> >> https://www.rrbo.com >> >> in Chrome on Mac, everything appears to work just fine. I can click the >> "lock" icon in the browser and it shows me a valid certificate for >> www.rrbo.com. But, if I use either IE or Chrome on Windows, I get browser >> error message. And in Chrome in particular, it tells me that it's being >> served a certificate for www.vacationtrade.com instead of www.rrbo.com. >> >> So, is this a heroku bug where it's giving out the wrong certificates in >> some cases? Is it a problem with how we configured our certificates? >> >> Anyone have any clues? >> >> I've opened a ticket on this, but it's gone unanswered for two days >> (grumble, grumble). >> >> Mike >> >> -- >> 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.
Re: rails-3.0.0.beta4 on bamboo-ree-1.8.7?
Good news! Looking forward to it! On Jun 11, 4:43 am, Pedro Belo wrote: > Hey guys! > > Thanks for reporting. We're aware we need to update Bundler - we'll > roll that out asap! > > On Thu, Jun 10, 2010 at 7:37 PM, Chris Hanks > > > > wrote: > > I'm anxious for Bundler 0.9.26 also! > > > On Jun 9, 3:31 am, Ariejan de Vroom wrote: > >> Hey, > > >> I'm running into a Bundler/Rails issue when trying to deploy a Rails > >> 3.0.0.beta4 app to the bamboo-ree-.1.8.7 stack. Rails 3b4 need bundler > >> 0.9.26, however, 0.9.25 is installed. > > >> Are there any plans on upgrading Bundler on the bamboo stack or are > >> there other ways around? > > >> Thanks, > > >> Ariejan de Vroomhttp://ariejan.net > > > -- > > 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: rails-3.0.0.beta4 on bamboo-ree-1.8.7?
Curious to see the update too! On Jun 11, 4:43 am, Pedro Belo wrote: > Hey guys! > > Thanks for reporting. We're aware we need to update Bundler - we'll > roll that out asap! > > On Thu, Jun 10, 2010 at 7:37 PM, Chris Hanks > > > > wrote: > > I'm anxious for Bundler 0.9.26 also! > > > On Jun 9, 3:31 am, Ariejan de Vroom wrote: > >> Hey, > > >> I'm running into a Bundler/Rails issue when trying to deploy a Rails > >> 3.0.0.beta4 app to the bamboo-ree-.1.8.7 stack. Rails 3b4 need bundler > >> 0.9.26, however, 0.9.25 is installed. > > >> Are there any plans on upgrading Bundler on the bamboo stack or are > >> there other ways around? > > >> Thanks, > > >> Ariejan de Vroomhttp://ariejan.net > > > -- > > 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: Application monitoring and DR/BC backups - SMS and email alerting etc
On 11 June 2010 09:18, Daryl wrote: > Hey there! > > In the past, I've generally had dedicated servers (or Amazon EC2) that > have allowed me to use monit and be pointed at via Nagios for > monitoring and alerting when things went all pear shaped. > > What are people using as reasonably priced options for monitoring the > uptime and such of their heroku apps ? Looked at Scout but sms > monitoring is not available for less than $159 USD a month which is a > bit steep for our NGO on top of the fees we'll be paying heroku. > > Have you heard of these folks: http://pingdom.com/ Cheers, Ben > thanks ! > Daryl. > > > > -- > 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: How can I clean out or reinitialize an app's git repository?
Hey, If you really need to clean out the repo and start from a clean init (I personally think that its worth keeping just for the history) then you can do something along these lines (I haven't tried it so backup and double check before you do it). # find all the git files and remove them cd APP_DIR rm -rf `find . -name .git` #re init the repo git init git add . #check everything and commit git commit -m 'fresh repo after cleanup' # Then add heroku as a remote again git remote add g...@heroku.com:APP_NAME.git heroku # Then force heroku to accept the new commit git push heroku master --force Like I said I haven't checked it so it might be worth making a copy of the app using a bundle or something and testing things first. Steve On Jun 8, 9:39 pm, Dan Z wrote: > I've got several apps where I need to re-init or clean out the > repository (partly to reduce the bundle size). Heroku doesn't support > direct access to the machine. > > Is there some way (e.g. a git command) I can accomplish this without > creating a new app and pushing my clean repository to it? > > The problem with that is that I'd have to re-add and configure all my > addons, and it would require DNS changes, which are a pain and involve > some downtime. -- 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.
Application monitoring and DR/BC backups - SMS and email alerting etc
Hey there! In the past, I've generally had dedicated servers (or Amazon EC2) that have allowed me to use monit and be pointed at via Nagios for monitoring and alerting when things went all pear shaped. What are people using as reasonably priced options for monitoring the uptime and such of their heroku apps ? Looked at Scout but sms monitoring is not available for less than $159 USD a month which is a bit steep for our NGO on top of the fees we'll be paying heroku. Would be interested to hear what other people have come up with. Primarily we'd be looking at alerts when the app is down, there are performance issues or services are otherwise disrupted (ie. site slow, unreachable, or for example, delayed job throws a fit). Additionally, while we're looking at just backing up hourly to an S3 snapshot or the like for the datbase we'd be interested in hearing about what experiences people have had with that when things have gone horribly horribly wrong and in general what the time to recover and such is. thanks ! Daryl. -- 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.
