Krettis

Install your public key into the machine

ssh-copy-id [-i [identity_file]] [user@]machine 

Link to a port in your machine

$ ssh -f -N -L 9471:127.0.0.1:3306 user@db-machine.org.gov
# -f ssh in background

-N not executing a command

Krettis

var _id = mongoose.mongo.BSONPure.ObjectID.fromHexString("4eb6e7e7e9b7f4194e000001");

Krettis

Keybase proof

I hereby claim:

• I am krettis on github.
• I am krettis (https://keybase.io/krettis) on keybase.
• I have a public key whose fingerprint is 8323 0FE3 BEE2 5AB0 ADDF 2727 668D 2C06 9551 93A1

To claim this, I am signing this object:

Krettis

List

\list or \l: list all databases

select database

\connect dbname or \c dbname

import

psql dbname < filepath

Krettis

• run commands
• resource control
• run control
• runtime configuration

Personally, I'd go with run control, because ESR says so.

http://www.catb.org/~esr/writings/taoup/html/ch10s03.html

Krettis

Prefix commits

PRJ-P-G04

- Two / Three letter shortname of project
dash 

- Type of commmit
        - A : api breaking (first number of your semversion)
        - F : feature (second number of your semversion)

Krettis

-- stop all vagrant boxes
 vboxmanage list runningvms | sed -E 's/.*\{(.*)\}/\1/' | xargs -L1 -I {} VBoxManage controlvm {} savestate

Krettis

Developer Cheat Sheets

This are my cheat sheets that I have compiled over the years. Tired of searching Google for the same things, I started adding the information here. As time went on, this list has grown. I use this almost everday and this Gist is the first bookmark on my list for quick and easy access.

I recommend that you compile your own list of cheat sheets as typing out the commands has been super helpful in allowing me to retain the information longer.

Krettis

Represential State Transfer - api

Only has two types of resources:

• Collection
• Instance

URLS

• Create clean, short, simple uris.

Krettis

Only update composer lock hash

composer update nothing 

or

composer update --lock

More clean way