vothanhkiet

Debug SHA1 (root of project)
    
    keytool -J-Duser.language=en -list -v -keystore ~/.android/debug.keystore -alias androiddebugkey -storepass android -keypass android

Release SHA1 (/android/app/)

    keytool -J-Duser.language=en -list -v -keystore mystore.keystore

vothanhkiet

/* global EXIF */
'use strict';

// Require library: https://github.com/jseidelin/exif-js
// Require Jquery (If not have jquery you must handle DOM by native js code)
/**
  @description this directive auto rotate image by css base on image orientation value
  Check the example of image orientation here: 
    https://github.com/recurser/exif-orientation-examples
  @example

vothanhkiet

/**
 * Deep diff between two object, using lodash
 * @param  {Object} object Object compared
 * @param  {Object} base   Object to compare with
 * @return {Object}        Return a new object who represent the diff
 */
function difference(object, base) {
	function changes(object, base) {
		return _.transform(object, function(result, value, key) {
			if (!_.isEqual(value, base[key])) {

vothanhkiet

Every so often I have to restore my gpg keys and I'm never sure how best to do it. So, I've spent some time playing around with the various ways to export/import (backup/restore) keys.

Method 1

Backup the public and secret keyrings and trust database

cp ~/.gnupg/pubring.gpg /path/to/backups/
cp ~/.gnupg/secring.gpg /path/to/backups/
cp ~/.gnupg/trustdb.gpg /path/to/backups/

or, instead of backing up trustdb...

vothanhkiet

Installing an Android ROM with your Mac via Heimdall and bash

Because every time I want to flash a new ROM, I forgot how I did it the last time.

This is how I re-flashed my unbranded Samsung Galaxy S4 (german black edition) with a stock ROM (because Cyanogenmod crashed my phone all the time). The correct Stock ROM for my Galaxy S4 is: I9505XXUHOJ2_I9505OXAHOJ2_I9505XXUHOJ2

Software you need

• adb
• heimdall (brew cask install heimdall-suite)

vothanhkiet

I recently ran into a problem where I had a suite of applications hosted on a set of subdomains that all needed to be able to share a single cookie. Any cookies other than the shared cookie needed to stay specific to their subdomain, but this one shared cookie needed to be accessible to any of them. I also wanted to accomplish this using Laravel's Cookie facade.

The Problem

To accomplish this, there were two issues to solve.

1. All cookies created by the Laravel framework are encrypted by default. (link)
2. I needed to figure out how to set a domain on the shared cookie that was different than the domain it was being set from.

Setting Non-Encrypted Cookies

In Laravel 5.1, a feature was added which allows you to add a list of cookie names that should not be encrypted to the EncryptCookies Middleware under the $except array. Check out [the docs](http://laravel.com/docs/5.1/responses#attaching-cookies

vothanhkiet

function keepTrying(otherArgs, promise) {
	promise = promise||new Promise();
	
	// try doing the important thing
	
	if(success) {
		promise.resolve(result);
	} else {
		setTimeout(function() {
			keepTrying(otherArgs, promise);

vothanhkiet

func EncodeStreamingVideo(streamingFile io.Reader, request ShouldCanceler) (*os.File, error) {
  outputFilename := generateFilename("mp4")

  // Actually start the command.
  cmd := exec.Command("ffmpeg",
    // Read input from stdin.
    "-i", "-",
    // ... environment-specific ffmpeg options ...
    "-y", outputFilename)

vothanhkiet

public function index(){
    $categoryList = Category::all();
    return view('category.list')->with('categoryList', $categoryList);
}

vothanhkiet

vi /etc/environment

add these lines...

LANG=en_US.utf-8
LC_ALL=en_US.utf-8