I have never had this problem before, but when I try to do a cap
deploy:update, after a setup and a check that passes, it gives this
error: failed: sh -c \touch /home/deployer/apps/staging/current/tmp/
restart.txt\
This never seemed to be a problem and I have yet to solve it. Any
ideas?
Josh,
Did you recently start using git? I suspect the tmp/ directory doesn't
exist... Git won't track empty directories.
- Lee
2009/6/29 Josh josh.rach...@gmail.com
I have never had this problem before, but when I try to do a cap
deploy:update, after a setup and a check that passes, it gives
I don't know git (I use it for basics things) but could you put your
octave code as external in your rails app?
Joshua wrote:
It resides as two subdirectories of a single git repository.
E.g.,
root/.git
root/my-nifty-rails-app
root/a-pile-of-octave-code-and-libraries
I would expect this would work quite nicely if they were in two repositories
(if you are thinking of them as two separate pieces of code). Then app A)
could treat app B) as submodule
2009/6/29 Rafael G. r...@aspgems.com
I don't know git (I use it for basics things) but could you put your
When I said external I want to said external repository (as in
subversion). When you update your rails app then your external
repository will be updated too.
So you don't need try to set two repositories in capistrano.
Lee Hambley wrote:
I would expect this would work quite nicely if they
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
Josh,
Since cap:deploy:setup can, unless you have disabled it use sudo, it's
entirely possible that your deploy user doesn't have permission to write to
the directories it has setup, there're two options; one check the
permissions on the directories that deploy:setup makes, or alternately, add
Mathias Meyer wrote:
On Fri, Jun 19, 2009 at 10:12 PM, Joe
McDonaghjoseph.e.mcdon...@gmail.com wrote:
Hi, I have a simple web push I want to do, and it looks like it works
fine, but it's not a rails app so there should be no app or db role. How
do I tell deploy.rb that?
Just set
Joe,
Can you paste the exact error?
- Lee
2009/6/29 Joe McDonagh joseph.e.mcdon...@gmail.com
Mathias Meyer wrote:
On Fri, Jun 19, 2009 at 10:12 PM, Joe
McDonaghjoseph.e.mcdon...@gmail.com wrote:
Hi, I have a simple web push I want to do, and it looks like it works
fine, but it's not
Do you always need to deploy both together?
Might you ever want to deploy them separately?
On Jun 29, 2009, at 5:08 AM, Lee Hambley wrote:
I would expect this would work quite nicely if they were in two
repositories (if you are thinking of them as two separate pieces of
code). Then app
I'd rather keep them in a single repository just because of the
headache of managing lots of repositories - the repository they are in
is already one of a number of repositories..
It seems like it'd be nice if the notion of a package/module was
distinct from the notion of a repository.
Josh
On
Sometimes I only change one of them and not both, so yes, I can
imagine only wanting to deploy one.
On the other hand, they are both pretty small, so I don't mind
treating them as a single unit from a deployment perspective.
Josh
On Jun 29, 12:52 pm, Peter Booth pbo...@nocoincidences.com wrote:
12 matches
Mail list logo
