nguyentamvinhlong

MacOS

Build 3059

Download from here:

http://d.pr/f/QE3d

MD5: 59bab8f71f8c096cd3f72cd73851515d

nguyentamvinhlong

//PhantomJS http://phantomjs.org/ based web crawler Anton Ivanov anton.al.ivanov@gmail.com 2012
//UPDATE: This gist has been made into a Node.js module and now can be installed with "npm install js-crawler"
//the Node.js version does not use Phantom.JS, but the API available to the client is similar to the present gist

(function(host) {

    function Crawler() {
        this.visitedURLs = {};
    };
    

nguyentamvinhlong

//PhantomJS http://phantomjs.org/ based web crawler Anton Ivanov anton.al.ivanov@gmail.com 2012
//UPDATE: This gist has been made into a Node.js module and now can be installed with "npm install js-crawler"
//the Node.js version does not use Phantom.JS, but the API available to the client is similar to the present gist

(function(host) {

    function Crawler() {
        this.visitedURLs = {};
    };
    

nguyentamvinhlong

By default, Rails 3.2 loads everything in app/javascripts and everything in app/stylesheets on 
every page, despite controller-specific file naming. If you want to load controller-specific 
files only on views from their respective controllers, you need to change the manifests and the 
layout. The basic idea is to NOT require the entire trees, but only specific subfolders, in the 
manifests, and then load the controller-specific files separately in the layout.

Any file you DO want loaded on every page should be placed in app/assets/javascripts/general or 
app/assets/stylesheets/general.

For this to work in production, you also need to ensure that the individual files are precompiled by modifying your production.rb file, listing all of the controller-specific files.

nguyentamvinhlong

tmux shortcuts & cheatsheet

start new:

tmux

start new with session name:

tmux new -s myname

nguyentamvinhlong

tmux shortcuts & cheatsheet

start new:

tmux

start new with session name:

tmux new -s myname

nguyentamvinhlong

#Heroku, Ruby on Rails and PhantomJS

In this post, I’m going to show you how to modify an existing Ruby on Rails app running on Heroku’s Cedar stack to use PhantomJS for screen scraping. If you’ve never heard of PhantomJS, it’s a command-line WebKit-based browser (that supports JavaScript, cookies, etc.).

Let’s get started. This is a high-level overview of the required steps:

• Modify your app to use multiple Heroku buildpacks.
• Extend your app to use both the Ruby as well as the PhantomJS buildpacks.
• Confirm that everything worked.

nguyentamvinhlong

git rm -r --cached .
Followed by:

git add .
and

git commit -m "fixed untracked files"
This should fix your problem.

nguyentamvinhlong

All binary can be downloaded http://pan.baidu.com/s/1hqH2Pko

Sublime Text 3, build 3083 (dev) for Windows x64

OFFSET	ORIGINAL	CRACKED
0xe21b3	85	3B

md5:c3522c719d24f85dd770c93b9bf9e56f

nguyentamvinhlong

### USAGE
###
### ./ElasticSearch.sh 1.5.0 will install Elasticsearch 1.5.0
### ./ElasticSearch.sh 1.4.4 will install Elasticsearch 1.4.4
### ./ElasticSearch.sh will fail because no version was specified (exit code 1)
###
### CLI options Contributed by @janpieper
### Check http://www.elasticsearch.org/download/ for latest version of ElasticSearch

### ElasticSearch version