Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Hard coded environment settings. Is this a bug?
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  3 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Drinkingbird  
View profile  
 More options Aug 16 2007, 7:32 pm
From: Drinkingbird <drinkingb...@gmail.com>
Date: Thu, 16 Aug 2007 16:32:27 -0700
Local: Thurs, Aug 16 2007 7:32 pm
Subject: Hard coded environment settings. Is this a bug?
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.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Jamis Buck  
View profile  
 More options Aug 16 2007, 8:50 pm
From: "Jamis Buck" <ja...@37signals.com>
Date: Thu, 16 Aug 2007 18:50:58 -0600
Local: Thurs, Aug 16 2007 8:50 pm
Subject: Re: [Capistrano] Hard coded environment settings. Is this a bug?
Sure, I'd entertain a patch for that. If you whip one up, please
submit it to http://dev.rubyonrails.org.

Thanks!

- Jamis

On 8/16/07, Drinkingbird <drinkingb...@gmail.com> wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Drinkingbird  
View profile  
 More options Aug 16 2007, 9:56 pm
From: Drinkingbird <drinkingb...@gmail.com>
Date: Thu, 16 Aug 2007 18:56:49 -0700
Local: Thurs, Aug 16 2007 9:56 pm
Subject: Re: Hard coded environment settings. Is this a bug?
Cheers.

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

- Chris

On Aug 17, 10:50 am, "Jamis Buck" <ja...@37signals.com> wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »