Login Engine replacement or upgrade

Rails
1

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.

2

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. [email protected]

3

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. [email protected]

4

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”
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

5

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”
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