I hereby claim:
- I am sysadmiral on github.
- I am sysadmiral (https://keybase.io/sysadmiral) on keybase.
- I have a public key ASAuXvOdX5M1WeNUVoxrQcvi46Q-g0TJeW0JcPznBLQlmAo
To claim this, I am signing this object:
# http://EditorConfig.org | |
# Top-most EditorConfig file | |
root = true | |
[*] | |
charset = "utf-8" | |
end_of_line = lf | |
indent_style = space | |
indent_size = 2 |
I hereby claim:
To claim this, I am signing this object:
resource "aws_lb_ssl_negotiation_policy" "tls_policy" { | |
name = "${aws_elb.elb.name}-policy" | |
load_balancer = "${aws_elb.elb.id}" | |
lb_port = 443 | |
attribute { | |
name = "Protocol-TLSv1" | |
value = "true" | |
} |
TMPFILE="/tmp/seeinstalls.tmp" | |
function get_initial_installs { | |
zgrep '^Package:' /var/log/installer/initial-status.gz | awk '{ print $2}' > $TMPFILE | |
} | |
function diff_lists { | |
aptitude search -F %p '~i!~M' | awk '{ print $1}' | grep -v -F -f $TMPFILE | |
} |
If you have an IAM user that you set up using the IAM interface, you need to do the following two steps to enable the user to send email using the Amazon SES SMTP interface:
Derive the user's SMTP credentials from their AWS credentials using the algorithm provided in this section. A user's SMTP username is the same as their AWS Access Key ID, so you just need to generate the SMTP password.
Apply the following policy to the IAM user:
{
"Version": "2012-10-17",
"Statement": [
find_executable: checking for gmake... -------------------- no | |
-------------------- | |
find_executable: checking for make... -------------------- yes | |
-------------------- | |
find_executable: checking for cmake... -------------------- yes |
#!/usr/bin/env bash | |
# SEE YOU SPACE COWBOY by DANIEL REHN (danielrehn.com) | |
# Displays a timeless message in your terminal with cosmic color effects | |
# Usage: add "sh ~/seeyouspacecowboy.sh; sleep 2" to .bash_logout (or similar) in your home directory | |
# (adjust the sleep variable to display the message for more seconds) | |
# Cosmic color sequence |