Changeset b4be4cf1


Ignore:
Timestamp:
01/08/2021 06:46:05 PM (8 months ago)
Author:
Bruce Dubbs <bdubbs@…>
Branches:
10.1, 11.0, qt5new, trunk, xry111/git-date, xry111/git-date-for-trunk, xry111/git-date-test
Children:
7c9ae62
Parents:
c5e3c1c
Message:

More tweaks to git server page

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@24092 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:
1 edited

Legend:

Unmodified
Added
Removed
  • general/prog/gitserver.xml

    rc5e3c1c rb4be4cf1  
    7777        For any developer who should have access to the repository
    7878        add his/her public ssh key to <filename>/home/git/.ssh/authorized_keys</filename>.
    79         First, prepend some options to prevent users to use the
     79        First, prepend some options to prevent users from using the
    8080        connection to git for port forwarding to other machines
    8181        the git server might reach.
     
    117117      </para>
    118118
     119      <note>
     120        <para>
     121          In all the instructions below, we use <emphasis>project1</emphasis>
     122          as an example repository name.  You should name your repository
     123          as a short descriptive name for your specific project.
     124        </para>
     125      </note>
     126
    119127<screen role="root"><userinput>install -o git -g git -m755 -d /srv/git/project1.git &amp;&amp;
    120128cd /srv/git/project1.git                             &amp;&amp;
     
    127135      <title>3. Populate the repository from a client system</title>
    128136
     137      <note>
     138        <para>
     139          All the instructions in this section and the next should
     140          be done on a user system, not the server system.
     141        </para>
     142      </note>
     143
    129144      <para>
    130145        Now that the repository is created, it can be used by the
     
    150165        to the repository as the initial content:
    151166      </para>
     167
     168      <note>
     169        <para>
     170          The <emphasis>gitserver</emphasis> term used below
     171          should be the host name (or ip address) of the git server.
     172        </para>
     173      </note>
    152174
    153175<screen role="nodump"><userinput>mkdir myproject
     
    199221        <filename>authorized_keys</filename> file and there is no
    200222        option for the public to export/clone the repository. To
    201         enable this, continue with step 4 to setup the git server.
     223        enable this, continue with step 4 to set up the git server
     224        for public read-only access.
    202225      </para>
    203226
     
    210233        The setup described above makes a repository available for
    211234        authenticated users (via providing the ssh public key file).
    212         There is also a quite simple way to publish the
     235        There is also a simple way to publish the
    213236        repository to unauthenticated users - of course without write
    214237        access.
     
    253276
    254277      <para>
    255         In order to make <application>git</application> exporting a
     278        In order to allow <application>git</application> to export a
    256279        repository, a file named <filename>git-daemon-export-ok</filename>
    257280        is required in each repository directory on the server. The
     
    263286
    264287      <para>
    265         Also review the configuration file
     288        Finally, review the configuration file
    266289        <filename revision="sysv">/etc/sysconfig/git-daemon</filename>
    267290        <filename revision="systemd">/etc/default/git-daemon</filename>
    268         for valid repository paths.
     291        for valid repository paths and change them as appropriate.
    269292      </para>
    270293
Note: See TracChangeset for help on using the changeset viewer.