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/
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.
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
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:
in fact, I want to know, how to only get the modified files.
There is 1 alternative - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
JIC you're webserver is not your workstation
git archive --format=tar HEAD | ssh webuser@webserver.tld 'tar -C /var/www -xf -'s/you're/your/
In fact, my web service and git service on the same machine.
And, I just want to update the changed files, but, "git pull origin master" always failed.
rsync seems a more handy tool to update only changed files. Once configured, you can update site with:
rsync -av --exclude=.git/ /path/to/repo /path/to/wwwOr you can have a patch folder, with all the modifications between the repo version and your prod site (like a different config file). You can then apply the patches with:
find /path/to/patches/*.patch -exec patch -i {} \;I had to resort to this on deploy scripts, to fetch bootstraping scripts on a server with no git installed.
Streaming git over ssh, love it!