會想開始寫這個是因為覺得有些書寫得不錯,但是覺得都沒推薦心得直接推薦不太妥。 所以就自己寫一篇了
- 講解了 MySql 5.7 與 MariaDB 10.1 的新特性,並詳細講解兩個同功能細節上的相異之處。
| - 我想要挑戰isomorphic,但目前好像比較少redux配isomorphic又配上webpack的方案 | |
| - 這個範例可看,最近全部改寫過 | |
| - https://github.com/coodoo/react-redux-isomorphic-example | |
| - 注意下面幾點 | |
| - js/bootClient.js 與 js/bootServer.js | |
| - bootServer.js 負責做 server-render |
| #!/bin/bash | |
| # xcode command tool | |
| xcode-select --install | |
| # check | |
| xcode-select -p | |
| # homebrew | |
| /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)" |
Here's what I did to get things working.
Yep, over at: https://developer.apple.com
| NOTE: Easier way is the X86 way, described on https://www.genymotion.com/help/desktop/faq/#google-play-services | |
| Download the following ZIPs: | |
| ARM Translation Installer v1.1 (http://www.mirrorcreator.com/files/0ZIO8PME/Genymotion-ARM-Translation_v1.1.zip_links) | |
| Download the correct GApps for your Android version: | |
| Google Apps for Android 6.0 (https://www.androidfilehost.com/?fid=24052804347835438 - benzo-gapps-M-20151011-signed-chroma-r3.zip) | |
| Google Apps for Android 5.1 (https://www.androidfilehost.com/?fid=96042739161891406 - gapps-L-4-21-15.zip) | |
| Google Apps for Android 5.0 (https://www.androidfilehost.com/?fid=95784891001614559 - gapps-lp-20141109-signed.zip) |
| #!/bin/bash | |
| # Size at the end is * 2048 where 2048 = 1 MB, so 1572864 = 768 MB | |
| #DISK=`/usr/bin/hdiutil attach -nobrowse -nomount ram://1572864` | |
| DISK=`/usr/bin/hdiutil attach -nobrowse -nomount ram://2097152` | |
| /usr/sbin/diskutil erasevolume HFS+ "RamDiskCache" $DISK | |
| CACHEDIR="/Volumes/RamDiskCache/$USER" |
One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.
Most workflows make the following compromises:
Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.
Use production SSL certificates locally. This is annoying