Hide

What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again.

Delete that bloated snippets file you've been using and share your personal repository with the world. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.


If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/

Get involved!

You can sign-in using OpenID credentials, or register a traditional username and password.

First-time OpenID users will be automatically assigned a username which can be changed after signing in.

Universal configuration monitoring and system of record for IT.
Hide

Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for:

Hide

News

May 19, 2015 - A Look At The New Commandlinefu
I've put together a short writeup on what kind of newness you can expect from the next iteration of clfu. Check it out here.
March 2, 2015 - New Management
I'm Jon, I'll be maintaining and improving clfu. Thanks to David for building such a great resource!
Hide

Top Tags

Hide

Functions

Hide

Credits

github push-ing behind draconian proxies!

Terminal - github push-ing behind draconian proxies!
git remote add origin git@SSH-HOST:<USER>/<REPOSITORY>.git
2009-11-19 06:57:50
User: jnash
2
github push-ing behind draconian proxies!

If you are behind a restrictive proxy/firewall that blocks port 22 connections but allows SSL on 443 (like most do) then you can still push changes to your github repository.

Your .ssh/config file should contain:

Host *

ForwardX11 no

TCPKeepAlive yes

ProtocolKeepAlives 30

ProxyCommand /usr/local/bin/proxytunnel -v -p -d %h:443

Host

User git

Hostname ssh.github.com

ChallengeResponseAuthentication yes

IdentityFile ~/.ssh/id_rsa

IdentitiesOnly yes

Basically proxytunnel "tunnels" your ssh connection through port 443.

You could also use corkscrew or some other tunneling program that is available in your distro's repository.

PS: I generally use "github.com" as the SSH-HOST so that urls of the kind git@github.com:USER/REPO.git work transparently :) You

Alternatives

There are 2 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

At least in debian/ubuntu 'man ssh_config' reveals all the other options you can use. When I check out an svn+ssh:// url I sometimes need to specify an alternate SSH port, and ~/.ssh/config is the only way to do this, since the svn command line client doesn't accept port numbers in the repository url.

Comment by bwoodacre 297 weeks and 5 days ago

Your point of view

You must be signed in to comment.