<sigh> so here's where things are failing for me now. This seems like it's
specific to capistrano and not radiant :/
* executing `deploy:update_code' updating the cached checkout on all
servers
executing locally: "git ls-remote g...@github.com:fleshins/radiant.git
master"
* executing "if [ -d /var/www/html/radiant/shared/cached-copy ]; then cd
/var/www/html/radiant/shared/cached-copy && git fetch -q origin && git reset
-q --hard 04edfa7f2f3f00635ac7dcda343ab891cf06fd68 && git submodule -q init
&& for mod in `git submodule status | awk '{ print $2 }'`; do git config -f
.git/config submodule.${mod}.url `git config -f .gitmodules --get
submodule.${mod}.url` && echo Synced $mod; done && git submodule -q sync &&
git submodule -q update && git clean -q -d -x -f; else git clone -q
g...@github.com:fleshins/radiant.git /var/www/html/radiant/shared/cached-copy
&& cd /var/www/html/radiant/shared/cached-copy && git checkout -q -b deploy
04edfa7f2f3f00635ac7dcda343ab891cf06fd68 && git submodule -q init && git
submodule -q sync && git submodule -q update; fi"
I tried running this locally on the target server and got a syntax error.
<sad face> :P
On Fri, Dec 17, 2010 at 1:22 PM, Fima Leshinsky <flesh...@gmail.com> wrote:
> hm .. so it looks like git is placing the submodules (extensions) located
> in vendor/extensions in shared/cached-copy instead of the 'current'
> directory . do i need to symlink the extensions from the shared directory to
> 'current'?
>
>
> On Fri, Dec 17, 2010 at 11:06 AM, Fima Leshinsky <flesh...@gmail.com>wrote:
>
>> ok so the log file error is due to the log file not existing in my shared
>> directory - not sure how to address it but probably not a show stopper
>>
>> the extension errors appear to be due to me not using Git properly? I
>> found a thread that discusses having to use Git submodules to manage
>> extensions .. going to play with that and see what happens :P
>>
>
