jq is useful to slice, filter, map and transform structured json data.
brew install jq
| #!/bin/bash | |
| AWS_DEFAULT_REGION="ap-northeast-1" | |
| AWS_ACCESS_KEY_ID="YOUR ACCESS KEY HERE" | |
| AWS_SECRET_ACCESS_KEY="YOUR SECRET ACCESS KEY HERE" | |
| INSTANCE_ID_URL="http://169.254.169.254/latest/meta-data/instance-id" | |
| INSTANCE_ID=$(curl -s ${INSTANCE_ID_URL}) | |
| SERVER_STATUS_URL="http://localhost/php-fpm-status" |
| #!/usr/bin/env bash | |
| # | |
| # Get the value of a tag for a running EC2 instance. | |
| # | |
| # This can be useful within bootstrapping scripts ("user-data"). | |
| # | |
| # Note the EC3 instance needs to have an IAM role that lets it read tags. The policy | |
| # JSON for this looks like: | |
| # | |
| # { |
| name: "GoogleNet" | |
| input: "data" | |
| input_dim: 10 | |
| input_dim: 3 | |
| input_dim: 224 | |
| input_dim: 224 | |
| # hierarchy 1 | |
| # conv -> relu -> pool -> lrn |
Source: http://forum.lowyat.net/index.php?showtopic=355950&view=findpost&p=11151482
A few forumers asked me questions regarding reading of MyKad surface information. The answer is there is no encryption; it is just about knowing what (APDU) command to send.
There will be 5 APDU commands that I'll introduce. I name them as:
Getting started:
Related tutorials:
| server { | |
| listen 80; | |
| server_name example.com www.example.com; | |
| if ($http_x_forwarded_proto = "http") { | |
| return 301 https://$server_name$request_uri; | |
| } | |
| ... directives to generate a response | |
| } |