Forum: Ruby on Rails Capistrano/SwitchTower "current" dir deployment question

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
Bb4bdf2b184027bc38d4fb529770cde5?d=identicon&s=25 Wes Gamble (weyus)
on 2006-04-11 00:18
All,

I have successfully executed the "deploy" task in Capistrano/Switchtower
to establish a symbolic link named "current" which points to the current
version of my app. on my remote server.

My app. was already deployed to the existing Rails root directory (call
it "appname") though.
I have Apache fronting my app. through a virtual host whose doc. root is
itself a symbolic link to "appname".

So to summarize, now I have

appname/app
appname/config
.
.
.
appname/vendor

because of the "OLD" way,

and I have

appname/current/app
appname/current/config
.
.
.
appname/current/vendor

because of Capistrano deployment.

In order to take advantage of my new deployment ability, should I:

1) Point my Apache symlink to the "appname/current" symlink

OR

2) somehow force my RAILS_ROOT to be this "appname/current" symlink

OR

3) configure Capistrano to use "appname" itself as the name of the
"current" directory and lose the directory named "current" living under
"appname"?

I hope that this makes sense.

Thanks,
Wes
992fe8c19bbbc27f2b562a9f96efc03d?d=identicon&s=25 Jamis Buck (Guest)
on 2006-04-11 07:05
(Received via mailing list)
Wes,

The recommended route is to point apache at the 'current' symlink.
You could probably make it work in any number of other ways, but
it'll go a lot easier on you if you simply conform. :)

- Jamis
This topic is locked and can not be replied to.