So the *Feature* that says my PATH tweaks and environment variables
will all be set as expected.
I'm not seeing that.
Are you saying that my .profile (or whatever my default profile is set
to) will be loaded?
I ran an echo $PATH as a command and don't see my path as modified in
my .profile (and
I created a screencast[1] for the RailsRumble[2] contest, and it has
some capistrano content that I think could be beneficial to new users
of capistrano who may be lurking here. It is 27 minutes long, and
goes the basics of deploy a Rails app to Debian.
1:
I frequently reference configuration parameters within the value of
others. This does not work when defining configuration parameters
within the project UI.
Example
set :application, authentication
set :repository, svn://sourcetree.foo.local/#{application}/
#{target_branch}
(Where
Tim wrote:
However this is what happens: *** LOCAL SCM ERROR: svn: URL
'svn://sourcetree.foo.local/ #{application}/#{target_branch}' is not
properly URI-encoded
The values are not being replaced. Should this be possible via the
UI? I'd like the neatness the UI provides, but the only way
Ok; much better! Thanks. I did use ruby gems but got an old version of
highline for some reason.
However, I am still having difficulties;
* executing `deploy:cold'
* executing `deploy:update'
** transaction: start
* executing `deploy:update_code'
svn: Can't create tunnel: The system
What is your :repository variable set to?
- Jamis
On 9/4/07, rails chick [EMAIL PROTECTED] wrote:
Ok; much better! Thanks. I did use ruby gems but got an old version of
highline for some reason.
However, I am still having difficulties;
* executing `deploy:cold'
* executing
ENV is a Hash instance, containing all defined environment variables.
However, that's not really going to be the problem, since all it means
is that you don't have one of the (optional) environment variables
set. Rather, the error you are getting occurs when you don't have your
roles configured
No I don't have a Capfile. I was under the impression that was for
2.0 only, although I could very well be wrong. I am using 1.4.1.
Although I ran the command again to find the previous error message
and this time it worked. Not sure why. I am just getting some
permission errors on the
