/app.com/current.
Now when Cap tries to bundle it can't find the Gemfile because its not
looking one directory deeper into the current symlink.
Is this a CloudForge issue or Net-SSH or how do I fix this? Can't find
anything I can set to tell Cap where to look.
Thanks
Matt
--
You received
-darwin13.0.0]
rake: rake, version 10.1.1
vagrant: Vagrant 1.4.2
os: Darwin MattbookPro.local 13.0.2 Darwin Kernel Version 13.0.2: Sun Sep
29 19:38:57 PDT 2013; root:xnu-2422.75.4~1/RELEASE_X86_64 x86_64
Thanks
Matt
--
You received this message because you are subscribed to the Google Groups
Hi,
I have an example using SSHKit:
# ssh-kit-test.rb:
require 'sshkit'
require 'sshkit/dsl'
on 'example.com', user: 'matt' do
within('current') do
puts this works as expected:
puts capture :ls
puts this does not get executed in the 'current' directory:
puts capture 'ls -l
I have an example script here: https://gist.github.com/mattconnolly/8212674
I can see in the code that it is bypassing all of the `with`, `within`,
`user` etc conversions when the command has a space in it.
I would have expected that commands that are not mapped would have the same
treatments
and look forward to seeing what you create!
Thanks,
--
Matt
On Tuesday, January 3, 2012 at 3:58 PM, Lee Hambley wrote:
Matt,
Certainly, continuous deployment is a luxury few of us are afforded, I've
mostly worked at places where the deploy is weekly, and that's as agile as we
can
if
there's a way to disable migration running on moonshine?
In any rate, it seems like it would best be done the other way around -
`cap deploy` does migrations, too, and `cap deploy:nomigrations` does what
it says. Is there something I'm missing?
Thanks,
--
Matt
--
* You received this message
of people out
there doing different deploy methods and I failed to take that into account.
Thanks,
--
Matt
On Tuesday, January 3, 2012 at 11:56 AM, Donovan Bray wrote:
Because if you want to deploy with migrations there's a task for that
deploy:migrations
That gives you the ability
I wrote a lovely missive about what I was doing by accidentally mailed
it directly to Lee. Dang it.
I actually do not want to run it serially, but functionally it doesn't
really matter if I do for this task. It would be nice to know how to
do this.
It all really boils down to the problem of
I am trying to use the 'run' directive in cap and having a devil of a
time dealing with nested single and double quotes. I come from the
world of Perl so I cannot fathom how similar formatting can be
achieved in Ruby.
Here is what I am doing:
My first example works as the command is not riddled
I am trying to make a task that executes all tasks in a namespace.
Because the tasks will be defined at execution by an array that
changes, I need to make this work so that I can call each task of the
namespace dynamically.
This is what I mean:
http://pastie.org/2634167
... but there is not
The behavior of the deploy:cleaup task appears to be that when given a
list of servers, at the first server it encounters with nothing to
clean up it stops without checking the rest of the servers on the
list. Why is this and is there a workaround to force it to check all
servers that are supplied
is called when stuff
is rolled-back. Is there a global rollback task I can hook into, or some
other way to detect when a deploy fails? I'd like to do it within cap and
not outside...
Thanks,
--
Matt
--
* You received this message because you are subscribed to the Google Groups
Capistrano group
Good luck fellas
On 2 July 2010 19:10, Lee Hambley lee.hamb...@gmail.com wrote:
Matt,
Not sure - I know Jamis still controls the DNS, and he points it at a VPS
box that I run… can't tell you anything more than that… Reverse DNS on the
i...@zenom reported does still point to my ISP… I'll
Brent, which bit in particular did you want? Was it the order of the
commands you use to setup the remote system right at the start?
2009/9/30 sbfaulkner bre...@unwwwired.net:
oh well, I guess it's gone then, 'cause that's not it.
On Sep 30, 3:01 pm, Lee Hambley lee.hamb...@gmail.com
Brent, I'm with you brother. I also missed the doc when it went, but
after looking through the new docs, and using cap -T, I managed to
muscle my way through it, and learned a bit about it on the way.
Reckon you and I can rewrite the steps? I'm sure there's people on
here will put us right if
Thanks Rafa
That does make a hell of a lot more sense
V
2009/9/24 Rafael G. r...@aspgems.com:
If I understood, only with add machineB to role :app should works:
role :app, machineA, machineB
role :web, machineA
role :db, machineA, :primary = true
namespace :deploy do
desc Restarting
I had a similar sort of problem but it turned out that I hadn't run
the cap deploy:setup properly.
Don't ask me how
2009/6/29 Lee Hambley lee.hamb...@gmail.com:
Josh,
Did you recently start using git? I suspect the tmp/ directory doesn't
exist... Git won't track empty directories.
- Lee
Interesting. I'll definitely consider that. The solution I just came
up with involves using: grep -v www
I'm curious about why you're strongly recommending against using the
defaults? There must be something bigger I'm not thinking about...
Matt
On Mar 5, 2:36 pm, Jamis Buck ja
OK, I've suddenly started to get this error when attempting to deploy
a branch, and after a little investigation, I have found that the
query_revision function in git.rb is attempting to compare a string
(the branch name) with a symbol (the branch name as a symbol) on this
line:
if
Cool, thanks Jamis, that worked perfectly.
I wonder if this is something that should be worked around in core
capistrano since I'd imagine long running migrations would also cause
this problem (for those with short tcp tmeouts anyway)
Matt
on using this
as a keep-alive mechanism on the client side?
Matt
On Jul 14, 10:53 pm, matt [EMAIL PROTECTED] wrote:
Nope,
ClientAliveInterval 15
ClientAliveCountMax 15
gives the following stack trace every time in the same place (when it
tries to restart the 3rd of 3 app server instances
I am trying to deploy a site using capistrano with git. I can do the
cap deploy:setup, that works OK. Then I invoke a cap deploy:check,
which at the very end says the following:
The following dependencies failed. Please check them and try again:
-- `/home/entouchd/git' could not be found in
/execute.rb:14:in `execute'
from /usr/local/lib/ruby/gems/1.8/gems/capistrano-2.4.0/bin/cap:4
from /usr/local/bin/cap:19:in `load'
from /usr/local/bin/cap:19
Any help appreciated, thanks,
Matt
--~--~-~--~~~---~--~~
To unsubscribe from this group
no longer alive.
Matt
--~--~-~--~~~---~--~~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~--~~~~--~~--~--~---
I recently moved my rubber deployment plugin to github. For those
new
to rubber, it enables relatively complex multi-instance deployments
of
rails apps to Amazon’s Elastic Compute Cloud (EC2). See the wiki
page
on github for more details.
http://github.com/wr0ngway/rubber/wikis
I'm getting this error as well. If I modify the lines that use
#{stage} (so they don't error out) and plug in the task :show_stage,
the correct stage is spit out. It's only when I'm using them in string
eval set(:bar) {#{stage}} that they are not coming thru.
# each of the deploy/#{stage}.rb
# is
bumped up a bit! ;))
Thanks 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
FYI:
gem list --local | grep cap
capistrano (2.2.0, 2.1.0, 2.0.0, 1.4.1)
capistrano-ext (1.2.0)
and cap -V gives 2.2.0
On Apr 19, 11:59 pm, Matt R [EMAIL PROTECTED] wrote:
I modified the file to look like:
set :stages, %w(dev staging production)
set :default_stage, 'dev'
require
Jamis,
That did it for me!! Thanks for your help, would've never 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
they belong
to.
The README for the project is at: http://rubber.rubyforge.org/svn/trunk/README
It should be trivial to demo it using the steps outlined therein - if
not, then I broke something, so please let me know :)
Matt
On Jan 11, 3:29 pm, David Masover [EMAIL PROTECTED]
wrote:
Working on a way
feedback appreciated, but check the TODO first :)
Matt Conway
http://simplygenius.com
--~--~-~--~~~---~--~~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~--~~~~--~~--~--~---
', 'host2']) do
run echo hi
end
end
Hope this helps,
Matt
On Jan 19, 3:55 pm, Dick Davies [EMAIL PROTECTED] wrote:
Hi all
I finally took the time to try out capistrano yesterday - been meaning
to since it was switchtow*r -
and I really wish I'd tried it years ago :)
It'll be really handy
for the heap of questions. I just need prodding in the right
direction :-)
TIA,
Matt.
--~--~-~--~~~---~--~~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~--~~~~--~~--~--~---
If I execute something like:
ROLES=web HOSTS=web01 cap deploy:start
the start_search task gets executed even though it is tied to
the :search role. This doesn't happen if I don't restrict the scope
using ROLES/HOSTS. Any workarounds known for this?
The relevant parts of my deploy.rb are:
on a machine they weren't
intended for.
Matt
On Sep 12, 4:32 pm, Jamis Buck [EMAIL PROTECTED] wrote:
Oh, I see what you were saying. Yes, specifying ROLES or HOSTS as
environment variables will override the restrictions for all tasks
that get executed, not merely the top-level task.
- Jamis
all remote commands through taskset, but I
don't know the cap internals well enough to try this myself.
http://blog.mecworks.com/articles/2007/02/13/cpu-affinity-how-to-work-around-broken-ssh-on-smp-machines-using-taskset/
Matt
!
Matt
--~--~-~--~~~---~--~~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~--~~~~--~~--~--~---
Hey thanks Jamis, unfortunately that doesn't seem to work. What do you
recommend I do if I don't want the username and password to appear when the
command gets executed?
Matt
On 6/27/07, Jamis Buck [EMAIL PROTECTED] wrote:
You can do something like
require 'capistrano/shell'
class
/releases/20070627152315
(echo 1168
/usr/local/projects/project-x/releases/20070627152315/REVISION)
servers: [some-domain.com]
[some-domain.com] executing command
Matt
On 6/27/07, Jamis Buck [EMAIL PROTECTED] wrote:
Perhaps I'm misunderstanding how you are using this. Are you using
cap
= message.gsub(/--password (\S+)/, --password filtered)
previous_log_method level, message, line_prefix
end
end
Matt
On 6/27/07, Jamis Buck [EMAIL PROTECTED] wrote:
Ah, ok. You're not using the cap shell, then. Capistrano::Shell is
used _only_ for the cap shell task, when you are starting
Hi,
I'm using Capistrano for non-Rails deployment. I'd like to be able to use
just the Capfile and not config/deploy.rb. The problem is that Capfile
doesn't have an extension so text editors don't recognize it as Ruby. Would
it be possible to get it so Capistrano also loads a Capfile.rb?
Matt
41 matches
Mail list logo
