Hi,
I had a similar problem and managed to make the logging work by setting the
log output to stdout, like this:
# From config/environments/staging.rb
MyApp::Application.configure do
config.logger = Logger.new(STDOUT)
# rest of config removed ..
end
Did a blog post on it here:
I am also having this issue I cannot get my debug logs to show up on heroku.
On Tuesday, January 31, 2012 4:21:37 PM UTC-7, GeorgeW wrote:
I am troubleshooting some problem with my app on heroku. And I need
to see some logger.debug output to the via heroku logs
I have set the
I am troubleshooting some problem with my app on heroku. And I need
to see some logger.debug output to the via heroku logs
I have set the appropriate level heroku config:add LOG_LEVEL=DEBUG,
but still it doesn't output the logger.debug output from the
controller.rb but it works fine on
Finally got to the bottom of this. The main culprit behind recent
oddities was a long forgotten .gem file that I didn't delete back when
I updated to rails 3 and bundler. It didn't have any effects on
update pushes and it wasn't in my netbeans project--hence the
forgotten part. But creating
That sounds awfully plausible. Deleting/recreating the heroku app
doesn't help, I'd already tried that at least a dozen times before I
resorted to posting. But still, the idea of a bundle cache sounds
quite likely. Unfortunately I so far haven't been able to find where
that would exist. I've
My app was working fine on the 1.9.2 branch, and it still runs fine
locally. But now when I try to deploy to Heroku it crashes with this
error in the log.
You have already activated rack 1.3.0, but your Gemfile requires rack
1.2.3. Consider using bundle exec. (Gem::LoadError)
I briefly had rails
This happens because rack 1.3.0 still exists in your app's bundler cache and
the stacks prior to cedar do not bundle exec when running your app. You could
work around this by deleting and recreating the app. You could also give the
cedar stack a try which does not have this issue.
Cheers,
I'm running a Rails 3 app using Authlogic 2.1.6. I've added a cron task that
will not execute. It errors out with this:
$ heroku rake cron
(in /app)
start sending reminder emails
rake aborted!
uninitialized constant Object::Event
/usr/ruby1.9.2/lib/ruby/1.9.1/rake.rb:2482:in `const_missing'
/app
Confused how Authlogic, usually found in a controller, could be a part of
this.
Event.send_reminders is not using authentication, is it?
On Tue, Apr 26, 2011 at 10:33 PM, Darren Bereska dbere...@gmail.com wrote:
I'm running a Rails 3 app using Authlogic 2.1.6. I've added a cron task
After more searching, I have finally come across this:
http://stackoverflow.com/questions/4300240/rails-3-rake-task-cant-find-model-in-production
- which provided the hint that the problem is actually due to having
the production environment configured to be thread safe. Since the
cron would work
searching, I have finally come across this:
http://stackoverflow.com/questions/4300240/rails-3-rake-task-cant-find-model-in-production
- which provided the hint that the problem is actually due to having
the production environment configured to be thread safe. Since the
cron would work prior
:
After more searching, I have finally come across this:
http://stackoverflow.com/questions/4300240/rails-3-rake-task-cant-fin...
- which provided the hint that the problem is actually due to having
the production environment configured to be thread safe. Since the
cron would work prior to adding
://devcenter.heroku.com/articles/rails3
--Keenan
On Mar 8, 2011, at 5:21 PM, Damo wrote:
Hi
Im a bit of a rails newbe and am having what is probably a simple
problem to fix but i just cant seem to sort it out.
Ive a very simple rails 3 app deployed to heroku but images are not
being
On Mar 8, 2011, at 5:21 PM, Damo wrote:
Hi
Im a bit of a rails newbe and am having what is probably a simple
problem to fix but i just cant seem to sort it out.
Ive a very simple rails 3 app deployed to heroku but images are not
being served, im getting a 404. When i look in my reroku
Hi
Im a bit of a rails newbe and am having what is probably a simple
problem to fix but i just cant seem to sort it out.
Ive a very simple rails 3 app deployed to heroku but images are not
being served, im getting a 404. When i look in my reroku logs i see
the following:
2011-03-08T13:49:00-08
Disclaimer: I'm biased because I wrote it. But check it
out: http://rack-pagespeed.heroku.com/
File system (~/tmp) storage is flakey since Heroku wipes the directory every
once in a while, so the assets will start 404'ing at some stage. Memcached
store requires you to have the addon enabled,
Hi, I'm trying to get my DJ jobs working in Heroku. I spin up a worker, but
my jobs aren't going through. Is there a way to look at the delayed_job.log
file?
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to
Given the read-only
filesystem: http://docs.heroku.com/constraints#read-only-filesystem
...and the fact that javascript_include_tag :some, :stuff, :cache = true
doesn't seem to work reliably on Heroku with Rails 3...
...and the fact that I have lots of separate javascript and css files
We use https://github.com/sbecker/asset_packager under Rails3 on Heroku -
works great for us,
Run a rake task locally to package after any changes to js/css, commit to
git and then deploy
John.
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To
On Thursday, January 13, 2011 1:35:27 PM UTC, John Beynon wrote:
We use https://github.com/sbecker/asset_packager under Rails3 on Heroku -
works great for us,
Run a rake task locally to package after any changes to js/css, commit to
git and then deploy
Thanks for that. I've been playing
Another approach if you're packaging assets like this anyway would be to upload
them to S3 instead of adding them to the app. You could then use S3 as an asset
host, and even take advantage of CloudFront as a CDN.
On Jan 13, 2011, at 12:49 PM, Trevor Turk wrote:
On Thursday, January 13, 2011
On Thursday, January 13, 2011 5:51:42 PM UTC, David Dollar wrote:
Another approach if you're packaging assets like this anyway would be to
upload them to S3 instead of adding them to the app. You could then use S3
as an asset host, and even take advantage of CloudFront as a CDN.
Yeah, I
I believe if you simply set the asset host in Rails, it will keep appending the
timestamp at the end of the URLs it generates in your view.
On Jan 13, 2011, at 12:55 PM, Trevor Turk wrote:
On Thursday, January 13, 2011 5:51:42 PM UTC, David Dollar wrote:
Another approach if you're packaging
did you ever get this resolved? I'm running into the same problem
today (simple_captcha and imageMagick on heroku, ruby 1.8.7)
On Dec 15 2010, 8:42 am, chadoh chad.ostrow...@gmail.com wrote:
I believe this is probably related to ImageMagick or RMagick. Mycaptchaworks
locally, but the image is
I had to add config.ru to the repository.
Rails 3 has some new components which must be included in your git
push.
One way to figure out what's missing is to compare your app with a
new, empty Rails 3 app. git ls-files lists the files in your git
repository. A commit with nothing changed
I believe this is probably related to ImageMagick or RMagick. My
captcha works locally, but the image is not generated on heroku. I
don't get an error, just no image.
From what I've found around the web, people mainly seem to have
RMagick issues with Paperclip, but I've had Paperclip installed
I've been trying to move an app from Rails 2.3.8 to 3.0.3. The 2.3.8
version runs fine on Heroku. Modified for Rails 3.0.3, it runs on my
Windows/MySQL development machine.
But I haven't been able to get it to run at all on Heroku. bundle
install runs clean, and git push runs clean. All I get
I've got the same thing happening and opened a case with new relic.
Haven't heard back yet. They told me to remove the new relic addon in
the mean time
On Nov 7, 8:11 pm, JDeville jeffdevi...@gmail.com wrote:
Basically, I update my gemfile with:
gem 'newrelic_rpm'
push, add the new relic
Thanks Nader. Would you mind updating me when you get a reply?
On Nov 8, 9:24 am, nader iamna...@gmail.com wrote:
I've got the same thing happening and opened a case with new relic.
Haven't heard back yet. They told me to remove the new relic addon in
the mean time
On Nov 7, 8:11 pm,
Will do
On Nov 8, 6:35 am, JDeville jeffdevi...@gmail.com wrote:
Thanks Nader. Would you mind updating me when you get a reply?
On Nov 8, 9:24 am, nader iamna...@gmail.com wrote:
I've got the same thing happening and opened a case with new relic.
Haven't heard back yet. They told
just remove the gem from your gemfile and you should be ok. the addon
is self contained, so you don't need to add anything to your gemfile
On Nov 8, 7:37 am, nader iamna...@gmail.com wrote:
Will do
On Nov 8, 6:35 am, JDeville jeffdevi...@gmail.com wrote:
Thanks Nader. Would you mind
Basically, I update my gemfile with:
gem 'newrelic_rpm'
push, add the new relic addon, and before long, I get a silent crash
of my app. Nothing logged. I've turned it off for the moment
obviously. Is this a known issue? I'm running Rails 3.01 w/ a
mongodb backend.
--
You received this
The issue seemed to be with Ruby 1.9.2 and Paperclip.
I've moved to Ruby 1.8.7 and everything is working fine.
On Nov 5, 11:53 pm, adriaan adri...@infoding.com wrote:
My app requires image upload functionality for users to upload
images.
I successfully implemented image uploads to S3 using
My app requires image upload functionality for users to upload
images.
I successfully implemented image uploads to S3 using paperclip (as
outlined in Heroku docs - http://docs.heroku.com/s3). Files are
processed to generate 2 new image sizes and uploaded to S3.
This works fine locally, but results
I would go for async load+upload and avoided delayed job
Not really sure if this is possible with paperclip
On Nov 5, 3:53 pm, adriaan adri...@infoding.com wrote:
My app requires image upload functionality for users to upload
images.
I successfully implemented image uploads to S3 using
Hi,
I've been trying to get a freshly created Rails 3.0.1 app up on
Heroku. The app works fine locally, but crashes immediately whenever I
push it to Heroku:
{{code}}
$ heroku logs
Could not find activesupport-3.0.1 in any of the sources
Try running `bundle install`.
== dyno-2863476.log (crash)
Anyone have thoughts or know if mongo mapper or mongoid work better with
rails 3 on heroku? Tried a couple things with each to see if I liked one
more that the other, but it seems fairly even. Just wondering if one runs
better on heroku rails3.
Thanks,
Josh
@JoshCoffman
480-270-4578 | josh
...@gmail.comwrote:
Anyone have thoughts or know if mongo mapper or mongoid work better with
rails 3 on heroku? Tried a couple things with each to see if I liked one
more that the other, but it seems fairly even. Just wondering if one runs
better on heroku rails3.
Thanks,
Josh
@JoshCoffman
@cloudmailin
Incoming email for your web app
On 21 Sep 2010, at 15:20, Josh Coffman wrote:
Anyone have thoughts or know if mongo mapper or mongoid work better with
rails 3 on heroku? Tried a couple things with each to see if I liked one more
that the other, but it seems fairly even. Just
Incoming email for your web app
On 21 Sep 2010, at 15:20, Josh Coffman wrote:
Anyone have thoughts or know if mongo mapper or mongoid work better with
rails 3 on heroku? Tried a couple things with each to see if I liked one
more that the other, but it seems fairly even. Just wondering if one runs
came from but it works like a charm so
thanks to whoever created it :-)
Steve
--
http://cloudmailin.com
@cloudmailin
Incoming email for your web app
On 21 Sep 2010, at 15:20, Josh Coffman wrote:
Anyone have thoughts or know if mongo mapper or mongoid work better with
rails 3 on heroku
I have a controller that's slow every now and then, but can't figure
out why. I've gone all the way up to gold with NewRelic, and the
tracing doesn't go any further than the controller action, which
doesn't really help me identify where my problem is. Is NewRelic not
working properly with rails 3
and then, but can't figure
out why. I've gone all the way up to gold with NewRelic, and the
tracing doesn't go any further than the controller action, which
doesn't really help me identify where my problem is. Is NewRelic not
working properly with rails 3 yet?
--
You received this message
(',')})
decent.not_in(:_id = ids_to_exclude).skip(skip).limit(limit)
}
seems absurd. :-)
On Sep 1, 9:56 am, Neil Middleton neil.middle...@gmail.com wrote:
Here's a snapshot of a production Rails 3 running NewRelic Bronze (on
Heroku).
Are you seeing the same level of detail?
http://i54
Am 12.08.2010 um 01:59 schrieb Mitchell Hashimoto:
I would recommend running Rails 3 on Ruby
1.8.7, which is supported, and which I can say from experience works
great.
In my experience it doesn't work good enough for environments which need UTF8.
Stefan
--
AMOOMA GmbH - Bachstr. 126
Hi,
just wanted to do a heroku rake db:migrate and look what happened. The
current situation with Ruby 1.9.1 on Heroku is a bit disappointing. I really
would like to use Heroku but haven't been able to fire up a single Rails 3
server yet.
---cut---
s...@swmbp 0 1.9.2-preview3
...@amooma.de wrote:
Hi,
just wanted to do a heroku rake db:migrate and look what happened. The
current situation with Ruby 1.9.1 on Heroku is a bit disappointing. I really
would like to use Heroku but haven't been able to fire up a single Rails 3
server yet.
---cut---
s...@swmbp 0 1.9.2
So this should make rails3 rc work, right? :)
--
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
It usually takes Heroku a week to test the latest bundler before
deploying it -
On Jul 27, 1:34 am, Daniel Kehoe gro...@fortuity.com wrote:
Heroku, please update Bundler to 1.0.0.rc.1 so we can use our Rails 3
apps.
The Rails 3 release candidate is out and now we can't deploy Rails 3
apps
Heroku, please update Bundler to 1.0.0.rc.1 so we can use our Rails 3
apps.
The Rails 3 release candidate is out and now we can't deploy Rails 3
apps to Heroku.
I get
- Gemfile detected, running Bundler
Unresolved dependencies detected; Installing...
Fetching source index from
it.
Let us know if that works out, I'm sure there are more people looking
forward for NR + Rails 3 :)
On Mon, Jul 19, 2010 at 2:40 PM, Neil neil.middle...@gmail.com wrote:
Hi Everyone,
Apparently with Rails 3, NewRelic have a beta (http://rubygems.org/
gems/newrelic_rpm/versions/2.13.0.beta5
, Jul 19, 2010 at 11:21 PM, Pedro Belo pe...@heroku.com wrote:
You can install any version of the New Relic agent you want to
vendor/plugins/rpm and we won't overwrite it.
Let us know if that works out, I'm sure there are more people looking
forward for NR + Rails 3 :)
On Mon, Jul 19, 2010 at 2
any version of the New Relic agent you want to
vendor/plugins/rpm and we won't overwrite it.
Let us know if that works out, I'm sure there are more people looking
forward for NR + Rails 3 :)
On Mon, Jul 19, 2010 at 2:40 PM, Neil neil.middle...@gmail.com wrote:
Hi Everyone,
Apparently
for NR + Rails 3 :)
On Mon, Jul 19, 2010 at 2:40 PM, Neil neil.middle...@gmail.com wrote:
Hi Everyone,
Apparently with Rails 3, NewRelic have a beta (http://rubygems.org/
gems/newrelic_rpm/versions/2.13.0.beta5) that works.
If we were to install this version into an app would it deploy
Hi Everyone,
Apparently with Rails 3, NewRelic have a beta (http://rubygems.org/
gems/newrelic_rpm/versions/2.13.0.beta5) that works.
If we were to install this version into an app would it deploy OK or
would it interfere with the one that Heroku uses by default? Is it
possible to try
You can install any version of the New Relic agent you want to
vendor/plugins/rpm and we won't overwrite it.
Let us know if that works out, I'm sure there are more people looking
forward for NR + Rails 3 :)
On Mon, Jul 19, 2010 at 2:40 PM, Neil neil.middle...@gmail.com wrote:
Hi Everyone
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
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 yuriga...@gmail.com 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
, 2010 at 2:27 PM, Yuri yuriga...@gmail.com 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
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
Hi Guys,
it took me hours but finally i got it:
If you have problems get your time and date saved as UTC, try to add
ENV['TZ'] = 'UTC' in your environment.rb file.
Befor that, i could do what i want, but times got saved in Pacific
TIme Zone in the DB.
Can someone confirm this? OR explain ;-)
...@heroku.com wrote:
I don't think new relic supports rails 3 yet.
On Mon, May 17, 2010 at 9:21 AM, Neil neil.middle...@gmail.com wrote:
I'm hitting a brick wall on this, but does anyone else have issues
with Rails 3 andNewRelicon Heroku? Even when I create a vanilla
Rails 3 app
things.
On Mon, May 17, 2010 at 12:23 PM, Oren Teich o...@heroku.com wrote:
I don't think new relic supports rails 3 yet.
On Mon, May 17, 2010 at 9:21 AM, Neil neil.middle...@gmail.com wrote:
I'm hitting a brick wall on this, but does anyone else have issues
with Rails 3 and NewRelic
I could be wrong but I believe in Rails 3 the options in Initializers
affect the ActiveRecord time (ie. writing to the DB in the local time
zone rather than UTC) but Time Zones set in the controllers are
supposed to make the application honour time zone settings versus the
System Date/Time.
I
Hi Daryl,
I'm still living in 2.3 land, but one thing I often see is using Time.now vs
Time.zone.now
Also, in test_helper (not sure the rails 3.0 equivalent), I needed to set a
default Time.zone - otherwise the Time.zone is nil, so Time.zone.now throws
exceptions
--Keenan
On May 3, 2010, at
Hi Daryl,
The Time.zone code only affects the behavior of Time.zone
(Time.zone.now, Time.zone.parse, ActiveRecord's casting of Date
columns, etc) inside your application; it doesn't have any effect on
system time (which is what `date` as well as Time.now will give you).
The best practice is to
I keep trying to install the email deploy hook (I like infomring
myself I've depoyed... ahem... ) and it keeps giving me a heroku error
when I try to activate and Test it. Also, while configured, it's not
sending mails when I deploy.
Still being worked on for Rails 3?
Are there any other AddOns
Look at this thread:
http://groups.google.com/group/heroku/browse_thread/thread/a857eb7e93cb03b2?hl=pl
--
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
Solved... For some reason it appears that when I created the app the
1.9.1 stack did not stick. Detroying the app and then recreating it
again with the bamboo-mri-1.9.1 stack and then redeploying did the
trick.
D
On Apr 28, 1:33 am, Daryl daryl.mann...@gmail.com wrote:
Oh and bundler is
Oh and bundler is (0.9.24)
--
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
Hi all,
I'm a Rails 2 user, and I am trying to set up an app on Heroku using
Rails 3.0.0.beta. Here is the error that I get at http://correctpath.heroku.com
:
App failed to start
Check out the troubleshooting section on our Documentation site.
Original Error
On Apr 27, 3:52 am, Shane Becker veganstraighte...@gmail.com wrote:
is anyone having success with bundler?
namely, are your dev only gems *not* compiled into your production slug?
mine are. it's making kittens cry.
Heroku locks bundle with all groups, I think it's even documented
somewhere. I
is anyone having success with bundler?
namely, are your dev only gems *not* compiled into your production slug?
mine are. it's making kittens cry.
thanks
sb
still vegan. still straightedge.
shane becker
+1 801 898-9481
blog: http://iamshane.com
shirts:
Try using bundler 0.9.20.
On Thu, 2010-04-22 at 15:05 -0700, Dave Rupert wrote:
Hello,
I have a Rails 3.0.0.beta3 app ( bundler 0.9.23 ) on the bamboo-
ree-1.8.7 stack that i'm trying to push, but I keep getting stuffed
and the App is Failing to Start. Keeps giving me a Read-only file
Lifesaver! Totally worked.
On Apr 23, 11:47 am, Terence Lee hon...@gmail.com wrote:
Try using bundler 0.9.20.
On Thu, 2010-04-22 at 15:05 -0700, Dave Rupert wrote:
Hello,
I have a Rails 3.0.0.beta3 app ( bundler 0.9.23 ) on the bamboo-
ree-1.8.7 stack that i'm trying to push, but I keep
%w(environments you want notifications from)
filters %w(MEMCACHE_PASSWORD MEMCACHE_USERNAME) # or whatever is
applicable
end
On Apr 11, 11:24 am, Chap chapambr...@gmail.com wrote:
Anybody successfully using hoptoad with a rails 3 app?
This didn't work for
me:http
Anybody successfully using hoptoad with a rails 3 app?
This didn't work for me:
http://help.hoptoadapp.com/discussions/questions/216-rails-3-support
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to her
A friend of mine modified Hassle and made this great little writeup:
http://mentalized.net/journal/2010/04/06/heroku_rails_3_and_sass/
Cheers,
Casper Fabricius
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to
, peterpunk pedro.visin...@gmail.com wrote:
I'm currently using rails 3 and ruby 1.9.1 and I'm getting this error
when I add the will_paginate gem from my fork on github.
I'm also using another gems from github without problems.
This is how is included in the gemfile:
gem 'will_paginate', :git
I'm currently using rails 3 and ruby 1.9.1 and I'm getting this error
when I add the will_paginate gem from my fork on github.
I'm also using another gems from github without problems.
This is how is included in the gemfile:
gem 'will_paginate', :git = 'git://github.com/peterpunk
I'm seeing the same problem with gems installed via git; it only
started happening in the last few days. Was there a change?
On Mar 30, 7:04 pm, peterpunk pedro.visin...@gmail.com wrote:
I'm currently using rails 3 and ruby 1.9.1 and I'm getting this error
when I add the will_paginate gem from
.
On Mar 30, 10:04 am, peterpunk pedro.visin...@gmail.com wrote:
I'm currently using rails 3 and ruby 1.9.1 and I'm getting this error
when I add the will_paginate gem from my fork on github.
I'm also using another gems from github without problems.
This is how is included in the gemfile:
gem
Hi, I was trying to deploy a sample rails 3 app.
I follow the rails 3 document. I followed this as well
http://docs.heroku.com/bundler.
I have my Gemfile in the root of the sample app.
I am getting these errors.
- Heroku receiving push
- Gemfile detected, running Bundler
are you running on the bamboo stack?
run heroku stack to see which stack it's set to.
Oren
On Thu, Mar 25, 2010 at 11:33 AM, Nathan Clark nathanclar...@gmail.comwrote:
Hi, I was trying to deploy a sample rails 3 app.
I follow the rails 3 document. I followed this as well
http
:
Hi, I was trying to deploy a sample rails 3 app.
I follow the rails 3 document. I followed this as well
http://docs.heroku.com/bundler.
I have my Gemfile in the root of the sample app.
I am getting these errors.
- Heroku receiving push
- Gemfile detected, running Bundler
Taps 0.2 activates Thor 0.9.9 (exact) and Rails 3 Thor 0.13.0. Taps
0.3.pre4 removes thor entirely, but won't talk to Taps 0.2 on Heroku.
Is there a work around for loading a DB in a Rails 3 beta stack?
--
You received this message because you are subscribed to the Google Groups
Heroku group
After successful deploy to bamboo-mri-1.9.1, all I can see is static
page saying:
Heroku | Welcome to your new app!
Refer to the documentation if you need help deploying.
Logs are empty.
Is there anyone who is running rails 3 app on heroku?
--
You received this message because you
are empty.
Is there anyone who is running rails 3 app on heroku?
--
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
Obviously I tried this, but didn't help. Anyway after Gemfile refresh
it started.
New problem is that on heroku is bundler 0.9.5 which is not working
with rails master.
And application which is running on rails master, doesn't run on rails
3.0.0.beta anymore (which is running with bundler 0.9.5)
Just wondering whether people will have the option to play with the 3
beta (once released) on Heroku?
--
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
We don't run any customized version of Rails, so most probably yes -
you should be able to just run it.
On Tue, Nov 24, 2009 at 4:59 PM, jasonb jason.bower...@gmail.com wrote:
Just wondering whether people will have the option to play with the 3
beta (once released) on Heroku?
--
You
Rails 3 won't run on Ruby 1.8.6, so Heroku will need to offer Ruby
1.8.7 or 1.9 (preferably 1.9) before we can use it. This is what's
keeping me from trying out Rails 3.0.pre on Heroku right now.
Source:
http://www.mail-archive.com/rubyonrails-c...@googlegroups.com/msg09683.html
On Nov 25
92 matches
Mail list logo
