The freeze task does a clone into vendor/radiant as opposed to adding
it as a submodule. To put it in as a submodule first unfreeze (i.e.
delete vendor/radiant) then try
git submodule add git://github.com/radiant/radiant.git vendor/radiant
Then on a new deployment you'll need to run
git submodule init
git submodule update
I'm guessing that's what `:git_enable_submodules, 1` tries and fails
to do. So you may never need to manually run the last two commands.
On 2008/09/25, at 13:17, Peter Berkenbosch wrote:
I'm currently working on another radiant instance and I'm using
github.
I freezed the edge of radiant in my project, in my github account I
can see
a link in vendor/radiant but thats it..
When I do a deploy, the code inside vendor/radiant is not checked-
out..
(euh... pulled)
I tried to add set :git_enable_submodules, 1 to my capistrano
deploy.rb, but
this is giving met the following error:
No submodule mapping found in .gitmodules for path 'vendor/radiant'
I will investigate further... looking for a .gitmodules for example..
But anyone with a solution?
Thanks.
--
met vriendelijke groet,
Peter Berkenbosch
_______________________________________________
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
_______________________________________________
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
