I hereby claim:
- I am ltran on github.
- I am mrltran (https://keybase.io/mrltran) on keybase.
- I have a public key ASDkFn97D9O7I4AGzQ18VaBcSQ3HDFbBDuqE1mA79D7BOQo
To claim this, I am signing this object:
I hereby claim:
To claim this, I am signing this object:
[color] | |
diff = auto | |
status = auto | |
branch = auto | |
ui = auto | |
[log] | |
date = local | |
[core] | |
excludesfile = ~/.gitignore | |
quotepath = false |
func search(nums []int, target int) int { | |
nL := len(nums) | |
if nL == 0 { | |
return -1 | |
} else if nL == 1 { | |
if nums[0] == target { | |
return 0 | |
} else { | |
return -1 | |
} |
I hereby claim:
To claim this, I am signing this object:
Spin up three m3.medium
EC2 ubuntu 14.04
instances with public DNS enabled and configure them for high network traffic by increasing these limits:
Added fs.file-max=80000
to /etc/sysctl.conf
Added the following lines to /etc/security/limits.conf
Sometimes you want to use a gem on Heroku that is in a private repository on GitHub.
Using git over http you can authenticate to GitHub using basic authentication. However, we don't want to embed usernames and passwords in Gemfiles. Instead, we can use authentication tokens.
This method does not add your OAuth token to Gemfile.lock
. It uses bundle config to store your credentials, and allows you to configure Heroku to use environment variables when deploying.
༼ つ ◕_◕ ༽つ | |
ᕕ( ᐛ )ᕗ | |
(╯°□°)╯︵ ┻━┻ | |
┌∩┐(◣_◢)┌∩┐ | |
¯\_(ツ)_/¯ |