Power User Tools - Revision history

Cclark: /* auto-reconnect */

2017-05-04T01:55:23Z

‎auto-reconnect

2017-05-04T01:35:17Z

‎Reverse SSH

2017-05-04T00:56:18Z

‎Reverse SSH

2017-05-04T00:50:51Z

2015-08-11T14:35:29Z

‎Adding new repo

2015-07-07T14:20:42Z

‎Adding new repo

2015-07-07T14:20:06Z

‎Adding new repo

2015-07-07T14:19:15Z

‎Adding new repo

2015-07-03T15:39:41Z

‎Managing configs with vcsh and mr

2015-07-03T15:27:32Z

‎Managing configs with vcsh and mr

← Older revision		Revision as of 01:55, 4 May 2017
Line 45:		Line 45:
	==auto-reconnect==		==auto-reconnect==

−	The above command will work, but	+	The above command will work, but if <code>ssh</code> is disconnected for some reason, you will have to rerun it. In fact, some <code>ssh</code> clients are configured to disconnect after a certain amount of inactivity. The <code>autossh</code>[http://www.harding.motd.ca/autossh/] utility will monitor an <code>ssh</code> connection and reconnect it if it is disconnected. To use <code>autossh</code>, run the following command
		+
		+	> autossh -M 0 -f -N -R 2222:localhost:22 Public
		+
		+	The <code>-M</code> option tells <code>autossh</code> which port to use for monitoring the connection. For more detailed (and advanced configuration), see this [https://www.everythingcli.org/ssh-tunnelling-for-fun-and-profit-autossh/ blog post].

@@ Line 31: / Line 31: @@
 =Reverse SSH=
-The <code>ssh</code> command has a <code>-R</code> option that can be used to allow ssh access to a computer that does not have a public, static IP address (such as a computer behind a NAT at home) using another
+The <code>ssh</code> command has a <code>-R</code> option that can be used to allow <code>ssh</code> access to a computer that does not have a public, static IP address (such as a computer behind a NAT at home) using another
 computer that does have a public IP Address.
-Assume you have two computers, <code>Public</code> and <code>Private</code>. <code>Public</code> has a public, static IP address, and you have ssh access to it. <code>Private</code> is a computer that sits behind your home router, and cannot be accessed from the outside. On <code>Private</code>, run the following command:
+Assume you have two computers, <code>Public</code> and <code>Private</code>. <code>Public</code> has a public, static IP address, and you have <code>ssh</code> access to it. <code>Private</code> is a computer that sits behind your home router, and cannot be accessed from the outside. On <code>Private</code>, run the following command:

← Older revision		Revision as of 00:56, 4 May 2017
Line 32:		Line 32:

	The <code>ssh</code> command has a <code>-R</code> option that can be used to allow ssh access to a computer that does not have a public, static IP address (such as a computer behind a NAT at home) using another		The <code>ssh</code> command has a <code>-R</code> option that can be used to allow ssh access to a computer that does not have a public, static IP address (such as a computer behind a NAT at home) using another
−	computer that does have a public IP ~~Adrees~~.	+	computer that does have a public IP Address.
		+
		+	Assume you have two computers, <code>Public</code> and <code>Private</code>. <code>Public</code> has a public, static IP address, and you have ssh access to it. <code>Private</code> is a computer that sits behind your home router, and cannot be accessed from the outside. On <code>Private</code>, run the following command:

@@ Line 1: / Line 1: @@
-=Managing configs with <code>vcsh</code> and <code>mr</code>=
+=Managing configs with <code>vcsh</code>=
 <code>vcsh</code> [https://github.com/RichiH/vcsh] is a utility that allows you to create multiple git repositories to store configuration files in your home directory.
@@ Line 29: / Line 29: @@
    > vcsh zsh push --set-upstream origin master # push to the origin and setup tracking
-Next, add the repository to the <code>mr</code> configuration.
+=Reverse SSH=
-Add the following lines
+The <code>ssh</code> command has a <code>-R</code> option that can be used to allow ssh access to a computer that does not have a public, static IP address (such as a computer behind a NAT at home) using another
+computer that does have a public IP Adrees.

@@ Line 31: / Line 31: @@
 Next, add the repository to the <code>mr</code> configuration.
-   > vim ~/.config/mr/
+   > vim ~/.config/mr/available.d/zsh.git
   ...

← Older revision		Revision as of 14:20, 7 July 2015
Line 37:		Line 37:

	[$HOME/.config/vcsh/repo.d/zsh.git]		[$HOME/.config/vcsh/repo.d/zsh.git]
−	checkout = vcsh clone ssh://~~repos~~@~~eigen.fhsu.edu~~/~~cclark~~/~~configs~~/~~vcsh~~/~~zsh~~ zsh	+	checkout = vcsh clone ssh://user@host/repo/with/write/access zsh

← Older revision		Revision as of 14:20, 7 July 2015
Line 35:		Line 35:

	Add the following lines		Add the following lines
		+
		+	[$HOME/.config/vcsh/repo.d/zsh.git]
		+	checkout = vcsh clone ssh://repos@eigen.fhsu.edu/cclark/configs/vcsh/zsh zsh

← Older revision		Revision as of 14:19, 7 July 2015
Line 28:		Line 28:
	> vcsh zsh remote add origin ssh://user@host/repo/with/write/access # create remote repo		> vcsh zsh remote add origin ssh://user@host/repo/with/write/access # create remote repo
	> vcsh zsh push --set-upstream origin master # push to the origin and setup tracking		> vcsh zsh push --set-upstream origin master # push to the origin and setup tracking
		+
		+	Next, add the repository to the <code>mr</code> configuration.
		+
		+	> vim ~/.config/mr/
		+	...
		+
		+	Add the following lines

← Older revision		Revision as of 15:39, 3 July 2015
Line 4:		Line 4:
	It solves the problem of having to use symlinks, and is a very nice tool. It works well with another tool named <code>mr</code> [https://github.com/joeyh/myrepos] that allows		It solves the problem of having to use symlinks, and is a very nice tool. It works well with another tool named <code>mr</code> [https://github.com/joeyh/myrepos] that allows
	you to synchronize all of your config repos with a single command.		you to synchronize all of your config repos with a single command.
		+
		+	==Common Tasks==
		+
		+	===Adding new repo===
		+
		+	Let say you want to add a repo for tracking your zsh configuration.
		+	First, create a gitignore file for the repo so you can just do <code>git add .</code>
		+
		+	> vim ~/.gitignore.d/zsh
		+	...
		+
		+	Add the following lines
		+
		+	/*
		+	!/.zsh
		+
		+
		+	Now create the repository and push to a remote
		+
		+	> vcsh init zsh # create the repo
		+	> vcsh zsh add . # add all files not masked by ~/.gitignore.d/zsh
		+	> vcsh zsh commit # commit files
		+	> vcsh zsh remote add origin ssh://user@host/repo/with/write/access # create remote repo
		+	> vcsh zsh push --set-upstream origin master # push to the origin and setup tracking

@@ Line 1: / Line 1: @@
 =Managing configs with <code>vcsh</code> and <code>mr</code>=
-<code>vcsh</code> is a utility that allows you to create multiple git repositories to store configuration files in your home directory.
+<code>vcsh</code> [https://github.com/RichiH/vcsh] is a utility that allows you to create multiple git repositories to store configuration files in your home directory.
-It solves the problem of having to use symlinks, and is a very nice tool. It works well with another tool named <code>mr</code> that allows
+It solves the problem of having to use symlinks, and is a very nice tool. It works well with another tool named <code>mr</code> [https://github.com/joeyh/myrepos] that allows
 you to synchronize all of your config repos with a single command.