Out of interest, this is the error I get at the moment if I do "gem update rails"...
Upgrading installed gems...
Updating Gem source index for: http://gems.rubyforge.org
ERROR: While executing gem ... (SystemStackError)
stack level too deep
Hi. can you add --backtrace to the end of the command?
···
On 8/12/05, Julian Leviston <julian@coretech.net.au> wrote:
Out of interest, this is the error I get at the moment if I do "gem
update rails"...
Upgrading installed gems...
Updating Gem source index for: http://gems.rubyforge.org
ERROR: While executing gem ... (SystemStackError)
stack level too deep
On 8/12/05, Julian Leviston <julian@coretech.net.au> wrote:
Out of interest, this is the error I get at the moment if I do "gem
update rails"...
Upgrading installed gems...
Updating Gem source index for: http://gems.rubyforge.org
ERROR: While executing gem ... (SystemStackError)
stack level too deep
Hi. can you add --backtrace to the end of the command?
You know, you're probably not going to get a great deal of help from people when asking about an OS that's two major releases obsolete. Mac developers are generally pretty quick to upgrade.
Not all Mac service providers are pretty quick to upgrade though, wouldn't you say?
I mean, we're still running 10.2.8 on our Xserve - and it's working perfectly well for everything it does (and that's a fair bit) - I just can't seem to install Rails properly. I'm running 10.4.2 on my dev machine, however (and I've got rails up and running beautifully on it - 0.13.1).
We're going to upgrade to 10.4.2 on the server shortly, though, so it won't be a problem after that. I'll just have the problem of Apache 2.0. But it does strike me as odd that more people aren't deploying on 10.2.x.
I wonder - does rails work wonderfully on Apache 2.0? We had a lot of interesting times getting WebObjects up and running on Apache 2... anyway.
Anyway... thanks for your two cents
Julian.
···
On 30/08/2005, at 2:11 AM, mathew wrote:
You know, you're probably not going to get a great deal of help from people when asking about an OS that's two major releases obsolete. Mac developers are generally pretty quick to upgrade.
I am running a rails app on Tiger server on a brand new xserve. Apache2 gave me problems with random 500 application errors. So I am running my rails app on Lighttpd/fcgi. It is working wonderfully. Serving up 30-40,000 page views a day.
-Ezra
···
On Aug 29, 2005, at 9:23 AM, Julian Leviston wrote:
Not all Mac service providers are pretty quick to upgrade though, wouldn't you say?
I mean, we're still running 10.2.8 on our Xserve - and it's working perfectly well for everything it does (and that's a fair bit) - I just can't seem to install Rails properly. I'm running 10.4.2 on my dev machine, however (and I've got rails up and running beautifully on it - 0.13.1).
We're going to upgrade to 10.4.2 on the server shortly, though, so it won't be a problem after that. I'll just have the problem of Apache 2.0. But it does strike me as odd that more people aren't deploying on 10.2.x.
I wonder - does rails work wonderfully on Apache 2.0? We had a lot of interesting times getting WebObjects up and running on Apache 2... anyway.
Anyway... thanks for your two cents
Julian.
On 30/08/2005, at 2:11 AM, mathew wrote:
You know, you're probably not going to get a great deal of help from people when asking about an OS that's two major releases obsolete. Mac developers are generally pretty quick to upgrade.