Skip to content
This repository was archived by the owner on Mar 29, 2020. It is now read-only.

Commit c1ad513

Browse files
committed
Add more moved pages
1 parent eb834a2 commit c1ad513

File tree

3 files changed

+27
-39
lines changed

3 files changed

+27
-39
lines changed

Issues.wiki

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
#summary Issue tracker
2+
3+
*Moved to:* https://tortoisegit.org/issues
4+
5+
Google is shutting down !GoogleCode. We're still in the middle of our migration. The following URLs will always point to the current locations:
6+
* Website: https://tortoisegit.org
7+
* Download: https://tortoisegit.org/download
8+
* Manual: https://tortoisegit.org/docs/tortoisegit/
9+
* Issue tracker: https://tortoisegit.org/issues
10+
* Mailing lists:
11+
* [https://groups.google.com/group/tortoisegit-announce tortoisegit-announce],
12+
* [https://groups.google.com/group/tortoisegit-users tortoisegit-users] and
13+
* [https://groups.google.com/group/tortoisegit-dev tortoisegit-dev]

SourceCode.wiki

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
#summary Source Code repository
2+
3+
*Moved to:* https://tortoisegit.org/sourcecode
4+
5+
Google is shutting down !GoogleCode. We're still in the middle of our migration. The following URLs will always point to the current locations:
6+
* Website: https://tortoisegit.org
7+
* Download: https://tortoisegit.org/download
8+
* Manual: https://tortoisegit.org/docs/tortoisegit/
9+
* Issue tracker: https://tortoisegit.org/issues
10+
* Mailing lists:
11+
* [https://groups.google.com/group/tortoisegit-announce tortoisegit-announce],
12+
* [https://groups.google.com/group/tortoisegit-users tortoisegit-users] and
13+
* [https://groups.google.com/group/tortoisegit-dev tortoisegit-dev]

UsingPuTTY.wiki

Lines changed: 1 addition & 39 deletions
Original file line numberDiff line numberDiff line change
@@ -1,41 +1,3 @@
11
#summary Tips and tricks for SSH/PuTTY
22
3-
= Introduction =
4-
PuTTY comes with a great session management, where you can save attributes of connections (e.g. ssh key, username, port). This page describes how to make use of it - partly in form of a FAQ. For this to work, you need the [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html PuTTY.exe-application].
5-
6-
== How to use sessions ==
7-
One special "session" is the _Default Settings_ session, where you can set default values for all new connections (e.g. a key, a default username, enable compression, force SSH version 2 or change the default port and so on).
8-
9-
You can also save settings for (single) ssh connections as sessions. Take one server where the ssh server only listens on a different port, then you can set up all settings and save it to e.g. "SERVERNAME". Now you can access this saved settings by starting PuTTY and double clicking "SERVERNAME" in the saved sessions list *OR*, when using !TortoiseGit, plink or other putty applications, the entered servername (e.g. git@*SERVERNAME*:/test.git) will be matched against the saved sessions list and if found, the settings of the saved session are used.
10-
11-
Session names do not need to be the exact servername, you can also use different names, like "SERVERNAME1" or "SERVERNAME-adminkey" (e.g. git@SERVERNAME-adminkey:/test.git) if you want to use different keys with the same username on one server. This way it is also possible to have a saved session called "test.com", but when accessed a connection to example.com (saved hostname) is established.
12-
13-
= FAQ and examples section =
14-
15-
This section is based on the descriptions above and will bring some examples for the usage with !TortoiseGit (and plink).
16-
17-
The examples assume that you want to clone {{{[email protected]:/test.git}}}.
18-
19-
== How to use a default key for all SSH connections ==
20-
Start PuTTY, go to _Connection->SSH->Auth_ and select your key. Then go to _Session_, select _Default Settings_ and hit _Save_.
21-
22-
Now PuTTY (!TortoiseGit and plink) will try to use this key for all new connections (no need to configure it in !TortoiseGit). If the PuTTY agent is running, putty and plink try to use an already loaded key, but will ask for the password themselves (as a fallback).
23-
24-
== How to connect to a SSH server on a different port ==
25-
26-
=== All connections to a server should use the different port ===
27-
28-
Start PuTTY, fill in the servername ({{{example.com}}} here) in the _Host Name_-field and into the _Saved Sessions_ field. Change the port number to the number you need and click on _Save_. Now, when !TortoiseGit/plink uses this servername the port is automatically loaded from the session.
29-
30-
=== One special connection should use a different port ===
31-
32-
Start PuTTY, fill in the servername ({{{example.com}}} here) in the _Host Name_-field and put the servername followed by e.g. a number into the _Saved Sessions_ field (e.g. {{{example.com1}}} or whatever you like). Change the port number to the number you need for this connection and click on _Save_.
33-
34-
Now, when you want to use this saved session use {{{example.com1}}} as the servername: Clone {{{[email protected]:/test.git}}}. Plink detects that this is a saved session and loads the correct servername and port from the session.
35-
36-
You can create several sessions for a server with different session names, but make sure you do not use the servername ({{{example.com}}} here) as the exact session name, otherwise these settings will be the default ones if you try to connect to the server ({{{example.com}}}).
37-
38-
== How to use two different ssh keys for the same user on the same host ==
39-
Start PuTTY, fill in the servername ({{{example.com}}} here) in the _Host Name_-field and put the servername followed by e.g. a number into the _Saved Sessions_ field (e.g. {{{example.com1}}} or whatever you like). Go to _Connection->SSH->Auth_ and select the key which should be used for this connection. Now go back to _Session_ and click on _Save_.
40-
41-
Now, when you want to use this saved session use {{{example.com1}}} as the servername: Clone {{{[email protected]:/test.git}}}. Plink detects that this is a saved session and loads the correct servername and ssh key from the session.
3+
Moved to: https://tortoisegit.org/docs/tortoisegit/tgit-ssh-howto.html

0 commit comments

Comments
 (0)