Hard coded environment settings. Is this a bug?

[Drinkingbird]

Hi all,

I've come across a situation where I needed to use a name other than
'current' for the symlink to the latest release.

Various docs I've found say that this can be changed using
the :current_dir variable in capistrano.

After a while of trying to figure out why that wasn't working, I went
digging around in the gem files and found this:

_cset(:releases_path) { File.join(deploy_to, "releases") }
_cset(:shared_path) { File.join(deploy_to, "shared") }
_cset(:current_path) { File.join(deploy_to, "current") }

Is this hard-coding something new to cap 2.0? I'd expected to find
something more like:

_cset(:releases_path) { File.join(deploy_to, release_dir) }
_cset(:shared_path) { File.join(deploy_to, shared_dir) }
_cset(:current_path) { File.join(deploy_to, current_dir) }

with the 3 _dir variables set somewhere else.

Should I be submitting this as a bug? It looks like an oversight much
more than it does a conscious design.

[Jamis Buck]

Sure, I'd entertain a patch for that. If you whip one up, please
submit it to http://dev.rubyonrails.org.

Thanks!

- Jamis

[Drinkingbird]

Cheers.

Patch at http://dev.rubyonrails.org/ticket/9283

- Chris

On Aug 17, 10:50 am, "Jamis Buck" <ja...@37signals.com> wrote:
> Sure, I'd entertain a patch for that. If you whip one up, please

> submit it tohttp://dev.rubyonrails.org.
>
> Thanks!
>
> - Jamis