- From: Noah Kantrowitz <
>
- To:
- Subject: [chef] Re: Application cookbook -- using Mercurial SCM provider
- Date: Tue, 4 Jun 2013 14:37:24 -0700
On Jun 4, 2013, at 12:50 PM, 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"]
This is not currently possible :-( You can look at the pypy-home cookbook in
github.com/python/psf-chef for my best effort (using a forked version of the
hg cookbook, take note) but it is still super flaky.
--Noah
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail
Archive powered by MHonArc 2.6.16.