Memo for myself someday.
http://www.typescriptlang.org/Tutorial/
- Thinkpad X201s
- Ubuntu 12.04.1 LTS
| 1) Create a branch with the tag | |
| git branch {tagname}-branch {tagname} | |
| git checkout {tagname}-branch | |
| 2) Include the fix manually if it's just a change .... | |
| git add . | |
| git ci -m "Fix included" | |
| or cherry-pick the commit, whatever is easier | |
| git cherry-pick {num_commit} | |
Memo for myself someday.
http://www.typescriptlang.org/Tutorial/
When speaking of the Icecast protocol here, actually it's just the HTTP protocol, and this document will explain further how source clients need to send data to Icecast.
Since Icecast version 2.4.0 there is support for the standard HTTP PUT method.
The mountpoint to which to send the data is specified by the URL path.
A running example of the code from:
This gist creates a working example from blog post, and a alternate example using simple worker pool.
TLDR: if you want simple and controlled concurrency use a worker pool.
| version: 0.0 | |
| os: linux | |
| files: | |
| - source: / | |
| destination: /home/ec2-user/node | |
| permissions: | |
| - object: /home/ec2-user | |
| owner: ec2-user | |
| group: ec2-user | |
| type: |
This article will briefly describe how to install SonarQube as Docker container on Amazon EC2 and integrate it with Jenkins.
Go to RDS > Parameter Groups
Create a new Parameter Group with the following parameter:
max_allowed_packet = 268435456
We need to create a new RDS database for SonarQube (you may use an existing MySQL instance)
| package main | |
| import ( | |
| "database/sql" | |
| "encoding/json" | |
| "fmt" | |
| "reflect" | |
| "time" | |
| "github.com/go-sql-driver/mysql" |
| # This is something that I always forget and had a surprisingly hard time finding (or better yet, understanding). Here's the | |
| # scenario: a colleague creates a new kubernetes cluster, named" cluster-foo.example.com". You want to look at it (for | |
| # troubleshooting, updating the deployment, whatever). To get your kubectl installation to "see" the new cluster, take the | |
| # following steps: | |
| # ASSUMPTION: You have pointed kops to some location where the cluster configurations are stored | |
| # (I have this in my ~/.bash_profile): | |
| export KOPS_STATE_STORE=s3://example-state-store | |
| # Use kops to get the list of clusters |