| 1 |
On 11/06/2011 06:49 PM, Pandu Poluan wrote: |
| 2 |
> |
| 3 |
> On Nov 4, 2011 10:17 PM, "Michael Orlitzky" <michael@××××××××.com |
| 4 |
> <mailto:michael@××××××××.com>> wrote: |
| 5 |
>> |
| 6 |
>> On 11/04/2011 11:00 AM, Pandu Poluan wrote: |
| 7 |
>> > I'm looking for a nice, lightweight way to implement a Mercurial server. |
| 8 |
>> > Somehow, installing a heavyweight webserver just for Mercurial seems |
| 9 |
>> > so... wasteful. |
| 10 |
>> |
| 11 |
>> If it's not for public use, you can clone/pull/whatever over SSH. |
| 12 |
>> |
| 13 |
> |
| 14 |
> That's news to me... so I don't have to install a Mercurial server at all? |
| 15 |
> |
| 16 |
|
| 17 |
Nope. |
| 18 |
|
| 19 |
$ hg help urls |
| 20 |
URL Paths |
| 21 |
|
| 22 |
Valid URLs are of the form: |
| 23 |
|
| 24 |
local/filesystem/path[#revision] |
| 25 |
file://local/filesystem/path[#revision] |
| 26 |
http://[user[:pass]@]host[:port]/[path][#revision] |
| 27 |
https://[user[:pass]@]host[:port]/[path][#revision] |
| 28 |
ssh://[user[:pass]@]host[:port]/[path][#revision] |
| 29 |
... |
| 30 |
|
| 31 |
|
| 32 |
There's a section in there about SSH URLs you'll probably want to read. |
| 33 |
You need Mercurial installed on the server machine, and its path |
| 34 |
handling is a little weird if you're used to another SCM. |
| 35 |
|
| 36 |
Works fine without a web server, though. |
Archives