I hereby claim:
- I am roustem on github.
- I am roustem (https://keybase.io/roustem) on keybase.
- I have a public key ASAydHUtI9pDZiM5XGGifDoFY_ZPnoLcdTyIn4KCoRiMtAo
To claim this, I am signing this object:
| "B5AppSubnet1": { | |
| "Type": "AWS::EC2::Subnet", | |
| "Properties": { | |
| "CidrBlock": { "Fn::Select" : ["0", { "Fn::FindInMap" : [ "SubnetCidr", { "Ref" : "Env" }, "b5app"] }] }, | |
| "AvailabilityZone": { "Fn::Select" : [ "0", { "Fn::GetAZs" : "" } ]}, | |
| "VpcId": { "Ref": "Vpc" }, | |
| "Tags": [ | |
| { "Key" : "Application", "Value" : "B5" }, | |
| { "Key" : "env", "Value": { "Ref" : "Env" } }, | |
| { "Key" : "Name", "Value": { "Fn::Join" : ["-", [ {"Ref" : "Env"}, "b5", "b5app-subnet1"]] } } |
| // Run on https://start.1password.com to get sjcl | |
| function timeSJCL_SHA256(iterations, value) { | |
| let timerName = "SJCL SHA-256 (" + value.length + " bytes, " + iterations + " iterations)"; | |
| console.time(timerName); | |
| for (let i = 0; i < iterations; i++) { | |
| sjcl.hash.sha256.hash(value); | |
| } | |
| console.timeEnd(timerName); |
| package main | |
| import ( | |
| _ "expvar" | |
| "io" | |
| "log" | |
| "net/http" | |
| "strings" | |
| ) |
I hereby claim:
To claim this, I am signing this object:
| package main | |
| import "fmt" | |
| func test() interface{} { | |
| return 123 | |
| } | |
| func main() { | |
| // no panic |
| package main | |
| import "fmt" | |
| type myError struct { | |
| Message string | |
| } | |
| func (m *myError) Error() string { | |
| return "MyError: " + m.Message |
| package main | |
| import "fmt" | |
| type MyError struct { | |
| Message string | |
| } | |
| func (m *MyError) Error() string { | |
| return m.Message |
WebCrypto APIs:
subtle.generateKey
subtle.exportKey
subtle.importKey
subtle.deriveBits
subtle.encrypt
subtle.decrypt
subtle.digest
A quick note on how I'm currently handling Blue/Green or A/B deployments with Terraform and AWS EC2 Auto Scaling.
In my particular use case, I want to be able to inspect an AMI deployment manually before disabling the previous deployment.
Hopefully someone finds this useful, and if you have and feedback please leave a comment or email me.
I build my AMI's using Packer and Ansible.
| -- | |
| -- This example shows how bad MySQL is when handling foreign key locks. | |
| -- Deadlock happens when multiple transactions are inserting child records | |
| -- pointing to the same parent and then try to update the parent record. | |
| -- | |
| -- The solution is to always try to update the parent record first | |
| -- but it could be hard to track the when database schema is more complex. | |
| -- | |
| -- Based on: https://bugs.mysql.com/bug.php?id=48652 | |
| -- |