It’s been a month since we promised that RC4 would be the final
countdown. And counting down we have. We’ve fixed a ton of major,
minor, and aesthetic issues and now have a package that we would be
very proud to call 1.0. No, it’s not completely spotless. A project of
this size with thousands of programmers using it for every application
type under the moon will never be. But it’s Pretty Damn Good.
So here it goes: Release candidate 5. This is the final, short pitstop
before 1.0 materializes next week. Thus, you’re more than well advised
to upgrade and make sure we didn’t leave anything heinous in there.
This is the “speak now or forever hold your peace” part of the
ceremony.
If you already upgraded to 0.14.x, going to RC5 is completely
effortless. Simply call upon the gems to do your bidding with: gem
install rails --include-dependencies. And you’ll be serving up your
application with all the bugs squashed. On top of that, we’ve thrown
in a new adapter for the Firebird database and added a beautiful new
index.html that’ll greet you on new applications.
So upgrade, dammit! Now. And stand by as we finish setting up the
fireworks planned for next week’s release of the long-awaited 1.0.
It’s magical times, my friends, and the spellcasting is just getting
started.
This is the “speak now or forever hold your peace” part of the
fireworks planned for next week’s release of the long-awaited 1.0.
It’s magical times, my friends, and the spellcasting is just getting
started.
I upgraded to it and had some mysql connection timeout error after the
application was idle for a little bit. Sorry for the lack of
specifics, I’ll get the exact error this evening. I’m running on
lighttpd/fcgi/mysql on TxD. The application has been very stable on
0.14.3.
This is the “speak now or forever hold your peace” part of the
fireworks planned for next week’s release of the long-awaited 1.0.
It’s magical times, my friends, and the spellcasting is just getting
started.
I upgraded to it and had some mysql connection timeout error after the
application was idle for a little bit. Sorry for the lack of
specifics, I’ll get the exact error this evening. I’m running on
lighttpd/fcgi/mysql on TxD. The application has been very stable on
0.14.3.
Same problem here, made a new project:
rails MyAppli
cd MyAppli
script/generate scaffold MyModel MyController
get a error… Access denied for user: ‘@localhost’ (Using password: NO)
(root@localhost can xs database but somehow the user is empty, same
error with edgerails…)
lighttpd/fcgi/mysql on TxD. The application has been very stable on
(root@localhost can xs database but somehow the user is empty, same
error with edgerails…)
That wasn’t the error I got, I believe. Again, I’ll post it this
evening.
This may be a stupid question, but after upgrading the gems do we have
to run “rails .” in our project dirs? If that’s the case, what exact
files do we need to overwrite?
This may be a stupid question, but after upgrading the gems do we have
to run “rails .” in our project dirs? If that’s the case, what exact
files do we need to overwrite?
This may be a stupid question, but after upgrading the gems do we have
to run “rails .” in our project dirs? If that’s the case, what exact
files do we need to overwrite?
I don’t think you need to run ‘rails .’
Everything points to libraries in Railties now. Since there haven’t
been any new scripts in script/, you don’t have to run rails.
However, you may want to run rake update_javascripts to get the latest
prototype/scriptaculous files.
The index page in /public? I’m under the impression that it won’t be
updated unless ‘rails’ is
run, which apparently isn’t necessary. I’m looking for something like
<%= debug(version) %>.
The index page in /public? I’m under the impression that it won’t be updated unless ‘rails’ is
run, which apparently isn’t necessary. I’m looking for something like <%= debug(version) %>.
CSN,
PLEASE fix your MUA. Every time you reply you’re creating a new thread.
You’ve scattered a single thread into 3 or 4 threads.
Okay its in 2 threads, but I think that might be from
Okay its in 2 threads, but I think that might be from