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.

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:



2011-03-12 - Confoo 2011 presentation
Slides are available from the commandlinefu presentation at Confoo 2011: http://presentations.codeinthehole.com/confoo2011/
2011-01-04 - Moderation now required for new commands
To try and put and end to the spamming, new commands require moderation before they will appear on the site.
2010-12-27 - Apologies for not banning the trolls sooner
Have been away from the interwebs over Christmas. Will be more vigilant henceforth.
2010-09-24 - OAuth and pagination problems fixed
Apologies for the delay in getting Twitter's OAuth supported. Annoying pagination gremlin also fixed.

Top Tags



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
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


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 [email protected]:USER/REPO.git work transparently :) You


There are 3 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 283 weeks and 4 days ago

Your point of view

You must be signed in to comment.