The new gem version dependency system from Rails 1.1.1 needed a few
tweaks to work properly and to stop throwing meaningless warnings.
This tiny release makes up for that. To install:
- gem install rails
- rake rails:update:configs (to get the latest config/boot.rb)
This release also signals our new commitment to do more tiny releases
from the stable branch, which only gets bug fixes. So it will not be
uncommon to see bi-weekly tiny releases in the 1.1.x series while we
continue to add features to the forthcoming 1.2.0.
David Heinemeier H.
http://www.loudthinking.com – Broadcasting Brain
http://www.basecamphq.com – Online project management
http://www.backpackit.com – Personal information manager
http://www.rubyonrails.com – Web-application framework
David Heinemeier H. wrote:
The new gem version dependency system from Rails 1.1.1 needed a few
tweaks to work properly and to stop throwing meaningless warnings.
This tiny release makes up for that. To install:
- gem install rails
- rake rails:update:configs (to get the latest config/boot.rb)
This release also signals our new commitment to do more tiny releases
from the stable branch, which only gets bug fixes. So it will not be
uncommon to see bi-weekly tiny releases in the 1.1.x series while we
continue to add features to the forthcoming 1.2.0.
Thank you! Sounds like we’ll be getting the best of both worlds (cool
new features in 1.2.0 and tiny bugfix releases in 1.1.x).
Looks like it is going to be an amazing year for Rails…
Hi, I received the following when I tried to perform the following
command:
rake rails:update:configs
rake aborted!
No Rakefile found (looking for: rakefile, Rakefile, rakefile.rb,
Rakefile.rb)
/usr/local/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:1822:in
`load_rakefile’
(See full trace by running task with --trace)
On 4/9/06, Conrad T. [email protected] wrote:
(See full trace by running task with --trace)
Hi Conrad. Make sure you are in the root directory of your relevant
rails
applications when you run that second command.
-Matt
You can use the:
rake rails:freeze:edge TAG=rel_1-0-0
Which will deploy 1.0.0 on that rails app.
-Nb
On 4/9/06 4:58 PM, “Conrad T.” [email protected] wrote:
The new gem version dependency system from Rails 1.1.1 needed a few
http://lists.rubyonrails.org/mailman/listinfo/rails
Rails mailing list
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails
Nathaniel S. H. Brown http://nshb.net
Should I reinstall 1.0 because I performed ‘gem cleanup after
installing 1.0’? Also, is it possible to select a version of rails to
develop with upon rails project creation?
Thanks in advance,
-Conrad
How many versions of rails can one install at a time? I’m needing to
use 1.0 because the hosting account is using ths version. Also, I
would like to experiment with the new features.
Thanks in advance,
-Conrad
So, switching to edge rails locally allow me to use any version of rails
on
my remote host? BTW, the remote host is current running 1.0?
-Conrad
Conrad T. wrote:
Should I reinstall 1.0 because I performed ‘gem cleanup after
installing 1.0’? Also, is it possible to select a version of rails to
develop with upon rails project creation?
Thanks in advance,
-Conrad
Try this link.
http://www.google.com/search?rls=en&q=freeze_edge+rails:freeze:edge&ie=utf-8&oe=utf-8
I think you’ll be amazed at the advances search engines made in the past
decade.
If you have trouble with a command, simply enter it into Google and bam!
You get numerous relevant hits. Same thing goes for error messages.
Try it out.
The TAG option for rake rails:freeze:edge came out with 1.1.0, so you
will
need to have at least one package installed with it.
You can install into a directory which you don’t even use other than for
deployment.
For example, on your remote server with 1.0.
Deploy a frozen edge.
rails ./
rake freeze_edge # This should bring you up to 1.1.0+
Now you will have access to 1.1.0 rake tasks, which you can use to
deploy
into other directories.
So you could use this command to get any tagged release you would like.
rake rails:freeze:edge REL=rel_1-0-0
rails ./
Now, one thing I haven’t tested, would be whether or not an older
version of
Rake will work like this (it should). Only way to know for sure is to
try,
so let me know how it goes 
-Nb
On 4/9/06 9:20 PM, “Conrad T.” [email protected] wrote:
develop with upon rails project creation?
Rails mailing list
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails
Rails mailing list
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails
Nathaniel S. H. Brown http://nshb.net
A slight modification to this…
On 4/9/06 9:33 PM, “Nathaniel B.” [email protected] wrote:
rails ./
rake freeze_edge # This should bring you up to 1.1.0+
Now you will have access to 1.1.0 rake tasks, which you can use to deploy
into other directories.
So you could use this command to get any tagged release you would like.
At this point you would deploy the same version you are using into the
target:
rails /path/to/target/rails --freeze
And now you would downgrade it to 1.0.0
rake rails:freeze:edge REL=rel_1-0-0
Would be nice to be able to have a REL tag in the rails command. I just
submitted a enhancement suggestion for this at:
http://dev.rubyonrails.org/ticket/4677
-Nb
my remote host? BTW, the remote host is current running 1.0?
Thanks in advance,
-Conrad
Try this link.
freeze_edge rails:freeze:edge - Google Search>>>
&
–
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails
Nathaniel S. H. Brown http://nshb.net
Hey Nathaniel, thanks for all the information. After reading about Edge
Rails, this simply what I need to do because my host is at 1.0 and I
simply
like to do rails apps that are 1.1+. Now, I have the following
question(s):
- After installing the edge rails locally on my system, is there a
different process for installing
the remaining gems? At this time, my getting started projects
don’t
use Subversion but it
seems that I should start.
I’ll setup SVN and follow the require steps to get Edge Rails installed
for
ongoing RoR projects.
Thanks again,
-Conrad
Hi, thanks for the information. I don’t have access to any command
line on the remote server. Thus, in you previous e-mail, I cannot
perform the following:
BEGIN PREVIOUS TRANSCRIPT:
For example, on your remote server with 1.0.
Deploy a frozen edge.
rails ./
rake freeze_edge # This should bring you up to 1.1.0+
Now you will have access to 1.1.0 rake tasks, which you can use to
deploy
into other directories.
So you could use this command to get any tagged release you would like.
rake rails:freeze:edge REL=rel_1-0-0
rails ./
END PREVIOUS TRANSCRIPT:
-Conrad
Using the -f (–freeze) uses the vendor, or current deployment for the
rails
update.
So if I am in a rails project (which has vendor/rails frozen to edge):
/rails/edge/# rails /path/to/new/project -f
That directory will also get edge version based on the fact that I
deployed
it with the -f/–freeze flag. From what I understand, it will only
deploy
the rails directory, but you may want to verify this yourself.
I outlined the steps before how to get up to 1.1.2. Re-read my previous
emails.
-Nb
On 4/9/06 10:19 PM, “Conrad T.” [email protected] wrote:
Now, one thing I haven’t tested, would be whether or not an older
rails on
develop with upon rails project creation?
freeze_edge rails:freeze:edge - Google Search
You get numerous relevant hits. Same thing goes for error messages.
Rails mailing list
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails
Nathaniel S. H. Brown http://nshb.net
Do it locally and upload the files?
Hmmm…
On 4/10/06 12:41 AM, “Conrad T.” [email protected] wrote:
rails ./
END PREVIOUS TRANSCRIPT:
On 4/9/06 10:19 PM, “Conrad T.” [email protected] wrote:
On 4/9/06, Conrad T. [email protected] wrote:
seems that I should start.
A slight modification to this…
deployment.
into other directories.
And now you would downgrade it to 1.0.0
So, switching to edge rails locally allow me to use any version of
to
If you have trouble with a command, simply enter it into Google and
http://lists.rubyonrails.org/mailman/listinfo/rails
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails
Nathaniel S. H. Brown http://nshb.net
David Heinemeier H. wrote:
This release also signals our new commitment to do more tiny releases
from the stable branch, which only gets bug fixes. So it will not be
uncommon to see bi-weekly tiny releases in the 1.1.x series while we
continue to add features to the forthcoming 1.2.0.
Good move!
thanks
Justin
Hey Nathaniel, I actually would like to deploy a rails 1.1.2 or later
application to a target (i.e. remote host) that has 1.0 installed.
Next, I
guess the non-development rails application folder should house the SVN
updates that are used with later projects. Now, is there an easy way to
when
invoking the rails command to create the application folder to pull in
the
stuff from the template application (i.e. vendor directory)?
-Conrad