Changeset b4be4cf1 for general/prog/gitserver.xml
- Timestamp:
- 01/08/2021 06:46:05 PM (3 years ago)
- Branches:
- 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- 7c9ae62
- Parents:
- c5e3c1c
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
general/prog/gitserver.xml
rc5e3c1c rb4be4cf1 77 77 For any developer who should have access to the repository 78 78 add his/her public ssh key to <filename>/home/git/.ssh/authorized_keys</filename>. 79 First, prepend some options to prevent users to usethe79 First, prepend some options to prevent users from using the 80 80 connection to git for port forwarding to other machines 81 81 the git server might reach. … … 117 117 </para> 118 118 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 119 127 <screen role="root"><userinput>install -o git -g git -m755 -d /srv/git/project1.git && 120 128 cd /srv/git/project1.git && … … 127 135 <title>3. Populate the repository from a client system</title> 128 136 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 129 144 <para> 130 145 Now that the repository is created, it can be used by the … … 150 165 to the repository as the initial content: 151 166 </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> 152 174 153 175 <screen role="nodump"><userinput>mkdir myproject … … 199 221 <filename>authorized_keys</filename> file and there is no 200 222 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. 202 225 </para> 203 226 … … 210 233 The setup described above makes a repository available for 211 234 authenticated users (via providing the ssh public key file). 212 There is also a quitesimple way to publish the235 There is also a simple way to publish the 213 236 repository to unauthenticated users - of course without write 214 237 access. … … 253 276 254 277 <para> 255 In order to make <application>git</application> exportinga278 In order to allow <application>git</application> to export a 256 279 repository, a file named <filename>git-daemon-export-ok</filename> 257 280 is required in each repository directory on the server. The … … 263 286 264 287 <para> 265 Alsoreview the configuration file288 Finally, review the configuration file 266 289 <filename revision="sysv">/etc/sysconfig/git-daemon</filename> 267 290 <filename revision="systemd">/etc/default/git-daemon</filename> 268 for valid repository paths .291 for valid repository paths and change them as appropriate. 269 292 </para> 270 293
Note:
See TracChangeset
for help on using the changeset viewer.