# Login Engine replacement or upgrade **URL:** \ **Category:** Rails\ **Created:** [March 6, 2007, 11:18am UTC](https://www.ruby-forum.com/t/login-engine-replacement-or-upgrade/102702 "2007-03-06T11:18:47Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Tiago\_F](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/58956e/32.png) [@Tiago\_F](https://www.ruby-forum.com/u/Tiago_F)\ **Post date:** [March 6, 2007, 11:18am UTC](https://www.ruby-forum.com/t/login-engine-replacement-or-upgrade/102702/1 "2007-03-06T11:18:47Z")
Hi, I have an app that uses login\_engine and the hosting company upgraded to Rails 1.2. Does anyone knows a good alternative, if possible to reuse the existing data in the database from the login\_engine? Thanks, Tiago F. ---
**Author:** ![Tiago\_F](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/58956e/32.png) [@Tiago\_F](https://www.ruby-forum.com/u/Tiago_F)\ **Post date:** [March 6, 2007, 3:06pm UTC](https://www.ruby-forum.com/t/login-engine-replacement-or-upgrade/102702/2 "2007-03-06T15:06:06Z")
Tiago, Why don’t you just freeze the version of rails you were using into the /vendor directory? That way you can still use the existing application and plugins as they are. The usual call is ‘rake freeze\_gems’ BR Mezza On Mar 6, 10:18 am, Tiago F. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) ---
**Author:** ![Tiago\_F](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/58956e/32.png) [@Tiago\_F](https://www.ruby-forum.com/u/Tiago_F)\ **Post date:** [March 8, 2007, 11:45am UTC](https://www.ruby-forum.com/t/login-engine-replacement-or-upgrade/102702/3 "2007-03-08T11:45:33Z")
Hi, Thanks for the reply. The upgrade on the server was already made, is it possible to force the app to be frozen in a previous version of the gems? Thanks, Tiago F. mezza wrote: > Tiago, > > Why don’t you just freeze the version of rails you were using into > the /vendor directory? That way you can still use the existing > application and plugins as they are. > > The usual call is ‘rake freeze\_gems’ > > BR > > Mezza > > On Mar 6, 10:18 am, Tiago F. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) ---
**Author:** ![Tiago\_F](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/58956e/32.png) [@Tiago\_F](https://www.ruby-forum.com/u/Tiago_F)\ **Post date:** [March 8, 2007, 3:04pm UTC](https://www.ruby-forum.com/t/login-engine-replacement-or-upgrade/102702/4 "2007-03-08T15:04:04Z")
Hi Tiago, I usually run the rake freeze\_gems or rake rails:freeze:gems on my apps on my development box before pushing them up to production servers. If you can’t do that for whatever reason, it is also possible to svn external a link in your /vendor directory. I don’t do this too much, so not sure of the syntax, but I’m sure you’ll be able to google it. The Rails 1.1 release should be able to be svn externalled into your app by typing: svn propset svn:externals “rails [http://dev.rubyonrails.org/svn/rails/branches/1-1-stable](http://dev.rubyonrails.org/svn/rails/branches/1-1-stable)” vendor from the root of your rails app. Assuming your on \*nix and have svn available. There is also one last option which is that if your hosting company haven’t deleted the previous versions of the rails gems you cold edit your environment.rb file to specify the version you want to use (but I’d stick with just freezing the version you want to /vendor). HTH Mezza ---
**Author:** ![Tiago\_F](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/58956e/32.png) [@Tiago\_F](https://www.ruby-forum.com/u/Tiago_F)\ **Post date:** [March 8, 2007, 10:52pm UTC](https://www.ruby-forum.com/t/login-engine-replacement-or-upgrade/102702/5 "2007-03-08T22:52:07Z")
Hi, Thank you very much Mezza, it worked. Tiago F. mezza wrote: > Hi Tiago, > > I usually run the rake freeze\_gems or rake rails:freeze:gems on my > apps on my development box before pushing them up to production > servers. > > If you can’t do that for whatever reason, it is also possible to svn > external a link in your /vendor directory. > > I don’t do this too much, so not sure of the syntax, but I’m sure > you’ll be able to google it. The Rails 1.1 release should be able to > be svn externalled into your app by typing: > > svn propset svn:externals “rails > [http://dev.rubyonrails.org/svn/rails/branches/1-1-stable](http://dev.rubyonrails.org/svn/rails/branches/1-1-stable)” > vendor > > from the root of your rails app. Assuming your on \*nix and have svn > available. > > There is also one last option which is that if your hosting company > haven’t deleted the previous versions of the rails gems you cold edit > your environment.rb file to specify the version you want to use (but > I’d stick with just freezing the version you want to /vendor). > > HTH > > Mezza