bibledit-gtk-data 4.9-1 / usr / share / bibledit-gtk / site / gtk / tutorials / collaboration / reposetup / secure-network-repository-setup.html

This file is indexed.

/usr/share/bibledit-gtk/site/gtk/tutorials/collaboration/reposetup/secure-network-repository-setup.html is in bibledit-gtk-data 4.9-1.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below. 

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
  <head>
    <link href="../../../../bibledit.css" rel="stylesheet" type="text/css" /><!-- 

Copyright (©) 2003-2011 Teus Benschop and Contributors to the Wiki.

Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3
or any later version published by the Free Software Foundation;
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
Texts.  A copy of the license is included in the section entitled "GNU
Free Documentation License" in the file FDL.

-->
    <title></title>
  </head>
  <body>
    <div id="menu">
      <ul>
        <li>
          <a href="../../../../home.html">1 Bibledit</a>
        </li>
        <li>
          <a href="../reposetup.html">Reposetup</a>
        </li>
        <li style="list-style: none; display: inline">
          <hr />
        </li>
        <li>
          <a href="open-network-repository-setup.html">Open network repository setup</a>
        </li>
        <li>Secure network repository setup
        </li>
        <li>
          <a href="secure-shell-keys-setup.html">Secure shell keys setup</a>
        </li>
        <li>
          <a href="usb-flash-drive-repository-setup.html">USB flash drive repository setup</a>
        </li>
      </ul>
    </div>
    <div id="content">
      <h1>
        Secure network repository setup
      </h1>
      <h3>
        <a name="TOC-Introduction" href="" id="TOC-Introduction"></a>Introduction
      </h3>
      <p>
        In this tutorial we are going to set up a secure network repository.
      </p>
      <p>
        It uses a git repository on sourceforge.net.
      </p>
      <p>
        Open an account on <a href="http://sourceforge.net/" rel="nofollow">sourceforge.net</a>. We will use the username "joe" in this tutorial.
      </p>
      <p>
        Register a new project on your personal account page on sourceforge.net. Let's call this project "repo2".
      </p>
      <p>
        Enable project feature "Git" on this project. This provides the repository.
      </p>
      <p>
        The next thing is to try whether you can read the repository properly. To try that, open a terminal and issue the following command:
      </p>
      <pre>
git ls-remote ssh://joe@repo2.git.sourceforge.net/gitroot/repo2/repo2
</pre>
      <p>
        This command probably will ask for your password, and the first time it could ask you whether you want to continue connecting. But it should show no errors. If it completes without errors, then your secure repository works well.
      </p>
      <p>
        The repository that was created in this tutorial has the following URL:
      </p>
      <pre>
ssh://user@repo2.git.sourceforge.net/gitroot/repo2/repo2
</pre>
      <p>
        The users that are going to use this repository need this URL. Where it says "user", each user would need to fill in his own username.&nbsp;
      </p>
      <p>
        Each user will need to open his or her own account on sourceforge.net. After that, they need to open an e-mail from sourceforge.net and click the link to activate their account. Each user needs to be registered as a member of the project, in this example, project "repo2". This is so that the user can write to the repository.&nbsp;
      </p>
      <p>
        So the moderator (or the person to first set up the repository) will need to log onto to his account at sourceforge.net,
      </p>
      <ul>
        <li>click on “account” in the upper right,&nbsp;
        </li>
        <li>choose the projects tab,&nbsp;
        </li>
        <li>click on the project name,&nbsp;
        </li>
        <li>then click View all files.
        </li>
        <li>Now there will be a series of tabs at the top which expand if your mouse cursor hovers above them. Go to the last one, Project Admin, and click Members.
        </li>
        <li>Finally! From there you will be add any members who have activated their accounts by clicking in the e-mail that was sent to them.
        </li>
        <li style="list-style: none; display: inline">
          <ul>
            <li>After this, each project member will be able to do the steps in <a href="../../../../gtk/tutorials/collaboration/reposetup/secure-shell-keys-setup.html">Secure shell keys setup</a>.
            </li>
          </ul>
        </li>
      </ul>
      <p>
        <br />
      </p>
    </div>
  </body>
</html>

APT Browse - Built by Thomas Orozco.