[chef] Re: Application cookbook -- using Mercurial SCM provider

[Cassiano Leal < >]

It would help if you included the error you're getting.

Guessing from the questions you asked, I'd say that the SSH key should be 
passphrase-less since Chef will run unsupervised.

-
Cassiano Leal


On Jun 4, 2013, at 16:50, Liam Kirsher 
<
 >
 wrote:

> Hi --
> 
> I'm using the Application / Application_python cookbook to install Django.
> The app source code lives in a Mercurial repo (which happens to be
> private).
> I need a little help here on how to do this.  This is what I've got, but
> it's not working.
> 
> Does anyone have an example of how to do this?
> 
> How do I correctly reference the Mercurial provider?
> I have verified that hg clone works with that url.
> Does the ssh private key have to omit a passphrase?
> I think the file referenced by deploy_key has to be uploaded somehow as
> part of the cookbook.
> 
>> application "bart" do
>>  path "/srv/bart"
>>  owner "nobody"
>>  group "nogroup"
>>  scm_provider "Chef::Provider::Mercurial"
>>  repository 
>> "ssh://
 /bart/server/bart"
>>  revision "master"
>>  deploy_key "/home/liam/.ssh/bti"
>>  migrate true
>>  packages ["libpq-dev", "git-core", "mercurial"]
> 
> Thanks!
> Liam
> 
> -- 
> Liam Kirsher
> PGP: http://liam.numenet.com/pgp/
>