docker ps
: list running containers (option-a
exited ones)docker run <image name>
: run/install docker image ; options :it
: interactive--rm
: delete container after it stops--mount type=bind,source=$(pwd),destination=/src
: mount current dir to/src
on the container
docker rm <id|name>
: delete containerdocker diff <id|name>
: show diff made in this imagedocker system df
: show space taken by docker
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/bin/bash | |
# inspired by : https://github.com/aseprite/aseprite/issues/477 | |
# To make it work in Nemo create a symlink like this : | |
# sudo ln -s /path/to/this/file/launch_aseprite /usr/bin/launch_aseprite | |
# and then in the default app of Nemo juste use `launch_aseprite` instead of Aseprite directly | |
# try to find the aseprite window by name | |
window_id=$(xdotool search --name "Aseprite v1" | tail -n 1) | |
if [ -n "$window_id" ]; then |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
select pid, usename, pg_blocking_pids(pid) as blocked_by, query as blocked_query | |
from pg_stat_activity | |
where cardinality(pg_blocking_pids(pid)) > 0; |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SELECT | |
table_name, | |
pg_size_pretty(table_size) AS table_size, | |
pg_size_pretty(indexes_size) AS indexes_size, | |
pg_size_pretty(total_size) AS total_size | |
FROM ( | |
SELECT | |
table_name, | |
pg_table_size(table_name) AS table_size, | |
pg_indexes_size(table_name) AS indexes_size, |
Patrick Joyce - pragmati.st/checklists
THE SUBMITTER SHOULD ALWAYS ASK THEMSELVES THE FOLLOWING QUESTIONS:
- Have I looked at every line of the diff between your branch and master?
- Is there anything in this patch that is not related to the overall change?
- Have I structured the commits to make the reviewer’s job easy?
- Have I tested the code locally?
- Should QA look at this before I submit it for review?