"hg archive" with remote URL

[Mutlu Dogruel]

On 8 Aug 2013, at 13:19, "Kastner Masilko, Friedrich" <kastner-masilko at at.festo.com> wrote:

>> From: mercurial-bounces at selenic.com [mailto:mercurial-bounces at selenic.com] On Behalf Of Mutlu Dogruel
>> 
>>>> Is there any plan to support "hg archive" with remote URLs, as in:
>>>> 
>>>> git archive --remote=ssh://git@bitbucket.org/username/reponame.git
>>>> --format=tar --output="file.tar" master
>>> 
>>> Definitely not. We intentionally restrict the set of things you can
>> do
>>> with remote repositories to push and pull so that people are forced
>> to
>>> do everything else locally.
>>> 
>> 
>> So what would your preferred method of getting project code be in an
>> automated customer-side product deployment?
> 
> _Especially_ in an automated customer-side product deployment scenario I wouldn't want them to install git locally and SSH into my repository server. I'd rather have them downloading zip archives from my authorizing web-server via something like wget and HTTPS, and this is easy enough with hgweb's archive feature. Having customers installing a DVCS to get started with deployment is a no-no IMHO.
> 
> Regards,
> Fritz

I agree, but not everyone may want to keep a web server only for this reason, especially if your code is already on Bitbucket. We use Bitbucket but it does not allow the use of curl/wget with private/public key authentication at the moment. This works:

curl --digest --user my_name:my_password https://bitbucket.org/user/repo/get/master.zip -o master.zip

But it's not very ideal to supply a user name & password from your customer's machine. A project specific private key that can be revoked later is the way to go IMHO.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20130808/ff2373c5/attachment-0002.html>