It sounds like you might have a bare deploy.cold somewhere in your
recipe file, or in your ~/.caprc file. Also, are you using any
capistrano plugins or extensions?
- Jamis
On Mar 8, 2008, at 7:28 PM, J2M wrote:
I am getting some very bizarre behaviour with cap 2. When I run any of
The default deploy is for Rails apps, so it tries to symlink and fix
permissions on the standard rails directories. If you aren't deploying
a rails app, you'll want to override the deploy:finalize_update task,
either to do nothing, or to do post-checkout tweaks as necessary:
deploy.task
If you are not deploying a web application, then there is probably
nothing to restart after a deploy. Thus, you might want to override
the deploy:restart task as well:
deploy.task :restart do
# nothing
end
- Jamis
On Mar 10, 2008, at 9:19 AM, [EMAIL PROTECTED] wrote:
Thanks. It
The Pageant interaction relies on the Ruby/DL library (bundled with
Ruby) to call into native C routines and communicate with pageant via
the windows interprocess API. I didn't write it (it was contributed),
and I don't have any way to test it--can anyone else confirm that
these errors are
From man nohup:
If the output file nohup.out cannot be created in the current
directory, the nohup utility uses the directory named by HOME
to create the file.
My guess is that since sh -c doesn't start a login shell, it is
inheriting the environment of the invoking shell, including the
On Mar 31, 2008, at 3:46 PM, Thijs van der Vossen wrote:
On 31 Mar 2008, at 23:41, Jamis Buck wrote:
From man nohup:
If the output file nohup.out cannot be created in the current
directory, the nohup utility uses the directory named by HOME
to create the file.
My guess is that since sh -c
On Apr 1, 2008, at 10:38 AM, Andrew McClain wrote:
Sean,
I'm already prompting the user for a password using password_prompt.
The issue isn't showing the password when the user _enters_ it, the
issue is that the password shows up in the capistrano log when the
command is executed.
i.e.
pass
I've been waiting to announce for github to implement the git -
lighthouse post-commit hooks, but I'll go ahead and post the link:
http://capistrano.lighthouseapp.com
New tickets should be posted here. Thanks!
- Jamis
On Apr 2, 2008, at 11:14 PM, Tim Carey-Smith wrote:
Hey Jamis,
Is
:
On Apr 8, 5:41 pm, Jamis Buck [EMAIL PROTECTED] wrote:
The lib/tasks/capistrano.rake file was deprecated long ago, and is
not
supported at all in modern cap versions (unless you're writing your
own capistrano.rake file, which I do not recommend).
Even config/deploy.rb is not necessary--you can
Thanks John. Could you submit this patch to the capistrano ticket
system?
http://capistrano.lighthouseapp.com/projects/8716-capistrano/tickets
Much appreciated!
- Jamis
On Apr 9, 2008, at 1:33 PM, John Aughey wrote:
Deploying with git fails because of missing parens around a command
I wonder if it wouldn't be better to make something like the following
work as you would expect:
namespace :some_app do
load 'deploy'
end
I suppose there is a risk of that breaking existing scripts that
depend on the current behavior, though. Could possibly introduce
another
I suspect that's breaking because your line break is inside a quoted
string...and capistrano's escaping is too naive to understand that.
You could put the command in a script and execute the script, thereby
foiling cap's escaping logic.
- Jamis
On Apr 10, 2008, at 10:23 AM, Brian Hartin
:my_app do
load 'deploy'
task :in_my_app do
deploy.symlink
end
after :in_my_app, 'deploy:web:enable'
end
(These are contrived examples, by the way.)
On Thu, Apr 10, 2008 at 11:30 AM, Jamis Buck [EMAIL PROTECTED]
wrote:
I wonder if it wouldn't be better to make something like
the '\\\', anyway? a\\\b gets
changed to:
a\
b
Would I break anything by changing \\\n to \\n in Command#process!
Thanks for your help,
Brian
On Apr 10, 11:34 am, Jamis Buck [EMAIL PROTECTED] wrote:
I suspect that's breaking because your line break is inside a quoted
string...and capistrano's escaping
You can specify a user specifically for the gateway in the hostname:
set :gateway, [EMAIL PROTECTED]
Alas, though, you can't set any other options that way...but note that
you can specify a list of keys to try when logging in:
ssh_options[:keys] = %w(/path/to/first/key /path/to/next/key
It's a quirk of Net::SSH that has never been patched. If anyone wants
to take a look and fix it, that'd be great. The problem might already
be fixed in Net::SSH v2 (due to be released in the near future), but I
haven't had a chance to verify.
- Jamis
On Apr 12, 2008, at 8:07 AM, Paul
:
I'd be willing to take a crack at it if you can point me in the right
direction and if it's not fixed in v2.
Paul
On Sat, Apr 12, 2008 at 10:39 AM, Jamis Buck [EMAIL PROTECTED]
wrote:
It's a quirk of Net::SSH that has never been patched. If anyone
wants to
take a look and fix it, that'd
I'm not sure what's going on there. You're sure you've got an ssh-
agent running locally? And, does git shell out to ssh under the
covers, or does it do it's own certificate validation? If the latter,
then forward-agent might very well have no effect, since forward-agent
only affects SSH
Weird, I've heard of Windows users running into that error, but even
in that case I don't know what causes it. If you figure it out, please
do report back. Sorry I can't be more helpful. :(
- Jamis
On Apr 13, 2008, at 2:35 AM, koba wrote:
Hello,
I managed to get Ruby, Mongrel, and
There is no such built-in support for deploying apps structured like
that. Yeah, it's definitely a strong...assumption, but I'd argue
against your choice of dubious to describe it. :) Any framework that
wants to be successful needs to have opinions, and you certainly can't
say that the
it, this would seem to be the case even if you has svn+ssh
access from each deploy target to the repo. So I guess I guess that
is normal then.
- Ken
On Apr 14, 2008, at 11:14 AM, Jamis Buck wrote:
I'm not sure what's going on there. You're sure you've got an ssh-
agent running locally
Nice! Thanks for sharing this tip.
- Jamis
On Apr 16, 2008, at 3:27 PM, shadowbq wrote:
ie. if you want to hard code in different users to execute as..
menu.choice :root do
set :user, :root.to_s
end
menu.choice :capistrano do
set :user, :capistrano.to_s
end
menu.choice
You'll need to walk the namespace tree and collect tasks, something
like this:
def walk_namespace(namespace, pattern, block)
namespace.tasks.each do |task|
block.call(task) if task.fully_qualified_name =~ pattern
end
namespace.namespaces.each do |ns|
Interesting, I can't duplicate this. If I add the following task to my
deploy.rb:
task :show_stage do
puts(stage)
end
and then invoke this:
cap production show_stage
it correctly prints production to my terminal.
Are you sure you've got the staging stuff configured right?
-
#
=
=
=
=
=
=
=
==
# default_run_options[:pty] = true
set :keep_releases, 3
require 'capistrano/ext/multistage'
require 'railsmachine/recipes'
On Apr 19, 11:02 pm, Jamis Buck [EMAIL PROTECTED] wrote:
Interesting, I can't duplicate
for your help and making such a great tool!
--
Matt
On Apr 19, 11:53 pm, Jamis Buck [EMAIL PROTECTED] wrote:
Ah, yeah. That'll fail, because when the variable is evaluated, the
multistage code has not yet been loaded. Be sure to load the
multistage extension as early as possible (after
setting
thought of
that (I kinda wondered how current_path was being eval'd, but never
put 2 and 2 together).
Thanks again,
--
Matt
On Apr 20, 12:31 am, Jamis Buck [EMAIL PROTECTED] wrote:
Yeah, I see what's going on now. Unfortunately, the stage variable
doesn't get set until you actually select
It looks like you're only creating the database.yml on deploy:setup.
Perhaps you really want it to be created after deploy:update_code? The
deploy:setup task is not called as part of the deployment task chain.
- Jamis
On Apr 21, 2008, at 8:36 AM, chris wrote:
I don't think that I am
Really? That seems very, very odd. What OS are you using? What version
of Ruby? I use puts() statements all the time, with no problems.
- Jamis
On Apr 21, 2008, at 11:39 AM, rAge wrote:
A few months ago I was having trouble with the following error:
** [deploy:update_code] exception
I suspect there's a key mismatch in the ~/.ssh/known_hosts file on the
remote host. If you log into the remote host and try to do an svn
checkout of your code, do you get the same error?
- Jamis
On Apr 23, 2008, at 6:21 PM, Sabotage Media wrote:
I'm currently doing set :deploy_via, :copy
If you are running without a pseudo-tty (the default), it _should_
autoload your profile info. However, all bets are off with Solaris--it
does so many things differently that I don't even try to keep up
anymore. :(
Note, though, that running without a pty can cause problems of its
own.
Check deploy:cleanup. By default it removes all but the five most
recently deployed versions.
cap --explain deploy:cleanup
- Jamis
On Apr 24, 2008, at 8:23 PM, growvotes wrote:
It seems like overkill to me to keep the old releases of my
application on my server and in my remote
The could not open direct channel error is the remote server saying
that it couldn't forward the connection. It could be that the hostname
you are using isn't recognized by the gateway as a valid server, or
that tcp-ip forwarding is disabled on the gateway's ssh server.
- Jamis
On Apr 25,
The *simplest* thing is to just show the entire command-line that was
used:
command_line = $0 + + ARGV.join( )
By way of explanation:
$0 - this will return the name of the script itself, as was given
on the command-line
ARGV - this is an array of command-line arguments that were
And I think I'd be just as likely to do it like this. :)
role :app, app1
role :db, app1, :primary = true
- Jamis
On Apr 28, 2008, at 2:12 PM, David Masover wrote:
And now that I've sent it twice... whoops.
role :db, :primary = true do
find_servers(:roles = :app).first.to_s
end
On
How is your deployment script being run automatically? Is it being run
as you, or a different user? When does it prompt for a password?
(Might it be prompting for an SSH certificate passphrase, which is not
the same as the password?)
- Jamis
On Apr 28, 2008, at 3:55 PM, Chuck wrote:
certificate, so I'm certain that's
not it.
Thanks,
Chuck
On Apr 28, 4:37 pm, Jamis Buck [EMAIL PROTECTED] wrote:
How is your deployment script being run automatically? Is it being
run
as you, or a different user? When does it prompt for a password?
(Might it be prompting for an SSH certificate
Are your mongrel instances already running before you cap deploy? If
not, you might want to do a 'cap deploy:cold' first. That, or (the
nearly equivalent) cap deploy:update deploy:start.
- Jamis
On Apr 29, 2008, at 9:28 AM, rejeep wrote:
Hi!
I have for a while now tried to set up
I'm not sure what it would take to make that build on windows, since
I'm not the author of fastthread. However, if your Ruby version is new
enough (a fairly recent patch release of 1.8.6), you can go into
capistrano/gateway.rb and remove the begin/rescue/end block from the
very top (where
Any chance you could share the definition of the umount_nfs_shares
task?
- Jamis
On Apr 29, 2008, at 2:16 PM, Chuck wrote:
Yes, but I've configured the group I'm a member of so that it doesn't
require a password when I use sudo with a NOPASSWD: ALL.
On Apr 29, 8:57 am, Jamis Buck [EMAIL
if [ `/sbin/ifconfig eth0 | grep inet | cut -d ' ' -f 12 | cut -
d ':' -f
2` = #{internal_db} ]; then sudo chown -R sms:mongrel /public; fi
run sudo chown -R user:group /var/www/blackbookmobile/
run sudo chmod -R g+w /var/www/blackbookmobile/
end
- Chuck
On Apr 29, 2:56 pm, Jamis Buck [EMAIL
to authenticate to the server with a password instead of
with a
public key.
On Apr 29, 3:26 pm, Jamis Buck [EMAIL PROTECTED] wrote:
Have you verified that sudo is configured right? For instance, add
the
following two tasks and see if both work without password prompts:
task
If you are using the default deployment recipes, you need to define a
spin script under your Rails script directory, which contains
instructions for spinning up (starting) your application. You can
read about it at http://capify.org/getting-started/rails (search for
script/spin on the
Those parameters don't get added to the role, but to each individual
server defined by that role declaration. If you want it, you'll need
to get the list of servers that match, but then you'll still need to
figure out which one of the :foo's you want, since you'll have
multiple servers
The :user variable does not have any effect on sudo. It only controls
who you are logging into your servers as, and who you are doing your
SCM operations as. To specify a specific user when sudo'ing, give
the :as option:
my_sudo_user = bob
sudo ..., :as = my_sudo_user
That will
Cap 2.1 comes with a git module prepackaged. Is the default one
insufficient?
In answer to your question, though, you want __FILE__, not FILE.
__FILE__ is a built-in constant that will always return the name of
the current source file.
- Jamis
On Apr 30, 2008, at 2:04 PM, Jordan Curzon
just me?
On Apr 30, 1:31 pm, Jamis Buck [EMAIL PROTECTED] wrote:
What do you mean by work? They all seem to load up fine for me.
- Jamis
On Apr 30, 2008, at 10:48 AM, [EMAIL PROTECTED] wrote:
Are there any pages (i.e. those listed
here:http://groups.google.com/group/capistrano/web
variable then?
On Apr 30, 1:30 pm, Jamis Buck [EMAIL PROTECTED] wrote:
The :user variable does not have any effect on sudo. It only controls
who you are logging into your servers as, and who you are doing your
SCM operations as. To specify a specific user when sudo'ing, give
the :as option
(or rather, forgetting
to rsync something locally).
Thanks for all the help Jamis!
On Apr 30, 5:59 pm, Jamis Buck [EMAIL PROTECTED] wrote:
It should be sufficient to set the user like this, outside of any
task:
set(:user) do
Capistrano::CLI.ui.ask(What user do you want to log
Louis,
I might be misunderstanding your question, but have you considered the
'multistage' extension to capistrano?
http://weblog.jamisbuck.org/2007/7/23/capistrano-multistage
You could then define your two deployment scenarios in separate files.
- Jamis
On Apr 30, 2008, at 8:29 AM,
I'm not 100% sure what the host key verification failed error is
about, but I suspect it is Subversion's SSH connection complaining
that it cannot verify the host key of the host it is trying to connect
to. Regarding passwordless authentication, you'll need to make sure
that you have your
to:
set :repository, svn+ssh://[EMAIL PROTECTED]/svn/#{application}/code/
ror/tags/quez/12
...then ran the cap task again but nothing changed, same error. Any
other ideas?
Thanks again for your help!
On Apr 30, 10:54 pm, Jamis Buck [EMAIL PROTECTED] wrote:
I'm not 100% sure what the host key
Yeah, I've heard other reports recently that the fastthread gem can be
difficult to build on windows. For now, the simplest solution is to
just find the capistrano/gateway.rb file in your capistrano
installation, and remove the begin/rescue/end block at the very top
(that tries to load
that the password input for the `su` command is magically
caught and read by Capistrano/Highline?
Sorry about the extra bother,
Edward
On May 1, 9:05 am, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Ah, ok, yeah, that makes a little more sense. Cool.
Thanks again Jamis.
On Apr 30, 6:38 pm, Jamis Buck [EMAIL
recommend?
Thanks again for your patience,
Edward
On May 1, 12:44 pm, Jamis Buck [EMAIL PROTECTED] wrote:
The simplest thing is to just make sure the entire deploy is done
by a
sudoer. If that's not possible for whatever reason, then you have to
reach into the bowels of capistrano to unplug
The --apply-to option no longer works in cap2. Instead, use the
'capify' command:
$ capify .
- Jamis
On May 1, 2008, at 2:58 PM, Mark A. Richman wrote:
So I got capistrano installed on my windows box, and my first attempt
to run cap --apply-to . on my rails directory resulted in this
Capistrano 2.3.0 is now available (though you never know how long it
really takes for the gem to propagate to the mirrors). You can read
all about what's new in the release announcement on my blog:
http://weblog.jamisbuck.org/2008/5/2/capistrano-2-3-0
Cheers!
- Jamis
(so I
don’t run into permissions issues down the road)?
Thanks again,
Edward
On May 1, 2:25 pm, Jamis Buck [EMAIL PROTECTED] wrote:
We run the mongrels as a different (non-sudoer) user. You can
accomplish that lots of ways, but one way is to set :use_sudo to true
(the default), and :runner
I'm still new enough to git that I'm not sure I can troubleshoot this
one with you. Anyone more experienced want to help Adam out? I'll
watch this one from the sidelines, and take notes.
- Jaims
On May 3, 2008, at 8:23 AM, Adam Salter wrote:
Hi,
Saw a post not that long ago about a SVN
the same basic set
of options, including :roles and :hosts. Those default to whatever
servers were defined for the task, for convenience's sake, but you can
override on a per-call basis, as I demonstrated.
- Jamis
On 3 May, 23:29, Jamis Buck [EMAIL PROTECTED] wrote:
The upload/download
sure Utahns everywhere appreciate the sentiment. The Idaho weather
is great, though. :)
- Jamis
On 4 May, 12:37, Jamis Buck [EMAIL PROTECTED] wrote:
On May 4, 2008, at 10:19 AM, [EMAIL PROTECTED] wrote:
Thinking about it again, in order to cover for the situation where
you’re updating
I've seen that message appear in the Net::SSH unit tests, but because
they never appeared in practice, I figured it was an artifact of the
tests. What version of Ruby do you have installed locally?
- Jamis
On May 4, 2008, at 1:39 PM, Michael Irwin wrote:
Using 2.3.0, deploying from OS X
On May 4, 2008, at 3:33 PM, Jeff wrote:
1. Just curious as to why cap doesn't use MultiSSH under the hood,
since the essence of capistrano (do stuff on multiple servers via ssh)
seems to be a natural fit for the purpose of MultiSSH as I understand
it (connect to multiple servers via ssh).
.
- Jamis
On May 4, 2008, at 9:50 PM, Jeff wrote:
On May 4, 4:55 pm, Jamis Buck [EMAIL PROTECTED] wrote:
On May 4, 2008, at 3:33 PM, Jeff wrote:
1. Just curious as to why cap doesn't use MultiSSH under the hood,
since the essence of capistrano (do stuff on multiple servers via
ssh)
seems
Right, sorry you had to dig to discover that. For others who may come
later, looking for this answer:
namespace :foo do
task :default do
end
task :bar do
end
end
The foo namespace has (in this case) two tasks, default, and
bar. Both may be invoked via foo:default
When you say restart manually, what does that entail? How does a
manual restart differ from how cap does it? Have you tried codifying
the manual restart process as a capistrano task?
- Jamis
On May 5, 2008, at 10:08 AM, rejeep wrote:
Hi, sorry for the delay.
I did as you said with the
Yeah, this is a known regression in Net::SSH 2.0, which I've fixed but
not yet released. In the meantime, you can work around it by putting
the following in your cap recipe:
ssh_options[:keys] = %w(~/.ssh/id_dsa ~/.ssh/id_rsa)
Sorry about that. I'll try to get the updated Net::SSH out
If not, what ssh server software are you connecting to?
- Jamis
On May 4, 2008, at 8:12 PM, Michael Irwin wrote:
It's the default Ruby that comes w/ Leopard:
ruby 1.8.6 (2007-09-24 patchlevel 111) [universal-darwin9.0]
On May 4, 4:27 pm, Jamis Buck [EMAIL PROTECTED] wrote:
I've seen that message
in
~/.ssh/config for some time, so it seems 2.3.0 just started noticing
it.
Thanks for your help, Jamis.
On May 5, 11:51 pm, Jamis Buck [EMAIL PROTECTED] wrote:
I can't seem to duplicate this...though to be honest I'm on 1.8.6
patchlevel 110 at the moment. Has anyone else seen this since
upgrading
Where is repos:setup defined? That's not a standard capistrano task.
- Jamis
On May 6, 2008, at 1:20 PM, Mark A. Richman wrote:
I'm trying to run cap repos:setup using a username with sudo access. I
get this error:
mkdir: cannot create directory '/var/www/apps/myproject/repos':
Can you refresh my memory? What is the bug that is manifesting?
- Jamis
On May 6, 2008, at 4:38 PM, matthooks wrote:
This is still present in 2.3. I fixed the bug by overloading the
deploy:stop task in my deploy.rb file:
namespace :deploy do
task :stop, :roles = :app do
# try_sudo
compression enabled in
~/.ssh/config for some time, so it seems 2.3.0 just started noticing
it.
Thanks for your help, Jamis.
On May 5, 11:51 pm, Jamis Buck [EMAIL PROTECTED] wrote:
I can't seem to duplicate this...though to be honest I'm on 1.8.6
patchlevel 110 at the moment. Has anyone else seen
For those of you that were getting bitten by the new Net::SSH (and
therefore, capistrano) not loading your id_dsa or id_rsa keys
automatically, you can now gem install net-ssh to grab Net::SSH
2.0.1, which fixes that issue.
- Jamis
--~--~-~--~~~---~--~~
To
Ah, yeah. That's currently the expected behavior of Net::SSH, but I
agree that it should not override 'user' if user is explicitly set.
I'd accept a patch for that, probably.
- Jamis
On May 7, 2008, at 11:39 AM, David James wrote:
$ cap -v staging shell
cap whoami
[establishing
and an SSH2 key and see how
they compare.
- Jamis
Cheers
George
On May 8, 1:05 am, Jamis Buck [EMAIL PROTECTED] wrote:
Is id_rsa.ppk an SSH1 key or an SSH2 key? Net::SSH (which is used by
Capistrano) only understands SSH2 keys, not SSH1. If you used ssh-
keygen to generate the key
Alright, the git SCM changes are getting out of hand (for me, anyway).
What works for one person doesn't work for another, and each
subsequent release of the git SCM for capistrano breaks things for
someone else. This isn't good!
So, I'd like someone well-qualified (with, you know, like 15
in ticket #6,
should I
just reopen that one and attach a note?
Best,
Patrick
On May 6, 2008, at 3:09 PM, Jamis Buck wrote:
Fair enough. I'm still new to git (and haven't needed to use git
with
capistrano yet), so I'll rely on the experience of those who do in
this case. I'm traveling
Tony,
Note that when you set a variable to a proc value, the value does not
get evaluated immediately--rather, it gets evaluated the first time
the variable is referenced. What you probably want is just this:
set :password, Capistrano::CLI.password_prompt(...)
set :intranet_login,
I suspect you've not configured your remote hosts for passwordless SSH
access to your git repository. Make sure you've got the public keys
set up on your remote host so you can do a git clone without a
password prompt there.
- Jamis
On May 10, 2008, at 5:10 AM, macace wrote:
Hi guys.
keys...
When I google it I dont get how they are doin that anny way..
as I said: big noobie at this..
Thank you for your repliy..
On May 10, 11:21 pm, Jamis Buck [EMAIL PROTECTED] wrote:
I suspect you've not configured your remote hosts for passwordless
SSH
access to your git repository
Just wanted to drop a note to the list and let everyone know that
Scott Chacon, author of the Git Internals peepcode PDF
(https://peepcode.com/products/git-internals-pdf
), has volunteered to help maintain capistrano's git SCM module. He'll
be acting as a filter for patches to that area of
Judging by this message:
*** [err :: herd.ida.liu.se] bash: line 1: sudo: command not found
I'd say that either sudo is not installed on the remote host, or is
not in the path on the remote host. Your options are to either install
it, or do without sudo:
set :use_sudo, false
- Jamis
You can probably turn off the ssh debugging -- it makes it hard to see
where the error messages are, and is rarely helpful in troubleshooting
issues like this. From what I can decipher, though, it looks like the
command finished successfully, though with warnings. Make sure your
mongrel
I'm not super familiar with mongrel_cluster. Anyone know how to tell
it to use the tmp/pids folder for pid files? AFAIK, it's something you
configure in mongrel_cluster.yml, but...
- Jamis
On May 14, 2008, at 8:58 AM, nico10gbb wrote:
When I execute : cap deploy:cold it looks like fine :
14, 2008, at 1:17 PM, macace wrote:
Well here I stand again
now I have fixed publickey-thingy...
guess what.. no change in the error message...
Anyone got some idea?
On May 11, 11:55 pm, Jamis Buck [EMAIL PROTECTED] wrote:
This is a pretty good site for explaining how to configure
That's a neat idea (and I LOVE the autogenerated documentation!), but
I'm not sure I like adding (1) another keyword, and (2) calling them
arguments, when they're really just variables that the task depends on.
What if this was implemented by extending the 'desc' keyword,
something like
Very concise! I love it. I'd love for Capistrano to have a way for you
to just specify what kind of configuration you're using, and have it
pick up the right task definitions. Not sure exactly what I mean by
that, but it seems like the current deploy.rb doesn't even really know
what setup
I disagree. You've certainly described *another* way to do it, but if
it means people have to actually set up those scripts themselves, your
way means additional (potentially confusing) setup is required for
people who want to use Capistrano, and that's what I'd like to avoid.
What I'd
of.
Another thing I monkey patched, was to support a fetch_or_default
method which set the variable to the default if it wasn't set (as
opposed to returning a default value for that call only)... If that
makes sense.
--gabe
On May 14, 5:10 pm, Jamis Buck [EMAIL PROTECTED] wrote:
That's a neat idea
Yeah, you'll need to reimplement deploy:restart, deploy:start, and
deploy:stop, in your deploy.rb. I'd provide an example, but I don't
use mongrel_rails directly like that, so I'd be sure to get it wrong.
- Jamis
On May 14, 2008, at 5:43 PM, Andrew Grimm wrote:
My shared hosting provider
I'd start by making sure the /var/www/apps/application/shared/log
directory is writable by the user doing the deploy.
- Jamis
On May 15, 2008, at 12:41 AM, JoeRails wrote:
I am trying to deploy an application in railsmachine that has ferret
installed. when i run the cap deploy:cold i get
Do you have pageant.exe running? Have you told it about your id_rsa key?
Alas, there isn't a mailing list for net-ssh (yet, though the volume
of requests is rising and I might create one soon). For now, just
email me directly with the output of your script when debugging is
enabled:
that, in theory, you can deploy the same
way to any remote host.
I'm not going to actually state a preference, just pointing out
where I think the disconnect is.
On Thu, May 15, 2008 at 9:10 AM, Jamis Buck [EMAIL PROTECTED]
wrote:
I disagree. You've certainly described *another* way to do
Capistrano 1.4.1 and earlier, and capistrano 2.1 and earlier, do not
work if you have net-ssh 2.x installed. You must install capistrano
1.4.2 or 2.2 in order to use capistrano. Capistrano 2.3 uses net-ssh
2, but the others do not, so if you don't need net-ssh 2 for something
else, you
You can do gem uninstall net-ssh and it will prompt you for the
version.
- Jamis
On May 16, 2008, at 2:28 PM, Ken wrote:
What is the exact syntax to uninstall net-ssh? Would it be gem
uninstall net-ssh -v 2.0.1?
Thanks, Ken
On May 16, 1:17 pm, Jamis Buck [EMAIL PROTECTED] wrote
Note that a task is not executed once per matching server, it is
executed once, for all matching servers. So, depending on what you need:
1. You simply want the host name to appear somewhere in a command
you're running in the current task:
run echo server is $CAPISTRANO:HOST$
The
Try adding this to your capfile:
ssh_options[:keys] = /path/to/identity_file
- Jamis
On May 19, 2008, at 8:46 AM, eric wrote:
Hello all,
I am trying to deploy to a staging server that is on EC2. I seem to
be having an issue when running the cap deploy:setup command.
Normally when I SSH
This ticket (http://capistrano.lighthouseapp.com/projects/8716/tickets/
5) was opened a couple weeks ago because of this same issue, where
someone wants capistrano to ask the remote host what the revision is,
rather than the local host. Feel free to post your comments there;
perhaps an idea
be incredibly hacky, but I suppose that you could do some
sort
of analysis of the /etc/sudoers file to figure out if the logged in
user
was restricted to a specific command set.
I'll keep thinking about it.
Wes
Jamis Buck wrote:
I apologize for that. This issue you're encountering is caused
2.3.0 with capistrano-ext 1.2.0, both
freshly updated via gem today.
I'm new to this, so I'm probably missing something; any ideas?
Ben
On May 20, 9:38 pm, Jamis Buck [EMAIL PROTECTED] wrote:
Ben,
It sounds like you want the :on_error = :continue option for the
task:
task :add_user
601 - 700 of 1085 matches
Mail list logo
