start tutorial
This commit is contained in:
48
GIT.md
Normal file
48
GIT.md
Normal file
@ -0,0 +1,48 @@
|
|||||||
|
Git over I2P for Users
|
||||||
|
======================
|
||||||
|
|
||||||
|
TUTORIAL for setting up git access through an I2P Tunnel. This tunnel will act
|
||||||
|
as your access point to a single git service on I2P.
|
||||||
|
|
||||||
|
This **NOT** git-remote-i2p, I'm working on it, it'll be ready soon.
|
||||||
|
git-remote-i2p will automatically tunnel to a git service hosted at an I2P
|
||||||
|
domain or at a .b32.i2p address.
|
||||||
|
|
||||||
|
Before anything else: Know the capabilities the service offers to the public
|
||||||
|
----------------------------------------------------------------------------
|
||||||
|
|
||||||
|
Depending on how the git service is configured, it may or may not offer all
|
||||||
|
services on the same address. In the case of gittest.i2p, there is a public
|
||||||
|
HTTP URL, but this URL is read-only and cannot be used to make changes. To do
|
||||||
|
that, you must also know the SSH base32, which isn't public at this time. Unless
|
||||||
|
I've told you the SSH base32 to gittest.i2p, head over to the [Server](GITLAB.md)
|
||||||
|
tutorial to set up your own.
|
||||||
|
|
||||||
|
First: Set up an account at a Git service
|
||||||
|
-----------------------------------------
|
||||||
|
|
||||||
|
To create your repositories on a remote git service, sign up for a user account
|
||||||
|
at that service. Of course it's also possible to create repositories locally
|
||||||
|
and push them to a remote git service, but most will require an account and for
|
||||||
|
you to create a space for the repository on the server. Gitlab has a very simple
|
||||||
|
sign-up form:
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
Second: Create a project to test with
|
||||||
|
-------------------------------------
|
||||||
|
|
||||||
|
To make sure the setup process works, it helps to make a repository to test with
|
||||||
|
from the server, and for the sake of this tutorial, we're going to use a fork of
|
||||||
|
the I2P router.
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
Third: Set up your git client tunnel
|
||||||
|
------------------------------------
|
||||||
|
|
||||||
|
![]()
|
22
README.md
22
README.md
@ -1,2 +1,20 @@
|
|||||||
# git-over-i2p
|
git-over-i2p
|
||||||
TUTORIAL for setting up git access through an I2P Tunnel. This **NOT** git-remote-i2p, I'm working on it, it'll be ready soon.
|
============
|
||||||
|
|
||||||
|
TUTORIAL for setting up git access through an I2P Tunnel. This tunnel will act
|
||||||
|
as your access point to a single git service on I2P.
|
||||||
|
|
||||||
|
This **NOT** git-remote-i2p, I'm working on it, it'll be ready soon.
|
||||||
|
git-remote-i2p will automatically tunnel to a git service hosted at an I2P
|
||||||
|
domain or at a .b32.i2p address.
|
||||||
|
|
||||||
|
[If you're trying to set up a git *service* for personal or community use, go here](GITLAB.md)
|
||||||
|
----------------------------------------------------------------------------------------------
|
||||||
|
|
||||||
|
... for a simple docker+Gitlab CE over I2P setup
|
||||||
|
|
||||||
|
[If you're trying to set up a git *client* for any reason, go here](GIT.md)
|
||||||
|
---------------------------------------------------------------------------
|
||||||
|
|
||||||
|
... for a tunnel-based configuration to access any Git service.
|
||||||
|
|
||||||
|
BIN
explore.png
Normal file
BIN
explore.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 89 KiB |
BIN
register.png
Normal file
BIN
register.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 62 KiB |
Reference in New Issue
Block a user