Re: [PATCH 1/6] gittutorial doc: replace "alice" and "bob" with "you" and "www-data"

[Bagas Sanjaya <bagasdotme@gmail.com>]

On 15/06/21 23.17, Ævar Arnfjörð Bjarmason wrote:
> -Suppose that Alice has started a new project with a Git repository in
> -/home/alice/project, and that Bob, who has a home directory on the
> -same machine, wants to contribute.
> +Suppose that you've started a new project with a Git repository in
> +/home/you/project, and you'd like another user on the same local
> +machine to be able to contribute to it. E.g. a www-data user to serve
> +the content up with a webserver.
>   
> -Bob begins with:
> +As the `www-data` user do:
>    >   ------------------------------------------------
> -bob$ git clone /home/alice/project myrepo
> +www-data$ git clone /home/you/project /var/www-data/deployment
>   ------------------------------------------------
> 

This assumes that we're on Debian or its derivatives, however many users 
run Git on other distributions (Fedora, Arch, Gentoo, openSUSE, etc.), 
so `www-data` user may not be present there. Also, `www-data` is system 
account, as opposed to normal user account, so you can't log in to it; 
you need as root `chown -R www-data:www-data /somewhere/`.

This also assumes that we use Apache HTTPD. The setup for other 
webservers may be different. For example, if NGINX is used (installed 
from upstream packages rather than from Debian package repository), you 
need to make site root (the path specified in `root` directive) readable 
by `nginx` user.

> -This creates a new directory "myrepo" containing a clone of Alice's
> +This creates a new directory "deployment" containing a clone of your
>   repository.  The clone is on an equal footing with the original
>   project, possessing its own copy of the original project's history.
>  

But the scenario is we're cloning from local repo, so `git clone` here 
implies --local (and bypasses normal Git transport mechanism), so to get 
clone experience similar to when using remote repo, we can use 
--no-local instead.

> -Bob then makes some changes and commits them:
> +As `www-data` you then makes some changes and commit them:
>   
>   ------------------------------------------------
>   (edit files)
> -bob$ git commit -a
> +www-data$ git commit -a
>   (repeat as necessary)
>   ------------------------------------------------
>   
> -When he's ready, he tells Alice to pull changes from the repository
> -at /home/bob/myrepo.  She does this with:
> +You can then pull those changes to the checkout in your home directory
> +at /home/you/project:
>   
>   ------------------------------------------------
> -alice$ cd /home/alice/project
> -alice$ git pull /home/bob/myrepo master
> +you$ cd /home/you/project
> +you$ git pull /var/www-data/deployment master
>   ------------------------------------------------
>   

The resulting rewrite until this point makes no sense for me. Previously 
we have Alice and Bob working the project, but now you do the same, one 
as normal user account and one as system user `www-data`. Honestly I 
would like keeping the status quo.

-- 
An old man doll... just what I always wanted! - Clara