Pushing changes to an empty git repository for the first time



  • $ git push --set-upstream origin master

    After cloning an empty repository on the client (“git clone” just after “git init”, for instance), “git push” fails.

    In order to be able to push to this repository for the first time, you need to run the above command. It will link your local “master” branch to the “master” branch in the origin server, and push the changes.

    This is only necessary only for the first push; after that, you can use just the commands “git push” or “git pull” in order to do this operations.

    commandlinefu.com

    Diff your entire server config at ScriptRock.com

    http://feedproxy.google.com/~r/Command-line-fu/~3/qK1bg8-UwAU/pushing-changes-to-an-empty-git-repository-for-the-first-time


Log in to reply
 



Tmux Commands

screen and tmux

A comparison of the features (or more-so just a table of notes for accessing some of those features) for GNU screen and BSD-licensed tmux.

The formatting here is simple enough to understand (I would hope). ^ means ctrl+, so ^x is ctrl+x. M- means meta (generally left-alt or escape)+, so M-x is left-alt+x

It should be noted that this is no where near a full feature-set of either group. This - being a cheat-sheet - is just to point out the most very basic features to get you on the road.

Trust the developers and manpage writers more than me. This document is originally from 2009 when tmux was still new - since then both of these programs have had many updates and features added (not all of which have been dutifully noted here).

Action tmux screen
start a new session tmux OR
tmux new OR
tmux new-session
screen
re-attach a detached session tmux attach OR
tmux attach-session
screen-r
re-attach an attached session (detaching it from elsewhere) tmux attach -d OR
tmux attach-session -d
screen -dr
re-attach an attached session (keeping it attached elsewhere) tmux attach OR
tmux attach-session
screen -x
detach from currently attached session ^b d OR
^b :detach
^a ^d OR
^a :detach
rename-window to newname ^b , <newname> OR
^b :rename-window <newn>
^a A <newname>
list windows ^b w ^a w
list windows in chooseable menu ^a "
go to window # ^b # ^a #
go to last-active window ^b l ^a ^a
go to next window ^b n ^a n
go to previous window ^b p ^a p
see keybindings ^b ? ^a ?
list sessions ^b s OR
tmux ls OR
tmux list-sessions
screen -ls
toggle visual bell ^a ^g
create another window ^b c ^a c
exit current shell/window ^d ^d
split window/pane horizontally ^b " ^a S
split window/pane vertically ^b % ^a |
switch to other pane ^b o ^a <tab>
kill the current pane ^b x OR (logout/^D)
collapse the current pane/split (but leave processes running) ^a X
cycle location of panes ^b ^o
swap current pane with previous ^b {
swap current pane with next ^b }
show time ^b t
show numeric values of panes ^b q
toggle zoom-state of current pane (maximize/return current pane) ^b z
break the current pane out of its window (to form new window) ^b !
re-arrange current panels within same window (different layouts) ^b [space]
Kill the current window (and all panes within) ^b killw [target-window]
  • $ for f in find . -type d; do pushd . > /dev/null ; echo -e cd $f ; find . -name *.js | wc -l "\t" $f | grep -v ^0 ; popd >/dev/null; done | sort -n -k 1 -r | less

    I wanted to count and display the top directories containing JavaScript files in some of my project. Here it is. Maybe it can be written to more simply syntax by using find -exec…

    View this command to comment, vote or add to favourites View all commands by tobi

    commandlinefu.com

    Diff your entire server config at ScriptRock.com

    http://feedproxy.google.com/~r/Command-line-fu/~3/ZAMRabS8DqE/count-number-of-javascript-files-in-subdirectories

    read more
  • $ cat configmap.json | jq 'with_entries(if .key == "data" then .value=(.value | to_entries | map( { (.key): (.value|@base64) } ) | add ) elif .key == "kind" then .value="Secret" else . end)'

    simple jq one-liner to convert from configmaps to secrets (which require the values to be base64 encoded).

    To automatically pull the config map, convert it, and re-upload the corresponding secret:

    kubectl get --export -o json cm [configmap name] | jq ‘with_entries(if .key == “data” then .value=(.value | to_entries | map( { (.key): (.value|@base64) } ) | add ) elif .key == “kind” then .value=“Secret” else . end)’ > secret.json; kubectl create -f secret.json

    View this command to comment, vote or add to favourites View all commands by tyzbit

    commandlinefu.com

    Diff your entire server config at ScriptRock.com

    http://feedproxy.google.com/~r/Command-line-fu/~3/qgjN_q700bU/convert-kubernetes-configmaps-to-secrets

    read more
});