Github authentication facts I forget every two months

#git #github

Git recommends SSH over HTTPS!
- You make the decision for SSH/HTTPS, when you
  - clone a remote repository, or
  - assign a remote to a local repository
When you do HTTPS:
- You can use the credential.helper in OSX to cache your password
- PITFALL POTENTIAL: If you use 2FA, then your password is not your password, but your Personal Access Token, which you can create here https://github.com/settings/tokens
When you do SSH:
- You need to have a key available. Otherwise you get "Not authenticated (public key error)" or something along these lines...
- Test if you have a key by typing in the console: ssh -vT git@github.com
- If you dont have a key, then go create one: https://github.com/settings/keys

Speedy emails, satisfied customers

Are delayed transactional emails costing you user satisfaction? Postmark delivers your emails almost instantly, keeping your customers happy and connected.