| /* Useful celery config. | |
| app = Celery('tasks', | |
| broker='redis://localhost:6379', | |
| backend='redis://localhost:6379') | |
| app.conf.update( | |
| CELERY_TASK_RESULT_EXPIRES=3600, | |
| CELERY_QUEUES=( | |
| Queue('default', routing_key='tasks.#'), |
FWIW: I didn't produce the content presented here (the outline from Edmond Lau's book). I've just copy-pasted it from somewhere over the Internet, but I cannot remember what exactly the original source is. I was also not able to find the author's name, so I cannot give him/her the proper credits.
| ssh-keygen -t rsa -b 4096 -N '' -C "rthijssen@gmail.com" -f ~/.ssh/id_rsa | |
| ssh-keygen -t rsa -b 4096 -N '' -C "rthijssen@gmail.com" -f ~/.ssh/github_rsa | |
| ssh-keygen -t rsa -b 4096 -N '' -C "rthijssen@gmail.com" -f ~/.ssh/mozilla_rsa |
| #!/bin/bash | |
| if [ "$#" -ne 2 ]; then | |
| echo "usage error: sh nmonitor.sh <pid> <time_to_monitor_in_seconds>";exit 1 | |
| fi | |
| pid=$1 | |
| time=$2 | |
| #read -p "Please enter your process Id: " pid |
| System: Host: lenovo Kernel: 4.10.0-26-generic x86_64 (64 bit gcc: 6.3.0) | |
| Desktop: Cinnamon 3.4.4 (Gtk 3.22.11-0ubuntu3) dm: lightdm Distro: Ubuntu 17.04 | |
| Machine: Device: laptop System: LENOVO product: 80SL v: Lenovo ideapad 310-14ISK | |
| Mobo: LENOVO model: Toronto 4A2 v: SDK0J40679 WIN UEFI: LENOVO v: 0XCN36WW date: 08/30/2016 | |
| Chassis: type: 10 v: Lenovo ideapad 310-14ISK | |
| Battery BAT0: charge: 24.4 Wh 88.8% condition: 27.5/30.0 Wh (92%) volts: 8.0/7.4 | |
| model: SMP L15M2PB2 serial: 1359 status: Discharging | |
| CPU: Dual core Intel Core i3-6100U (-HT-MCP-) cache: 3072 KB | |
| flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 9216 | |
| clock speeds: min/max: 400/2300 MHz 1: 470 MHz 2: 499 MHz 3: 499 MHz 4: 488 MHz |
Let's have some command-line fun with curl, [jq][1], and the [new GitHub Search API][2].
Today we're looking for:
| ## How to hide API keys from github ## | |
| 1. If you have already pushed commits with sensitive data, follow this guide to remove the sensitive info while | |
| retaining your commits: https://help.github.com/articles/remove-sensitive-data/ | |
| 2. In the terminal, create a config.js file and open it up: | |
| touch config.js | |
| atom config.js |
Grammar terminology matters because it allows us to communicate efficiently about language. Of course, it is not necessary to know the terminology to speak a language. We all learn our first languages without first learning what a verb and noun are. However, when we speak about grammar, especially in the context of writing, it helps if we can refer to grammar using precise vocabulary.
There are many sources online and in books that will explain grammar terminology. Not all of them will use exactly the same terms for the same grammatical points (I know, frustrating!). However, if you get into the habit of learning to identify the names of grammatical objects, you will move forward in your understanding of written English.
Sites and books that you can use to look up the names of grammatical terms
Use these rapid keyboard shortcuts to control the GitHub Atom text editor on Mac OSX.