server in the cloud

[Giovanni Gherdovich]

[Forwarding to the list, I replied to Mike alone, unintentionally]

---------- Forwarded message ----------
From: Michael Mossey <michaelmossey at gmail.com>
Date: 2014/1/21
Subject: Re: server in the cloud
To: Giovanni Gherdovich <g.gherdovich at gmail.com>


On 1/21/2014 1:59 AM, Giovanni Gherdovich wrote:
>
>
> but I would not recommend it unless you have some
> sysadmin skills and strong confidentiality requirements that would make
you not
> trust a free mercurial hosting service like https://bitbucket.org/
> (where, btw, you can even have "private repositories",
> that possibly prevent you from the casual internet visitor
> looking at your code, if you really don't want that to happen).
>
> so: read some bits from the docs above,
> sign up to bitbucket.org, create a repo and you're ready to go.

Ah, that's exactly what I was looking for, this bitbucket.org. Thanks,
Mike


---------- Forwarded message ----------
From: Giovanni Gherdovich <g.gherdovich at gmail.com>
Date: 2014/1/21
Subject: Re: server in the cloud
To: Michael Mossey <michaelmossey at gmail.com>


:::: Sorry to ask what might be a basic question, but I

:::: understand so little about Mercurial that the documentation
:::: makes little sense to me, and Google doesn't bring up
:::: anything relevant.

If you plan to use Mercurial, you will have to learn a little about it.
Here some places to start:

a tutorial you can follow
http://hginit.com/

a free book you can use as reference:
http://hgbook.red-bean.com/

::::
:::: I'm working on a small programming project with one other

:::: programmer (happens to use WinPython). We need some form
:::: of version control, in particular to share work that we
:::: do at different sites. We each have a Windows 7 laptop.
::::
:::: We also each have web domains hosted on one of those basic
:::: providers (in my case, MidPhase).

ok, you -could- use -one- of your two servers as a "central store"
to share code, provided that both of you have SSH access to it.
Your workflow would be something like

bob at bobsplace$ hg clone ssh://bob@server/path/to/repo
/* bob edits code */
bob at bobsplace$ hg commit
bob at bobsplace$ hg push

alice at alicesplace$ hg pull ssh://alice@server/path/to/repo
/* alice edits code */
...

but I would not recommend it unless you have some
sysadmin skills and strong confidentiality requirements that would make you
not
trust a free mercurial hosting service like https://bitbucket.org/
(where, btw, you can even have "private repositories",
that possibly prevent you from the casual internet visitor
looking at your code, if you really don't want that to happen).

so: read some bits from the docs above,
sign up to bitbucket.org, create a repo and you're ready to go.

::::
:::: Can we use Mercurial? I understand it's considered

:::: "distributed" version control, but the most important
:::: thing that we need to be able to do is share code with
:::: each other when we are at different sites.
::::
:::: Mike


Cheers,
GGhh




2014/1/21 Michael Mossey <michaelmossey at gmail.com>

> Sorry to ask what might be a basic question, but I understand so little
> about Mercurial that the documentation makes little sense to me, and Google
> doesn't bring up anything relevant.
>
> I'm working on a small programming project with one other programmer
> (happens to use WinPython). We need some form of version control, in
> particular to share work that we do at different sites. We each have a
> Windows 7 laptop.
>
> We also each have web domains hosted on one of those basic providers (in
> my case, MidPhase).
>
> Can we use Mercurial? I understand it's considered "distributed" version
> control, but the most important thing that we need to be able to do is
> share code with each other when we are at different sites.
>
> Mike
>
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20140121/ccdaea9e/attachment-0002.html>