A.s. adRn-s

PSQL

Magic words:

psql -U postgres

Some interesting flags (to see all, use -h or --help depending on your psql version):

-E: will describe the underlaying queries of the \ commands (cool for learning!)
-l: psql will list all databases and then exit (useful if the user you connect with doesn't has a default database, like at AWS RDS)

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j

	KEYBINDINGS
	byobu keybindings can be user defined in /usr/share/byobu/keybindings/ (or within .screenrc if byobu-export was used). The common key bindings
	are:

	F2 - Create a new window

	F3 - Move to previous window

	F4 - Move to next window

	#!/usr/bin/env bash
	# Runs a command wrapped in btrfs snapper pre-post snapshots.
	# Usage: $ snp <commands>
	# e.g.: $ snp pacman -Syyu
	# Requirements: snapper (https://wiki.archlinux.org/title/snapper)
	# The latest version of this script is hosted at https://gist.github.com/erikw/5229436

	log_path="/var/local/log/snp"
	date=$(date "+%Y-%m-%d-%H%M%S")
	log_file="${log_path}/snp_${date}.log"