"hg archive" with remote URL

[Mutlu Dogruel]

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

>> From: Mutlu Dogruel [mailto:mutludogruel at gmail.com] 
>> 
>> 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.
> 
> Or just create a BB account for your customer and revoke access for this user to your repo later on. Compared to forcing your customer to install a DVCS, this is a much simpler solution IMHO.
> 
> Or do you perhaps struggle with the 5 user free account limitation? If so, I'd suggest purchasing a plan and paying BB for their service. Maybe a suggestion of having private/public key authentication for archive downloads will then have a chance of making it through, too.
> 
> Regards,
> Fritz
> 

I think you misunderstood. I was talking about automatic deployment as in Opscode Chef cookbooks in which there is no manual installing as such. Basically, it's a script running on a remote machine that does all the installations, fetching code from repositories etc. It makes it easy to setup clusters in cloud computing platforms, for example. If you are using the "curl" solution, you have to pass the user name & password to the script somehow (one solution is the use of encrypted databags in Chef recipes). But ideally, key-based authentication would work best in such setups. Having to manage temporary user names & passwords on a project basis is not an elegant solution.

Btw, we are a paying BB customer, and I have already requested this feature from them.  Anyway, thanks for the suggestions. Looking forward to hearing from the Bitbucket team.

Best regards,
Mutlu